Skip to content

Privacy · GDPR: Privacy policy

How Revenue Precision, Lda. processes personal data on the call-emily.com website and in the emily product.

Last updated: 16 November 2026

01In short

  • emily is an artificial intelligence (AI) assistant for sales teams, built and run by Revenue Precision, Lda.
  • If you use emily through your company, your company decides about most of the data and we process it on its behalf.
  • What you say or write to emily, including your voice, and the data she looks up to answer you (CRM, ERP, email, calendar) are sent to an AI provider to be processed: Google (Gemini) and, in some accounts, Anthropic (Claude). The app asks for your permission before first use, and you can withdraw it whenever you like.
  • Your organisation's admins and managers can see your questions, emily's answers and the results of the tools she used.
  • You can delete your account inside the app, without contacting us. Your company's work records stay with your company.
  • We do not sell personal data. emily has no advertising and no ad tracking.
  • Gmail and Google Calendar data are used only for the features you ask for, and never to train AI models (see “Google user data”).

02Who we are and what this policy covers

emily (call-emily.com) is a product of Revenue Precision, Lda., a company based in Portugal. In this policy, “we” means Revenue Precision. Depending on the situation we are a controller or a processor under the General Data Protection Regulation (GDPR); “Who decides about your data” explains both cases. This English text is provided for convenience: the Portuguese version at call-emily.com/privacidade is the binding one, and if they differ, the Portuguese prevails.

For any privacy question, write to privacy@call-emily.com.

This policy applies when you:

  • visit the call-emily.com website;
  • use the web app (app.call-emily.com) or emily's iPhone and Android apps;
  • talk to emily by phone or WhatsApp, or contact emily's number without being a user;
  • receive an email, a message or a call from emily;
  • appear in information that one of our customers puts into or connects to emily.

03Who decides about your data

emily is a service for businesses. When a company uses emily (the “customer”), it is the controller of the work data that the company and its users put into or connect to emily: conversations, voice, meeting recordings, CRM, ERP, email, calendar, documents and reports. In those cases Revenue Precision is a processor and handles the data on the customer's behalf and on its instructions.

If you use emily through your employer or another customer company, take your questions to your company first. If you write to us, we will help and pass the request on.

Your data can also reach emily without you being a user: if you are a customer, supplier or contact of one of our customers, take part in a recorded meeting, or exchanged emails with a user. The customer is responsible for informing you and for answering your requests first; if you contact us, we pass the request on.

Before recording a meeting or connecting systems that hold other people's data, whoever uses emily must inform those people and, where the law requires it, obtain their consent.

Revenue Precision is the controller when it:

  • runs the website and sales contacts (demo requests and calls, forms, the “Ask emily” chat and website statistics);
  • manages the contract and invoicing with the customer;
  • provides the service to someone who created an account on their own, without an invitation from a company;
  • creates accounts and authenticates users;
  • protects the service against abuse and security incidents, provides support and fixes errors;
  • analyses how emily is used in order to improve it;
  • meets legal obligations.

04Data we process

We process the data below, depending on how you use emily and what your organisation connects or enters.

To have an account you need a name and an email, or a Google account. To talk to emily by phone or WhatsApp, you must register the number you call or write from. Integrations, photos and files are optional, but without them emily cannot do the tasks that depend on them.

Conversations, recordings and documents are free-form. emily does not need special categories of data (for example, about health) to work: do not enter them unless your company has a legal basis for that processing.

  • Account and identity: name, email, password (stored irreversibly), organisation, role (admin, manager or rep) and teams. If you sign in with “Continue with Google”, Google sends us your name, your email and your Google account identifier.
  • Phone numbers you register, used to recognise you when you call or write to emily.
  • Preferences: language, tone, voice, notifications and account status.
  • Personalisation profile: role, company, sector, goals, communication style and the notes emily remembers across conversations, to adapt the tone and content of her answers. It is a form of profiling used only for that purpose. You can view, add and remove what emily remembers in Settings, under “What Emily knows about you”.
  • Conversations: the messages you type or dictate in the app, chat, phone and WhatsApp, emily's answers, and the photos, PDFs and other files you send.
  • Voice: see “Voice and recordings”.
  • Interaction logs: for each request, the question, the answer, the tools used and their results, the duration, the cost and the AI model used. Results can include CRM or ERP data or the content of emails emily read. For phone calls we keep the transcript. These logs are how we measure use; we use no third-party analytics tools in the app.
  • Your organisation's business data: emily's CRM (companies, contacts, deals, notes, tasks and attachments, with change history), the data emily looks up in the company's ERP (customers, sales, balances, stock), Knowledge Base documents, reports, alerts and reminders. This data often includes third parties' personal data, such as customers' names, contacts and tax numbers.
  • Email and calendar, if you connect them: events (title, time, place, attendees), senders, subjects and previews, the content of emails you ask emily to read, drafts and the emails you ask her to send on your behalf.
  • Recordings from other services you connect (for example, Plaud): titles, dates, transcripts and summaries.
  • Integration credentials: Google, Microsoft and Plaud access tokens, mailbox passwords and ERP or CRM connection details. They are encrypted before being stored.
  • Technical data: IP address, browser or device type and server logs, used for security and to diagnose faults. In browsers and the Android app, if you turn notifications on, also the device's notification identifier.
  • Support and feedback: error reports, ratings of answers, feature ideas and votes.
  • Billing, if you subscribe to emily online: the company's billing details and payment history. Card details are handled by the payment provider and never reach our servers. The iPhone and Android apps do not take payments.
  • Website: what you fill in on forms and demo requests (name, email, phone, message), messages in the “Ask emily” chat and visit statistics.

05Voice and recordings

Revenue Precision does not record the audio of voice conversations with emily: it keeps only the transcript. emily does not use your voice to identify you; she recognises callers by their registered phone number.

  • Voice conversations in the app (web, iPhone and Android): microphone audio goes in real time, directly from your device, to Google (Gemini), which turns it into text and answers out loud. We keep the transcript.
  • Phone calls and WhatsApp calls: the audio passes through the communications operator (Twilio and, on WhatsApp, Meta) and our server, which forwards it in real time to Google (Gemini). We keep the transcript.
  • WhatsApp voice notes: we keep the audio file you send, which is also sent to the AI provider to be understood.
  • Meeting recorder: when you record a meeting in the app, we keep the audio, the transcript and the meeting report. These recordings also capture the voices of the other people present; tell them before recording.
  • Interpreter: the audio is sent in real time to Google (Gemini) for translation.
  • Audio files uploaded to the Knowledge Base: we keep the file and the transcript.

06Artificial intelligence and your permission

emily runs on third-party AI models. The main one is Google's Gemini (Gemini API), used to understand requests and answer, for real-time voice, transcription, summaries, translation and web search. In some accounts and features, written conversations and the messages emily sends on her own initiative are handled by Anthropic's Claude. These providers receive the data listed below only so that emily can answer.

Before first use, the app (web, iPhone and Android) explains this and asks for your permission. Without it, voice and chat do not work; the privacy policy, settings and account deletion stay available. You can withdraw permission at any time in Settings (⋯ button) → “emily AI”: emily stops working in the app until you allow it again.

Phone, WhatsApp and automatic tasks run on the setup made by your organisation and do not go through that screen; to stop using them, talk to your organisation or write to us.

Revenue Precision does not train AI models of its own on your data.

AI can be wrong: check answers before making decisions based on them. emily asks for confirmation before sending emails or messages to other people, deleting CRM records, cancelling meetings or saving orders in the ERP. emily does not take decisions that produce legal effects concerning you or that similarly significantly affect you (Article 22 GDPR).

What is sent to the AI provider:

  • your voice, in voice conversations, voice notes, the interpreter and meeting recordings you ask to transcribe;
  • the text of your messages and the conversation history;
  • the photos, PDFs and other files you send;
  • your personalisation profile (name, role, language, tone and what emily remembers);
  • the data emily looks up to answer: CRM, ERP, calendar, the content of emails you ask her to read, meeting transcripts and Knowledge Base documents;
  • web search phrases, when you ask for current information;
  • the text of the answers emily speaks back to you.

07What we use data for and on what legal basis

When we process data on a customer's behalf (Article 28 GDPR), the customer, as controller, determines the legal basis. Otherwise we use the bases of Article 6(1) GDPR listed below. We do not use your data for advertising and we do not sell it.

  • Providing the service (voice and written assistant, calls, WhatsApp, CRM, integrations, reports, reminders, alerts and notifications): on the customer's behalf; for self-created accounts, performance of the contract with the user.
  • Creating accounts, authenticating and sending invitations and sign-in links: performance of the contract or, for customers' users, the legitimate interest in giving secure access to the service.
  • Personalising answers with the personalisation profile: on the customer's behalf or, for self-created accounts, the legitimate interest in adapting the assistant to its user, with a right to object.
  • Protecting the service, preventing abuse and diagnosing faults (technical and interaction logs): the legitimate interest in keeping the service secure and working.
  • Providing support, fixing errors and improving the product (error reports, interaction logs, ratings, ideas and votes): the legitimate interest in solving problems and improving emily.
  • Managing the contract, invoicing and meeting accounting and tax obligations: performance of the contract and legal obligation.
  • Answering demo requests and contacts made on the website: steps taken at your request before entering a contract.
  • Sending product news: consent or, for customers, legitimate interest, with the right to object at any time.
  • Answering requests from authorities and defending rights in legal proceedings: legal obligation and legitimate interest.

08Who can access the data

In your organisation: admins and managers can see the interaction log of the organisation's users, which includes questions, answers and tool results (for example, ERP and CRM data or the content of emails emily read). Reps see only their own log. Members of the organisation share the CRM, meeting recordings, the Knowledge Base and colleagues' contact details, according to each person's role.

At Revenue Precision: a small number of team members can see interaction logs and error reports to provide support, ensure security, fix errors and understand how emily is used.

People you ask emily to send something to: when you ask emily to send an email, report or message to someone, that content reaches the recipient.

Authorities: where the law requires it.

Providers (processors): the providers below process data on our behalf, only to provide the service. We require them to protect the data to the same level described in this policy and to use it only for the purposes stated here.

  • Supabase: database, authentication and file storage. Holds emily's data described in this policy.
  • Google (Gemini API): AI model. Receives what is described in “Artificial intelligence and your permission”.
  • Anthropic (Claude): AI model used in some accounts and features. Receives the text of conversations and the data looked up to answer.
  • Twilio: phone calls and WhatsApp messages. Receives phone numbers, call audio in real time, and WhatsApp messages and files.
  • Meta (WhatsApp), through Twilio: the WhatsApp network.
  • Resend: sending emily's emails (invitations, notifications, reports and emails sent at your request).
  • Vercel: hosting of the web app and the website.
  • Hetzner: emily's server for phone, WhatsApp, the ERP connection and scheduled tasks.
  • Tailscale: encrypted private network between our server and the customer's ERP.
  • Google (Firebase Cloud Messaging) and browsers' notification services: delivery of push notifications on Android and the web. A notification only says what kind of alert it is, never names or amounts.
  • Stripe: payments for online subscriptions. Moloni: issuing invoices.
  • logo.dev: company logos in the CRM. Receives the company's website domain and the IP address of the device showing the logo.
  • On the website: Umami (visit statistics) and Calendly (demo booking).

09Services you connect to emily

These services are used only when the user or the organisation connects them, and remain governed by each provider's terms. emily accesses them only with the permission given when connecting them. What emily reads in these services is sent to the AI provider to answer your request and is kept in the interaction logs.

You can disconnect the calendar, mailbox and Plaud in Settings, under “Connected Accounts”. Organisation connections (ERP and other systems) are managed by admins.

  • Continue with Google: Google confirms your identity and sends us your name, your email and your account identifier.
  • Google Calendar and Gmail: emily reads, creates, changes and cancels events; searches and reads emails, creates drafts and sends them on your behalf when you ask (see “Google user data”).
  • Microsoft 365 (Outlook): emily reads, creates, changes and cancels events; searches, reads and drafts emails and sends them on your behalf when you ask.
  • Another mailbox (IMAP/SMTP): emily reads the inbox and sent items, saves drafts and sends emails on your behalf when you ask.
  • Plaud: emily reads your recordings, transcripts and summaries.
  • Your company's ERP (for example, PHC): emily queries it at your request and for scheduled alerts and reports. In PHC, she saves order drafts when you confirm them.
  • Other systems connected by an admin of your organisation: they receive the data emily passes to them to carry out your request.

10Google user data

When you sign in with “Continue with Google” or connect your Google account to emily, emily accesses the data below only with the permissions you grant on Google's consent screen, and only to provide the emily features you ask for:

  • Google profile (name, email and account identifier), scopes openid, https://www.googleapis.com/auth/userinfo.email and https://www.googleapis.com/auth/userinfo.profile: to create your account, sign you in and show which Google account is connected.
  • Gmail, read, scope https://www.googleapis.com/auth/gmail.readonly: to search and read the emails you ask emily about (for example, “what did customer X write to me?”), summarise them and answer questions about them.
  • Gmail, compose, scope https://www.googleapis.com/auth/gmail.compose: to create the email drafts you ask for in your Gmail Drafts folder and, when you ask and confirm, send them from your account.
  • Gmail, send, scope https://www.googleapis.com/auth/gmail.send: when this feature is available in your account, to send an email from your Gmail account, only when you ask and confirm the recipients, subject and text. emily does not use it to read your email or to send anything you have not confirmed.
  • Google Calendar (events), scope https://www.googleapis.com/auth/calendar.events: to show your schedule, prepare your visits, and create, change or cancel events when you ask.
  • emily asks for no other Google scopes. It does not access Google Drive, Google Contacts or any other Google service, and it asks for each permission only to provide the feature described next to it.

11How we protect and use Google data

Sharing with AI providers: to answer your request, the necessary part of that data (for example, the text of an email you ask emily to read, or your events for the day) is sent to the AI provider that runs emily, Google (Gemini API) and, in some accounts, Anthropic (Claude), only to generate the answer you asked for. It is not shared with anyone else, except the processors that host the service (see “Who can access the data”) or where the law requires it.

No AI training: Google Workspace APIs are not used to develop, improve, or train non-personalized AI and/or ML models. We do not use data obtained through Google APIs to develop, improve or train generalised AI or machine-learning models, ours or anyone else's, and the AI providers that answer your requests do not use it to train their models.

No sale and no advertising: we do not sell this data, and we do not use or transfer it for advertising (including personalised or targeted advertising), for credit-worthiness or lending decisions, or for any purpose unrelated to the emily features you use.

People: no one at Revenue Precision reads this data, except with your explicit consent for a specific case (for example, a support request), where necessary for security purposes (for example, investigating abuse), to comply with the law, or once aggregated and anonymised for internal operations.

What we store: your Google access tokens (encrypted), copies of your calendar events to show your schedule and, in the interaction logs, the excerpt of an email or event emily used to answer you. The drafts emily creates are saved in your own Gmail Drafts folder, not by us. We do not copy your mailbox.

How long we keep it: the access tokens and the copies of your calendar events are kept only while your Google account is connected. When you disconnect it, we delete them immediately and ask Google to revoke emily's access. Excerpts of emails and events in the interaction logs are kept while your emily account exists and are deleted when you delete the account; you can ask for them to be deleted earlier at any time (see “Your rights”). Copies in backups are overwritten within our hosting provider's backup cycle.

emily's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

How we protect Google data: the measures below apply to everything emily receives from Google.

Revoking access and deleting: you can disconnect your Google account in Settings → “Connected Accounts”; we then delete the access tokens and the copies of your calendar events and ask Google to revoke emily's access. You can also remove emily's access at https://myaccount.google.com/permissions. To delete everything else, including the interaction logs, delete your account (see “Deleting your account”) or write to privacy@call-emily.com.

  • Encryption in transit: all traffic between your device, our servers, Google's APIs and our AI providers uses TLS (HTTPS).
  • Encryption at rest: Google access and refresh tokens are encrypted with AES-256 before they are stored, with a key kept outside the database; the database and file storage are also encrypted at rest by our hosting provider.
  • Tokens stay on the server: they are never sent to your browser or to the apps, and are used only by our servers to call Google on your behalf.
  • Access control: database access rules (row-level security) limit each person's data to their own account and organisation. Access by the Revenue Precision team to production systems is restricted to the people who run the service, through individual accounts, and only for the purposes listed above.
  • Least privilege: emily asks only for the Google scopes listed in “Google user data”, and only when you connect your account.
  • Audit: every time emily reads or changes Google data on your behalf, the action is recorded in the interaction logs (what was done, when and for whom).
  • Incidents: if Google user data is affected by a security incident, we contain it, notify the people affected and the supervisory authority as the GDPR requires, and inform Google where its policies require it. To report a security problem, write to privacy@call-emily.com.

12Transfers outside the European Economic Area

Some of the providers listed in “Who can access the data” are based or process data outside the European Economic Area, notably in the United States (for example, Google, Anthropic, Twilio, Meta, Resend, Vercel and Stripe). In voice conversations in the app, the audio goes directly from your device to Google's servers.

These transfers rely on the mechanisms provided by the GDPR, such as the European Commission's adequacy decisions or the standard contractual clauses included in the contracts with those providers.

To find out which safeguards apply to a particular provider, or to ask for a copy, write to privacy@call-emily.com.

13How long we keep data

We keep data for as long as it is needed to provide the service. For data we process on a customer's behalf, the customer sets the periods; when the contract ends, the data is returned or deleted at the customer's request.

You can ask for any of this data to be deleted before the end of the period (see “Your rights”).

  • Account, profile, conversations, interaction logs, reminders and notifications: while the account exists. They are deleted when you delete the account.
  • The organisation's work data (CRM, meeting recordings, documents, reports): while the organisation keeps it and for the duration of the customer contract. A CRM record deleted in the app no longer appears; permanent erasure is done on request.
  • Credentials and copies of integration data (calendar, email, Plaud): until you disconnect the integration or delete the account.
  • Server logs and backups: for as long as needed for security and fault diagnosis, according to each provider's periods.
  • Messages, call records and emails kept by communications providers (Twilio, Resend): according to those providers' periods.
  • Billing data: for the period required by tax and accounting law.
  • Sales contacts and demo requests: for as long as the business relationship lasts or until you ask for them to be deleted.

14Deleting your account

You can delete your account at any time, inside the app and without contacting us. To confirm, you type the account's email. Deletion is immediate and cannot be undone.

If you are the only admin of a team with other members, first hand the admin role to someone else.

If you cannot access the app, you can ask for deletion in writing at privacy@call-emily.com.

Where to delete your account:

  • in the iPhone and Android apps: ⋯ button (Settings), top right → “Delete account”;
  • in the web app: Settings → “Delete account”.

15What happens to the data when you delete your account

emily is a work tool: deleting the account removes the person, not the company's records.

  • Deleted: your access and your profile, including phone numbers, preferences, AI permission and personalisation profile (what emily remembers about you).
  • Deleted: your conversations with emily, interaction logs, reminders, notifications and automatic tasks.
  • Deleted: connected accounts (calendar, email, Plaud), their credentials, email drafts and copies of calendar events and Plaud recordings.
  • Deleted: follow-up suggestions, order drafts, alerts, answer ratings and votes.
  • Stays with your company, no longer linked to your account: CRM companies, contacts, deals, notes and tasks and their history; meeting recordings and reports; Knowledge Base documents; report settings; ideas and comments. The content of these records may still include your name, your voice or what you wrote. To ask for it to be erased, contact your organisation or write to us.
  • Copies outside the database: server logs, backups and messages kept by communications providers are deleted according to the periods in “How long we keep data”.
  • Data on your device: deleted when you uninstall the app or clear the browser's data.

16iPhone and Android apps

emily's apps show the web app (app.call-emily.com) in their own window, with native functions for voice, sign-in and the screen. Everything this policy says about the web app therefore also applies to the apps.

The apps include no third-party advertising, analytics, attribution or tracking tools, and do not use your data to track you across other apps or websites.

  • Microphone: used when you talk to emily, in the interpreter and in the meeting recorder. In voice conversations the audio goes in real time to Google (Gemini) and is not recorded by Revenue Precision; in the meeting recorder the audio is kept (see “Voice and recordings”).
  • Speech recognition: when hands-free mode is available and you turn it on, the phone's system speech recognition listens for the word “emily” while the app is open, to start the conversation. That recognition is done by the system provider (Apple or Google).
  • Camera: used only when you choose to take a photo to send. The app does not access your gallery: it receives only the photo or file you choose.
  • Sign in with Google: opens the system's secure sign-in window. The app only signs in to accounts that already exist; new accounts are created on the website.
  • Screen on: while in use, the app keeps the screen from turning off. On Android it also gives small haptic signals. This collects no data.
  • Notifications: in the Android app, after you sign in, the device registers to receive notifications, which you can turn off by category in Settings. The iPhone app does not send push notifications.
  • Payments: the apps do not take payments.
  • What the apps do not use: the device's location, contacts, calendar and gallery, Bluetooth, health data and advertising identifier.

17Cookies and on-device storage

In the app we use only strictly necessary cookies, which keep you signed in. The app uses no advertising or tracking cookies. It also stores your preferences on the device (theme, language, voice and sound options) and the recent history of the main screen; on a shared device, sign out and clear the browser's or app's data.

On the call-emily.com website we use a functional language cookie and the theme preference. Visit statistics are done with Umami, which receives the IP address, browser type and page visited, with no advertising. On the contact page, Calendly's booking widget may set its own cookies.

18Security

No system is completely secure. If you find a security problem, write to privacy@call-emily.com. If a personal data breach occurs, we notify the supervisory authority and the people affected as required by the GDPR and, when we are a processor, we inform the customer without undue delay.

The measures we apply include:

  • encrypted traffic (HTTPS) between your device, our servers and our providers;
  • connection to the customer's ERP over an encrypted private network;
  • integration credentials encrypted before being stored, and passwords stored irreversibly;
  • data separated by organisation, and access according to each user's role;
  • private files (recordings, attachments, reports) served through temporary links;
  • confirmation before emily sends content to other people, deletes records or writes to the ERP;
  • restricted access for the Revenue Precision team.

19Your rights

To exercise your rights, write to privacy@call-emily.com. We answer within one month, which can be extended by two more months for complex requests. Exercising your rights is free, and we may ask you to confirm your identity. When your company is the controller, we pass the request to the company and help it answer.

You can object at any time to the processing we do on the basis of legitimate interest, including the personalisation of answers, and to receiving marketing communications.

Some things you can do directly in the app: correct your name, phone and preferences; see and remove what emily remembers about you; disconnect connected accounts; choose notifications; withdraw the AI permission; and delete the account.

You have the right to:

  • access your data and get a copy;
  • rectify inaccurate or incomplete data;
  • ask for your data to be erased;
  • ask for processing to be restricted, or object to it;
  • receive the data you gave us in a structured, commonly used format (portability);
  • withdraw consent at any time, without affecting processing already done;
  • lodge a complaint with the Portuguese data protection authority (Comissão Nacional de Proteção de Dados, CNPD) at www.cnpd.pt, or with the supervisory authority of the country where you live or work.

20Children

emily is a professional tool and is not intended for anyone under 18. We do not knowingly collect children's data. If you know that a child has given us personal data, contact us so we can delete it.

21Changes to this policy

We may update this policy to reflect changes in the service, providers or the law. The date at the top shows the version in force. If the changes are significant, we tell active users by email or in the app.

22Contact

  • Privacy and data protection: privacy@call-emily.com
  • Controller: Revenue Precision, Lda. (Portugal)
  • Supervisory authority: Comissão Nacional de Proteção de Dados (CNPD), www.cnpd.pt