Privacy Policy
Last updated: November 4, 2026
This Privacy Policy describes how Rothian IT LLC, a company established in the United Arab Emirates (“Rothian”, “we”, “us” or “our”), which operates the Amelia AI-powered sales and marketing platform (“Amelia” or the “Service”), collects, uses, discloses, stores and otherwise processes personal data. It covers the Service, the websites at amelia.always.expert and the custom domains on which the Service is offered, and our related dealings with customers, prospective customers, their staff and the individuals they contact. It covers your rights under the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) (the “PDPL”) and, for people in Europe and the UK, the EU General Data Protection Regulation and the UK GDPR (together, the “GDPR”). Please read it together with our Terms of Service and Cookie Policy.
1. Who we are, and whose data this covers
1.1 Contact. Amelia is operated by Rothian IT LLC. For questions about this policy or your data, contact us at info@rothian.com. That address is the point of contact for every request.
1.2 Our two roles. Our role, and who you should approach first, depends on your relationship with us:
- People who use Amelia or visit our website. For account holders, staff of our customers, website visitors, people who ask us for a demo, and people who deal with us about the Service, we decide how the data is used and we are its controller.
- People our customers contact through Amelia. When a company uses Amelia to hold its leads, send campaigns or answer chats, that company decides how your data is used and is its controller. We process it on the company’s behalf, under the Data Processing Schedule to our Terms of Service. If you received a message from a company using Amelia, its own privacy policy applies, and your requests should go to that company first. If you write to us, we will pass your request on to them. This also applies to individuals who use a company’s buyer portal, property pages or website chat.
1.3 Sections that refer to “a customer’s contacts” describe what the Service does on a customer’s instructions. They are here so that you can understand the Service, and they do not replace the customer’s own notice to you.
2. Information we collect
2.1 Categories. We collect or process the following categories of personal data, depending on how you interact with us:
- Account & profile data — your name, email address, phone number, company, role, and authentication details when you sign up, including any phone verification you choose to complete and records of the terms you accepted.
- Business content customers provide — leads, contacts, products, projects, campaigns, quotes, and knowledge-base documents added to the platform. Customers may import contact lists, and may have contact details filled in by a business contact data service. For a contact, this can include name, email address, phone number, employer, job title, professional profile links, location, and notes on what they may be interested in.
- Messages and chats — emails, WhatsApp and Instagram messages and website chats sent through Amelia, including replies written by its AI, attachments and related delivery records.
- Website visitors and demo requests — on our own website we count page views and demo requests without cookies, with an approximate location and your browser’s language, and we keep what you enter when you ask for a demo. Customers can use the same measurement on their own websites. See our Cookie Policy.
- Usage data — log and device information, pages viewed, and actions taken, used to operate and improve the service.
- Support and correspondence — what you send us when you ask for help, report a problem or otherwise write to us, including tickets and attachments.
- Connected-account data — when you link a third-party account (such as LinkedIn, Facebook, Instagram, WhatsApp or Google), we receive information according to the permissions you grant. Sections 3 and 4 explain this for LinkedIn and Meta.
2.2 Interest scoring and per-person tracking. For a customer’s contacts, the Service records whether a campaign email was delivered, opened and clicked, and unsubscribes. Where a customer switches it on, links to its website can carry a private code, so visits from those links are recorded against the person who received them. The code expires after 120 days and stops matching as soon as that person opts out. Amelia also works out how interested a contact seems from their replies and tone, email activity, visits, company details, what they have said about budget, timing and requirements, their investor grade and any reservation. A high score can automatically assign the contact to a team member, alert the team, and, where the customer has set this up, trigger an email or enrol them in a campaign. It does not make decisions with a legal or similarly significant effect.
2.3 Sources. We obtain personal data directly from you; from the customer whose workspace holds it, including lists that customer imports; from business contact data services and email-checking services a customer uses through the Service; from platforms you connect; and automatically from your device or from email and messaging providers when you interact with the Service.
2.4 Whether you must provide it. Account details are needed to create an account, and information about a problem is needed to resolve it. Otherwise, providing data to us is generally optional, but some features may not work without it.
2.5 Sensitive data. We do not ask for special categories of personal data. Please do not include them in chats or messages unless you have a reason to. Customers must not upload such data unless the law allows it.
3. LinkedIn integration
When you choose to connect your LinkedIn account using “Sign In with LinkedIn” (OpenID Connect), we receive your basic profile information — your name, profile picture, email address, and LinkedIn member identifier — together with an OAuth access token issued by LinkedIn.
With your explicit authorization, we use this connection only to:
- Publish posts that you have reviewed and approved to LinkedIn on your behalf, from Amelia’s social media tools; and
- Where you grant advertising permissions, create, manage, and report on advertising campaigns within ad accounts that you administer.
We act only with your consent and only on pages or ad accounts where you hold the appropriate role. We store LinkedIn access tokens securely, do not sell them, and do not share LinkedIn data with third parties for their own purposes. We use LinkedIn data solely to provide the features you request, in compliance with the LinkedIn API Terms of Use and Platform guidelines. You can disconnect LinkedIn at any time from Paid Ads → Accounts & Setup; doing so deletes the stored access token from our systems.
4. Meta integrations (Facebook, Instagram and WhatsApp)
You can connect your business’s Meta assets to Amelia through Meta’s own login screen (Facebook Login for Business). You choose which business, ad accounts, Pages and WhatsApp accounts to share, and Meta gives Amelia an access token limited to what you selected.
Depending on what you connect, we receive:
- Business details — the ID and name of your Meta business portfolio.
- Advertising data — the IDs, names, currencies and status of the ad accounts you share, their Meta Pixels, and the performance figures (such as spend, reach, clicks and results) of campaigns run through Amelia.
- Pages — the IDs and names of the Facebook Pages you share, any Instagram account linked to them, and the Page’s recent posts, so you can choose one to promote.
- WhatsApp — your WhatsApp Business Account ID, phone number and display name, your message templates, and the messages exchanged with your customers on that number.
We use this data only to provide the features you ask for:
- Create, run, pause and report on advertising campaigns in the ad accounts you share, under the Page you choose; and
- Set up your WhatsApp number in Amelia’s inbox, and send and receive WhatsApp messages and templates on your business’s behalf, including Amelia’s AI replies where you have turned them on.
We store Meta access tokens encrypted, do not sell Meta data, and do not share it with third parties for their own purposes. The service providers described in Section 7, such as the messaging provider that carries your WhatsApp conversations, process it only to run these features. We handle Meta data in line with the Meta Platform Terms and Developer Policies.
Removing access and deleting your Meta data
You can disconnect at any time. Disconnecting Facebook Ads in Paid Ads → Accounts & Setup deletes the stored access token and the list of ad accounts and Pages we hold for it. You can also remove Amelia from your business integrations in Facebook or Meta Business Suite settings, which ends our access straight away.
To have all Meta data we hold about you or your business deleted, email info@rothian.com with the subject “Meta data deletion” and the name of your Amelia workspace. We will delete it and confirm by email once it is done.
5. How we use information, and on what basis
5.1 Where we are the controller, we use personal data for these purposes, on these legal bases:
- To provide, operate, and maintain the platform and its features: performing our contract with you or your company, or our legitimate interest in providing the Service to our customers’ staff.
- To create and manage accounts, verify identity and keep records of acceptance: performing that contract, and our legitimate interest in knowing who uses the Service.
- To generate AI-assisted content and chat replies from the content provided: performing that contract.
- To analyze usage, measure performance, count visits to our website and improve our services: our legitimate interest in running and developing a good product.
- To secure the platform, prevent abuse and fraud, and troubleshoot issues: our legitimate interest in keeping the Service safe, and legal obligations where they apply.
- To communicate with you about your account and provide support, and to answer a demo request you made: performing that contract, or taking the steps you asked for.
- To tell business contacts about the Service: our legitimate interest in promoting it, or your consent where the law requires it. You may opt out at any time.
- To comply with legal obligations, respond to lawful requests, and establish or defend legal claims: legal obligation, and our legitimate interest in protecting our rights.
5.2 Where the PDPL applies, we rely on your consent or on another ground that law provides, including performing a contract with you and establishing or defending legal claims.
5.3 For the people our customers contact, the customer decides what its messages are for and is responsible for having a lawful basis to send them, including any consent the recipient’s country requires.
5.4 Legitimate interests. Where we rely on legitimate interest, we have considered that interest against your rights and expectations. You may ask us for more information about that assessment, and may object as Section 10 describes.
5.5 Automated processing. Interest scoring and AI replies are automated. We do not use them, and customers must not use them under our Terms, to make decisions producing legal or similarly significant effects on a person solely by automated means.
6. AI processing
Amelia uses OpenAI to write chat replies, drafts, summaries, and other outputs, to search documents, and to help classify messages. The relevant content, including what someone says in a chat, is sent to OpenAI to produce the output. Under OpenAI’s terms for business customers, it is not used to train OpenAI’s models unless the business opts in. We do not use a customer’s data to train models for use outside that customer’s workspace. AI output can be wrong. Where a customer has switched on AI replies, messages may be answered by AI without a person reviewing each one.
7. How we share information
7.1 We do not sell your personal information. We share data only:
- With service providers that run parts of the platform for us: Supabase (database), Cloudflare (file storage), Vercel (hosting), Trigger.dev (background jobs), Upstash (rate limiting), OpenAI (AI), Unstructured (reading uploaded documents), Resend (email delivery), Chatwoot (message inbox), Meta (WhatsApp and Instagram messaging), bundle.social (publishing social posts), PostHog (website analytics), Mapbox (maps), Bouncify (email address checks), and Gridnimbus (a feedback tool on our pages). A customer may also obtain business contact data from RocketReach or Lusha, which are its sources of that data.
- With platforms you connect, at your direction (for example, publishing to LinkedIn or sending a WhatsApp message). Meta handles WhatsApp messages under its business messaging terms, and Instagram, Facebook and advertising activity as a company in its own right under its own policies.
- With the company whose workspace it belongs to, and the people it gives access to.
- When required to comply with law, a court order or a regulator’s lawful request, to enforce our terms, or to protect rights and safety.
- With professional advisers, under a duty of confidentiality, where needed for our legal, accounting or insurance purposes.
- In connection with a business transfer (such as a merger or acquisition), subject to this policy.
7.2 Changes to this list. We will update this list when we add or replace a service provider. Customers receive notice of changes as the Data Processing Schedule to our Terms of Service provides.
8. Data retention
8.1 We keep personal data for as long as needed for the purposes in this policy, and then delete it or make it anonymous, taking into account the nature of the data, the risk from unauthorised use, and legal requirements. We have not set fixed periods for most records, and work by these criteria:
- Accounts and workspaces: for as long as the account is active or needed to provide the service, then as required to comply with legal obligations, resolve disputes, and enforce agreements. A customer may ask for an export for 30 days after its subscription ends, and we then delete its data within 90 days, as our Terms describe. Copies in backups are removed in the ordinary backup cycle.
- Customers’ contacts: for as long as the customer keeps them in its workspace, as the customer decides.
- Opt-outs: for as long as we hold the contact, so that they are not contacted again. If an opted-out contact is then deleted, or a company deletes a contact at their request, we keep a one-way fingerprint of their email address and phone number, with the reason and date, for as long as that company holds an account with us, so that they stay opted out if they are added again. The fingerprint cannot be read as the address or number, but it can still be matched against them, which is its purpose.
- Visit records: if a contact is deleted, their visit records stay but no longer point to them.
- Demo requests and correspondence: for as long as they are useful to deal with the request and any relationship that follows.
- Connected-account tokens: until you disconnect, as Sections 3 and 4 explain.
- Website analytics: for as long as the analytics service keeps it under our plan.
8.2 You may request deletion of your data as described below.
9. Security
We protect your information with measures including encryption in transit, access controls, separation of each workspace’s data, logging of staff and workspace actions, and storage of credentials and access tokens in access-controlled systems, with Meta advertising tokens encrypted. No method of transmission or storage is completely secure. If a breach puts you at risk, we will tell you and the relevant authorities as the law requires. Where we hold the data for a customer, we will tell that customer, which is responsible for telling you.
10. Your rights and choices
10.1 Depending on where you live and the law that applies, you may have the right to:
- Access, correct, or export your information, and ask how we got it and who has received it.
- Request deletion of your account and associated data.
- Restrict or object to how we use your information, including any use based on legitimate interest.
- Withdraw consent and disconnect any linked third-party account (including LinkedIn and Meta) at any time. This does not affect what was done before you withdrew it.
- Opt out of non-essential communications. Every campaign email has an unsubscribe link, which also stops your visits being matched to you.
- Not be subject to a decision based solely on automated processing that has legal or similarly significant effects on you.
10.2 Your right to object to direct marketing. You may object to direct marketing at any time, without giving a reason, and we will stop. If a company using Amelia is sending it, use the unsubscribe link in its emails or contact that company. Unsubscribing stops further campaign emails and, from a few minutes later, opening or clicking an email you already have is no longer recorded against you in Amelia, although the email provider that carries it may keep its own logs.
10.3 To exercise any of these rights, contact info@rothian.com. We may need to confirm your identity, and we may decline or limit a request where the law allows, in which case we will explain why. We will reply within one month, which the law may allow us to extend by up to two further months for a complex request, and we will tell you if so. Where a customer is the controller, we will pass your request to that customer.
10.4 You may also complain to the data protection authority where you live: in the UK the Information Commissioner’s Office, in the EU your national supervisory authority, and in the UAE the federal data protection regulator.
11. International data transfers
11.1 Your information is not kept only in your own country. Rothian is established in the UAE. Our main database is in India (Mumbai). Website analytics is processed in the EU. Other providers listed in Section 7, including OpenAI, Resend, Vercel and Meta, may process it in the United States and elsewhere under their own contract terms. Those countries may not have data protection laws equivalent to yours, and we have not relied on a finding that they do.
11.2 Where the GDPR restricts a transfer from a customer to us, the Standard Contractual Clauses in the Data Processing Schedule to our Terms apply once those Terms apply to that customer. For data we hold as controller, you can ask us about the safeguard that applies to a transfer of your data using the address in Section 15.
12. Cookies
We use essential cookies to keep you signed in and to operate the platform. Our website counts visits without cookies. Our Cookie Policy lists what is stored and why. You can control cookies through your browser settings.
13. Children
Amelia is intended for business use by adults and is not directed to individuals under the age of 18. We do not knowingly collect their data. If you believe a child has given us personal data, contact us and we will delete it.
14. Changes to this policy
We may update this Privacy Policy from time to time. We will revise the “Last updated” date above and, for material changes, provide additional notice where appropriate.
15. Contact us
Questions about this Privacy Policy or your data can be sent to Rothian IT LLC at info@rothian.com.