Version 2026-10-16 · Effective 2026-10-16

Privacy Policy

Aimée LLC 30 N Gould St, Ste R, Sheridan, WY 82801, USA Email: founder@tryaimee.com EIN: 36-5184363

Effective Date: October 16, 2026 Version: 2026-10-16

This Privacy Policy explains how Aimée LLC ("Aimée," "we," "us," or "our") collects, uses, stores, and shares personal information in connection with the Aimée AI voice agent platform (the "Service"). Please read this Policy carefully before using the Service.

What Changed in This Version

Corrected the description of our current tracking settings: Analytics and Marketing are enabled by default before a visitor saves a choice; saved opt-outs, including those from older settings versions, take priority.
Explained the cookie-settings button, category controls, reload after opt-out, and the limits of stopping data already sent to a provider. A default setting or continued browsing is not treated as affirmative consent.
Distinguished contact matching on legacy Offer 3 Ads forms from the reduced event payloads used by the assistant signup funnel, and clarified where page tracking and Session Replay are excluded.

1. Who We Are

Aimée LLC is a Wyoming limited liability company registered at 30 N Gould St, Ste R, Sheridan, WY 82801, USA. We operate the Aimée AI voice agent platform, which provides AI-powered telephone answering and appointment scheduling services to private medical and healthcare clinics.

Data Protection Contact: founder@tryaimee.com (Subject: "Privacy Request"). This contact serves the equivalent function of a data protection contact for all privacy-related inquiries, rights requests, and regulatory correspondence.

Article 27 Representative Details: Data protection inquiries may be sent to founder@tryaimee.com. If and when Aimée appoints a representative under an applicable Article 27 requirement, the representative's contact details will be published here.

2. Scope of This Policy

This Policy applies to the following categories of individuals whose personal data we process:

Customers — clinics, medical practices, dental practices, beauty salons, and other businesses that register for and use the Service, and the Authorized Users (owners, managers, receptionists, and other staff) who access the Service on behalf of a Customer.

Callers — patients and other individuals who call a clinic that uses the Service. Callers are data subjects whose personal information is incidentally processed when they telephone a clinic deploying the Aimée voice agent.

Website visitors — individuals who visit tryaimee.com or related Aimée web properties. Website visitors are subject to standard server-side logging (IP address, user agent, page visited, referrer, timestamp). We use Google Analytics 4 and Yandex Metrica for usage measurement, Google Ads for ad attribution and lead-conversion measurement, and Meta Pixel for Facebook and Instagram ad reporting. Analytics and Marketing are enabled by default before you save a choice, so these providers may receive data and set non-essential cookies on a first visit. A saved opt-out takes priority. Section 12 describes the data involved, excluded pages, and how to turn either category off.

Prospective customers — individuals who begin, but do not complete, account registration through our "Get Started" flow. If you leave before finishing registration, we retain the details you provided so you can resume where you left off, and so we can follow up about completing the setup you requested (see Sections 3, 4, and 5 for the specific data, purposes, and retention that apply).

Aimée's Data Protection Roles

Aimée acts as a processor for personal data handled on a Customer clinic's instructions in providing the Service, including callers' and patients' real-time call audio, transcripts, caller ID, and appointment data. The Customer clinic is the controller for this data.
Aimée acts as a controller for personal data whose purposes and means Aimée determines for operating its own business, including Customer and Authorized User account data, billing data, prospective-customer lead data submitted through /get-started, server logs, and website analytics.

3. Categories of Personal Data Collected

Notice at Collection (CCPA): The following table describes the categories of personal information we collect, the sources from which we collect it, and our purposes for collection. This notice is provided at or before the point of collection as required by the California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA).

Category	Examples	Source	Lawful Basis (GDPR Art. 6)
Account data	Email address, full name, password hash, organization name, country, role, UI language preference	Customer registration	Contract performance (Art. 6(1)(b))
Billing data	Last 4 digits of payment card, billing address, invoice history, subscription plan	Stripe, Inc. (tokenized — we never receive full card data)	Contract performance (Art. 6(1)(b))
Call audio	Real-time audio stream during a call	Caller's telephone call	Not stored — processed in real time only; legitimate interest of Customer in operating the Service (Art. 6(1)(f))
Call transcripts	Text transcription of the conversation generated from call audio	Generated via Deepgram STT service	Legitimate interest of Customer in reviewing and acting on call content (Art. 6(1)(f))
Caller phone number	Caller ID (CLI/ANI) transmitted with the incoming call	Telnyx telephony provider	Legitimate interest in call routing and caller identification (Art. 6(1)(f))
Appointment data	Caller name, requested appointment date/time, stated reason for visit, may include health-related information disclosed voluntarily by caller	Disclosed during call	Legitimate interest; for health data disclosed in a healthcare context — Art. 9(2)(h), subject to Art. 9(3) (provision of healthcare or social care under Customer's responsibility)
Usage analytics	Login timestamps, feature usage patterns, dashboard interactions, IP address, browser user agent, session data	Customer dashboard activity	Legitimate interest in service security, performance optimization, and fraud prevention (Art. 6(1)(f))
Communication preferences	Marketing opt-in/opt-out flag and history	User selection during registration or in account settings	Consent (Art. 6(1)(a)) — marketing communications are sent only to those who have affirmatively opted in
Consent audit records	Truncated IP address, browser user agent, timestamp, document version hash, language shown at acceptance	Automatically recorded at time of legal document acceptance	Legal obligation (Art. 6(1)(c)) — GDPR Art. 5(2) accountability; Art. 7(1) demonstrating consent; Legitimate interest (Art. 6(1)(f)) — audit integrity (see Section 16)
Prospective customer (lead) data	Practice type, optional CRM name, work email address, marketing campaign source (UTM parameters), referring page, and a record of any follow-up contact we sent	"Get Started" form submission; page you arrived from	Legitimate interest (Art. 6(1)(f)) — continuing the account setup you started; Consent (Art. 6(1)(a)) for any optional marketing communications you separately opt into

For special category data (Art. 9 GDPR): health-related information may be incidentally disclosed by callers during the course of scheduling appointments (e.g., stating the reason for a visit or a medical condition). We process such data under Art. 9(2)(h) — processing necessary for the provision of health care or treatment — and only to the extent necessary to fulfill the caller's request. In accordance with Art. 9(3), this Processing is carried out under the responsibility of Customer as the healthcare provider, and Aimée personnel and Subprocessors with access to Personal Data are bound by confidentiality obligations equivalent to the applicable obligation of professional secrecy, as described in DPA Sections 6 and 7.2 and Annex III. We do not actively solicit health information beyond what is necessary for the scheduling function. Customer, as Controller, warrants that it has established the required Art. 6 legal basis and Art. 9 condition, provided the notices required by Arts. 13 and 14, and obtained all consents required by applicable law, as set out in ToS Section 7.5 and DPA Section 6.

4. How We Use Your Data

We use the personal data described in Section 3 for the following purposes:

Account data — to create and manage Customer accounts; to authenticate Authorized Users; to communicate service-related information (billing, security alerts, product updates where opted in); to enforce this Policy and our Terms of Service.

Billing data — to process subscription payments via Stripe; to generate and maintain invoice records; to comply with tax and financial record-keeping obligations.

Call audio — to power the real-time AI voice agent response. Audio is streamed to our speech-to-text provider (Deepgram) for transcription and is not stored or retained by Aimée.

AI transparency — for telephone calls, the Service plays the current AI and, where applicable, recording preamble at the start of the call, before the opening greeting. For website-widget calls, the Service presents the current preamble for the caller's acceptance before connecting and does not repeat it in audio after acceptance. After a telephone preamble is played, the Service records a compliance-log entry containing the playback event, the preamble version, and the exact text used. For a website-widget call where the caller accepts the preamble before connection, the compliance log instead records that acceptance together with the preamble version and text snapshot.

Call transcripts — to display call history and summaries in the Customer dashboard; to enable Customer staff to review calls and follow up on appointments; to generate analytics reports for the Customer.

Caller phone number — to route incoming calls; to display caller identification in the dashboard; to enable the AI agent to reference prior interactions where applicable.

Appointment data — to populate the Customer's appointment and task management workflows; to enable follow-up actions by clinic staff.

Usage analytics — to monitor Service security and detect fraudulent activity; to measure Service performance and reliability; to generate aggregated, non-identifiable usage statistics.

AI model training — Aimée does not use Customer Data to train or fine-tune AI models.

Communication preferences — to determine whether to send marketing communications, product announcements, or usage tips. We do not send marketing communications to users who have not affirmatively opted in.

Consent audit records — as described in Section 16.

Prospective customer (lead) data — to let you resume an incomplete "Get Started" registration; to send a single automated reminder email 24 hours after you start, via our transactional email provider Resend (Section 7); and, if that reminder does not lead to a completed registration, to allow one manual follow-up email from our own team, sent from an Aimée company email address (founder@tryaimee.com), inviting you to continue. We do not send marketing or newsletter content through this follow-up unless you separately opt in, and every message tells you how to ask us to stop.

5. Retention Periods

We retain personal data for the periods set out below. When data is no longer needed, we delete it, anonymize it, or reduce it to a form that can no longer be associated with an individual.

Data Category	Retention	Basis and implementation	Configurable by Customer?
Call and patient data — transcripts, summaries, caller phone numbers, free-text review reasons, and callback contact details	The period selected by Customer in `auto_delete_days`; the product default is 30 days from the call or callback date	Processed on Customer's documented instructions under the DPA. The hourly GDPR service then NULLs the personal-content fields; it preserves only non-identifying operational metadata needed for aggregate analytics and audit	Yes — Customer controls the period in clinic settings
Authorized User account and profile data	For the subscription term, then deleted or anonymized as soon as reasonably practicable; Aimée's operational target is within 90 days after the subscription ends, unless the data remains necessary for an unresolved legal or security matter	Contract performance (Art. 6(1)(b)) during the subscription; only a limited wind-down period after the account relationship ends	No
Billing records, invoices, and tax or accounting documents	For the applicable statutory retention period, then deleted or anonymized when that period expires	Compliance with tax, accounting, and financial record-keeping law (Art. 6(1)(c)). This basis applies only to the financial records, not to Authorized User profiles	No
Security and administrative audit records	While reasonably necessary to investigate security events, prevent fraud, and establish or defend legal claims; identifying fields are minimized or anonymized when no longer needed	Legitimate interests in security, audit integrity, and legal-claim evidence (Art. 6(1)(f))	No
Consent audit log entries	7 years from the consent event (see Section 16), after which they are deleted or irreversibly anonymized	Legal accountability and proof of consent (Art. 6(1)(c), GDPR Arts. 5(2) and 7(1)); legitimate interest in audit integrity and contractual evidence (Art. 6(1)(f))	No
Marketing communication preference history	While the preference is active; after opt-out, a minimized suppression record is retained for as long as reasonably necessary to ensure the opt-out is honored	Consent (Art. 6(1)(a)) for marketing; legal compliance and legitimate interest for the suppression record	No
Prospective customer (lead) data — if registration is not completed	Work email, CRM name, and any free-text details are deleted or anonymized 90 days after you started	Legitimate interest in allowing completion of the requested setup and limited follow-up (Art. 6(1)(f))	No
Prospective customer (lead) data — if registration is completed	Same 90-day deletion for the fields above; the record that you were referred by a given campaign and later became a customer is kept for up to 25 months, then aggregated or deleted	Legitimate interest in measuring campaign attribution using minimized data (Art. 6(1)(f))	No

Where Customer exercises a right to erasure (Section 9.2), we anonymize identifying fields in personal records rather than deleting rows that are required for compliance or audit purposes. Specifically, consent log entries survive account deletion with the user reference set to null (see Section 16).

6. Legal Bases for Processing (EU/UK)

This Section is addressed specifically to Customers and data subjects located in the European Union, European Economic Area, or United Kingdom. For each processing activity, we rely on the following legal bases under GDPR Article 6 (and Article 9 for special category data):

Contract performance (Art. 6(1)(b)): account management, billing, authentication, and core service delivery to Customers who have entered into a contract with us.
Legitimate interests (Art. 6(1)(f)): security monitoring, fraud prevention, call processing (transcripts, caller ID), essential operational metrics, and audit log integrity. In each case, Aimée's legitimate interests are balanced against the rights and interests of the data subjects concerned. Callers have a legitimate interest in having their calls answered efficiently; Customers have a legitimate interest in reviewing call records. This basis does not replace any separate requirement to obtain consent for non-essential cookies or advertising technologies.
Legal obligation (Art. 6(1)(c)): retention of financial records, tax compliance, and maintenance of consent audit logs for regulatory accountability purposes.
Consent (Art. 6(1)(a)): marketing communications. Consent may be withdrawn at any time via account settings without affecting the lawfulness of processing prior to withdrawal.
Art. 9(2)(h), subject to Art. 9(3): processing of health-related information incidentally disclosed during healthcare appointment scheduling, under Customer's responsibility as the healthcare provider and with the confidentiality safeguards described in DPA Sections 6 and 7.2 and Annex III.

7. Subprocessors

We use the following third-party service providers ("subprocessors") to deliver the Service. They process personal data under applicable provider terms and, where available for the active service plan, data processing agreements and transfer safeguards. Customers receive 30 days' advance email notice before we add or replace any subprocessor.

A complete, always-current subprocessor list with additional detail is maintained at https://tryaimee.com/legal/subprocessors.

Provider	Purpose	Data Location	Safeguards for Non-EU Transfers
Supabase, Inc.	Database and authentication	London, United Kingdom (`eu-west-2`)	Published DPA; database, authentication, and storage use the configured London region
Deepgram, Inc.	Speech-to-text transcription	USA	DPA signed; EU SCCs Module 2 (Commission Decision 2021/914) + UK IDTA (ICO, Version B1.0)
ElevenLabs, Inc.	Text-to-speech voice synthesis	USA	DPA signed; EU SCCs Module 2 (2021/914) + UK IDTA
Groq, Inc.	Large language model (LLM) inference — primary	USA	DPA accepted; EU SCCs Module 2 (2021/914) + UK IDTA
xAI Corp.	LLM inference — fallback	USA	DPA accepted; EU SCCs Module 2 (2021/914) + UK IDTA
Vercel, Inc.	Frontend hosting and edge delivery	USA (with global edge locations)	DPA in place under the Pro plan; includes EU SCCs (2021/914) and the UK IDTA
Railway Corp.	Backend hosting	USA	DPA signed; EU SCCs Module 2 (2021/914) + UK IDTA
Telnyx LLC	Telephony services	EU + USA	DPA signed; EU SCCs for US-routed traffic (2021/914) + UK IDTA
Stripe, Inc.	Payment processing	USA	DPA signed; EU SCCs Module 2 (2021/914) + UK IDTA; PCI-DSS Level 1 certified
Resend (Plus Five Five, Inc.)	Transactional email delivery (billing, callback/task and clinic notification alerts, and the single automated "Get Started" reminder email)	USA	DPA available; EU SCCs Module 2 (2021/914) + UK IDTA

8. International Data Transfers

Where we transfer personal data of EU/EEA or UK data subjects to subprocessors located in the United States, those transfers are governed by:

For EU/EEA data: the Standard Contractual Clauses (Module 2: Controller-to-Processor) adopted by the European Commission in Decision (EU) 2021/914, incorporated by reference into our agreements with each US subprocessor.
For UK data: the UK International Data Transfer Addendum to the EU SCCs (issued by the UK ICO), incorporated by reference.

A full list of subprocessors with their applicable safeguards is available at https://tryaimee.com/legal/subprocessors. Customers receive 30 days advance email notice before any subprocessor change.

9. Your Rights

9.1 All Users

Regardless of your location, you have the following rights in relation to your personal data:

Access: request a copy of the personal data we hold about you.
Correction: request that we correct inaccurate or incomplete personal data.
Deletion: request that we delete your personal data, subject to applicable legal retention requirements (see Section 16 for consent audit records).
Portability: receive a copy of your data in a structured, commonly used, machine-readable format.

To exercise these rights, contact us at founder@tryaimee.com with subject "Privacy Request" and sufficient detail to verify your identity.

9.2 EU/EEA and UK Residents (GDPR / UK GDPR)

If you are located in the EU/EEA or UK, you have additional rights under GDPR Articles 15–22:

Right of access (Art. 15): obtain confirmation of whether we process your personal data and receive a copy.
Right to rectification (Art. 16): have inaccurate personal data corrected without undue delay.
Right to erasure (Art. 17): have personal data deleted ("right to be forgotten") where it is no longer necessary, consent is withdrawn, or processing is unlawful — subject to the limitations described in Section 16 for consent audit records.
Right to restriction of processing (Art. 18): restrict our processing of your data in certain circumstances.
Right to data portability (Art. 20): receive your data in a structured format and transmit it to another controller.
Right to object (Art. 21): object to processing based on legitimate interests; we will cease processing unless we can demonstrate compelling legitimate grounds.
Rights related to automated decision-making (Art. 22): the Service does not make solely automated decisions that produce legal or similarly significant effects on individuals.

Supervisory authority: You have the right to lodge a complaint with a data protection supervisory authority. For EU/EEA residents, the relevant authority is the supervisory authority of the EU member state where you reside, work, or where the alleged infringement occurred. A list of EU supervisory authorities is maintained by the European Data Protection Board at edpb.europa.eu. For UK residents, the relevant authority is the UK Information Commissioner's Office (ICO) at ico.org.uk.

9.3 California Residents (CCPA / CPRA)

Notice at Collection: personal information is collected at the categories and for the purposes described in Section 3 above.

If you are a California resident, you have the following rights under the California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA):

Right to know: know what categories of personal information we collect, use, disclose, or sell, and to access the specific personal information we hold about you.
Right to delete: request deletion of your personal information, subject to certain exceptions.
Right to correct: request correction of inaccurate personal information.
Right to opt out of sale or sharing: you can turn off the Marketing category in Cookie settings to stop the Google Ads and Meta uses described in Section 12. Disclosures to advertising providers may qualify as "sharing" under applicable California law; we do not describe those disclosures as an absence of data sharing.
Right to limit use of sensitive personal information: we do not use or disclose sensitive personal information beyond the purposes permitted by the CPRA without your explicit consent.
Right to non-discrimination: we will not discriminate against you for exercising your CCPA/CPRA rights.

To submit a CCPA/CPRA request, contact us at founder@tryaimee.com or via your account dashboard. We will respond within 45 days.

9.4 Other US State Residents

We honor privacy rights under applicable state privacy laws in Virginia (VCDPA), Colorado (CPA), Connecticut (CTDPA), Utah (UCPA), Texas (TDPSA), Oregon (OCPA), and other US states that have enacted comprehensive privacy legislation, to the extent those laws apply to our processing activities. The rights available are substantially equivalent to those described in Section 9.3. Submit requests to founder@tryaimee.com.

10. How to Exercise Your Rights

To exercise any privacy right described in Section 9:

Email founder@tryaimee.com with the subject line "Privacy Request".
Include your full name, the email address associated with your account (or used when contacting a clinic), the specific right you wish to exercise, and sufficient detail for us to identify you and locate your data.
We may ask for additional verification to confirm your identity before processing your request.

Response times:

EU/EEA and UK requests (GDPR/UK GDPR): response within 30 days of receiving a complete request. Complex requests may be extended by a further 60 days with notice.
US requests (CCPA/CPRA and other states): response within 45 days of receiving a verifiable consumer request.

For callers (patients who called a clinic using the Service): direct your request to the clinic you contacted. Clinics are the data controller for caller data processed in connection with their use of the Service. Aimée acts as a data processor on behalf of the clinic for that data. We will assist clinics in fulfilling data subject requests as required by our DPA.

11. Security Measures

We implement appropriate technical and organizational measures to protect personal data against unauthorized access, loss, destruction, or alteration:

Encryption in transit: all data is transmitted using TLS 1.2 or higher.
Encryption at rest: persisted Customer data is stored in the configured Supabase London (eu-west-2) region and protected by provider-managed encryption at rest.
Access control: role-based permissions and tenant-bound authorization checks restrict application access to authorized personnel and Authorized Users.
Audit logging: defined security-sensitive operations, including legal consent and selected administrative actions, are recorded in dedicated append-only audit tables; application and infrastructure activity is recorded in operational logs subject to provider retention.
Data minimization: call audio is processed in real time and is not stored or retained. Only the resulting transcript is saved, subject to the retention periods in Section 5.
Monitoring and incident response: we use application logs, infrastructure health checks, provider alerts, and manual operational review to identify potential security incidents. Our notification responsibilities depend on our role for the affected data:
- Customer-controlled data: where Aimée acts as processor, we notify the affected Customer without undue delay after becoming aware of a Personal Data Breach. The Customer, as controller, is responsible for determining whether to notify the relevant supervisory authority and affected individuals and for making those notifications. We provide reasonable assistance to support the Customer's compliance.
- Aimée-controlled data: where Aimée acts as controller, we determine whether notification is legally required and notify the relevant supervisory authority and affected individuals where required by applicable law.
Third-party security: subprocessors are governed by applicable provider terms and the transfer safeguards identified in Section 7.

12. Cookies and Tracking

Aimée uses cookies and similar technologies on the Service and on our marketing website. Analytics and Marketing are enabled by default before you save a choice. On eligible pages, the configured tags may load, send events, and set non-essential cookies during that first visit. A saved choice takes priority, including an opt-out retained from an older settings version. If browser storage is cleared or your choice cannot be read, the default settings apply again.

The round cookie-settings button at the bottom left and the "Cookie settings" link in the footer open the settings panel. You can choose "Reject all" or turn individual optional categories off and save. The default settings, opening or closing the panel, and continued browsing are not affirmative consent. Describing these technical defaults does not remove any applicable requirement to obtain consent before non-essential tracking.

We use three cookie categories:

Necessary — required for login sessions, security, saved preferences, and a support chat you choose to open. Crisp is loaded only after you click the chat button.
Analytics — Google Analytics 4 and Yandex Metrica on the marketing website and ordinary customer dashboard pages, while Analytics is enabled, including its default-on state. Yandex Session Replay is disabled in the dashboard and on personal signup/onboarding steps; form input contents are masked where Session Replay runs. Protected Auth, admin, widget, call-history and support routes and URLs containing recognized secrets or contact fields are excluded from ordinary page tracking. Personal assistant-session URLs are replaced with a generic funnel path and safe step for permitted analytics events.
Marketing — the Google Ads website tag measures ad visits and successful lead submissions while Marketing is enabled, including its default-on state. Our Google Ads conversion payload does not include submitted contact details or CRM name, and ad personalization signals are disabled in that tag. Meta Pixel measures eligible website and dashboard page visits and funnel stages such as signup, Checkout entry and trial activation. Legacy Offer 3 Ads form events may also provide submitted work email and phone number through Meta's advanced-matching fields, plus practice category, CRM name and whether CRM was supplied. The assistant signup funnel uses reduced stage events and does not deliberately put the submitted email, phone, website, resume capability or session UUID into its counter-event payloads. Meta's automatic form-interaction detection is enabled, so this reduced custom payload is not a guarantee that Meta cannot otherwise observe a form interaction. Meta page tracking is excluded from personal assistant-session pages and protected Auth, admin, widget, call-history and support routes. LinkedIn Insight Tag and TikTok Pixel are not loaded.

Cookie	Category	Set by	Purpose	Lifetime
`NEXT_LOCALE`	Necessary	Aimée	Remembers your interface language	1 year
`crisp-client/*`	Necessary (on chat use)	Crisp	Restores your support conversation after you open the chat	Up to 6 months
`_ga`	Analytics	Google Analytics	Distinguishes visitors	2 years
`_ga_*`	Analytics	Google Analytics	Persists session state	2 years
`_ym_*`	Analytics	Yandex Metrica	Counts eligible website and dashboard visits; supports Session Replay outside the dashboard and personal signup/onboarding steps	Up to 1 year
`_gcl_*`	Marketing	Google Ads	Links an ad interaction with a website conversion	Up to 90 days
`_fbp`	Marketing	Meta Pixel	Identifies a browser for ad reporting	Up to 90 days
`_fbc`	Marketing	Meta Pixel	Stores a Facebook ad click identifier when present	Up to 90 days

Aimée stores authentication sessions and the cookie-preference record in browser storage rather than cookies. Browser storage also holds campaign attribution, event-delivery receipts and pending funnel-event markers. Pending assistant-event markers contain an opaque deduplication identifier and timestamp, rather than the event payload, and expire after up to seven days. Turning off a category discards its pending assistant events. Providers also receive ordinary network information such as an IP address and browser information when their tags communicate with them.

Changing your choice: you can review or change either optional category at any time using the cookie-settings button or footer link. Turning a category off saves the preference and reloads the page to remove tags already loaded in that document. On the reloaded page, disabled-category tags are not loaded. These controls do not recall data already sent to a provider or guarantee deletion of cookies already set; you can also clear site data in your browser or contact us about your privacy rights. Rejecting optional tracking does not prevent use of the Service.

Preference record: when you save cookie preferences, the browser attempts to send a record containing the timestamp, a salted one-way hash of your IP address, a hash of your user agent, the selected categories, settings version, the control used and, where supplied by the hosting platform, a country code. This cookie-preference log does not store your raw IP address and is retained for up to 24 months. A default setting without a saved user action is not logged as an affirmative consent action.

EU/EEA and UK users are not required to accept any cookies beyond strictly necessary cookies to use the Service. If you have questions about specific cookies used by the Service, contact founder@tryaimee.com.

12.1 Google Calendar Connection

If an Authorized User chooses to connect Google Calendar, Aimée accesses only the Google Calendar data needed to show that user's existing calendar list, let the Authorized User select calendars for the Customer's doctors, verify access to those selected calendars, and create, read, update, or delete appointment events for the Customer. When the Authorized User explicitly selects Create a calendar for this doctor, Aimée also creates that secondary calendar in the connected Google account and assigns it to the selected doctor. Aimée does not create calendars automatically, change calendar sharing or permissions, or access Google Contacts, Gmail, Drive, or any other Google service through this connection.

We retain the selected calendar identifiers in the Customer's integration configuration. Calendar-list display data is fetched on demand and is not retained as a separate inventory. A calendar created at the Authorized User's request remains in that user's Google account if the doctor is removed, setup is cancelled, or Google Calendar is disconnected; the user can delete it in Google Calendar. During setup, OAuth credentials are encrypted and expire after 30 minutes unless the connection is activated. Active OAuth credentials remain encrypted and are retained only while the connection is active. An Authorized User can disconnect Google Calendar in the dashboard. Aimée asks Google to revoke the grant before removing active OAuth credentials; if Google does not confirm revocation, the credentials remain encrypted so the Authorized User can retry safely.

Google Calendar data is not sold, used for advertising, or used to train or improve generalized AI or machine-learning models. We do not allow humans to read connected Google Calendar data except with the Customer's affirmative agreement for requested support, where necessary for security, or where required by law. Aimée's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

13. Children's Privacy

The Service is not directed to children under the age of 16, and we do not knowingly collect personal information from individuals under 16. If we learn that we have inadvertently collected personal information from a child under 16, we will take prompt steps to delete that information. If you believe that a child's personal information has been submitted to the Service, please contact us immediately at founder@tryaimee.com.

14. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of changes as follows:

Material changes (such as new categories of data collected, new subprocessors, or changes to your rights): we will provide at least 30 days' advance written notice to the email address on file in your account before requiring an existing Customer to accept the updated Policy. An existing Customer may choose to review and accept the new version earlier; otherwise the previously accepted version continues to apply as explained below.
Minor or cosmetic changes (such as clarifications or formatting updates that do not affect your rights or our practices): we may update the Policy without prior notice, but we will always update the version date at the top.

Each version of this Policy takes effect on the Effective Date stated in that version. A Customer registering on or after that date accepts the then-current version. For an existing Customer, the version that Customer previously accepted continues to apply until the Customer accepts the updated Policy. If the Customer does not accept within the applicable acceptance period, incoming calls continue to be processed, the dashboard becomes view-only, and the active subscription remains payable until accepted or cancelled, as described in Section 19.6 and Section 12.2 of the Terms of Service. Where active re-acceptance is required under our three-tier re-acceptance system, you will be prompted to review and accept the updated Policy in the Service dashboard.

15. Contact Us

For privacy-related questions, rights requests, and data protection inquiries:

Aimée LLC 30 N Gould St, Ste R, Sheridan, WY 82801, USA Email: founder@tryaimee.com Subject line: "Privacy Request" or "Legal Notice"

Data Protection Officer: Aimée LLC has not appointed a Data Protection Officer. Data protection inquiries may be sent to founder@tryaimee.com.

For complaints that cannot be resolved directly, EU/EEA residents may contact their national supervisory authority and UK residents may contact the Information Commissioner's Office (ico.org.uk).

16. Special Notice — Consent Audit Logs

When you accept our Terms, Privacy Policy, DPA, or change your marketing preferences, we record a consent event including a truncated IP address (first 3 octets for IPv4 / first 48 bits for IPv6), browser user-agent, timestamp, and a cryptographic hash of the document version you saw, together with the language in which it was presented.

Lawful basis for this retention: these records are processed and retained under:

GDPR Art. 6(1)(c) — compliance with a legal obligation, specifically Aimée's accountability obligation under GDPR Art. 5(2) and the obligation under Art. 7(1) to be able to demonstrate that consent was obtained; and
GDPR Art. 6(1)(f) — legitimate interest in maintaining the integrity of audit logs for fraud prevention, contractual evidence, and regulatory compliance.

Important: because these records exist to satisfy a legal obligation, and because they have been minimized (truncated IP, no full identifier), we may decline requests to erase them under GDPR Art. 17(3)(b) and (e). They are retained for seven (7) years from the date of consent. Aimée selected this period as reasonably necessary to prove the fact and content of consent and to align the evidence window with contractual limitation periods in the jurisdictions where Aimée operates; it is not a statement that every such jurisdiction has the same limitation period.

If you delete your account, the user account record is anonymized but the consent log entries remain with the user reference set to null. This ensures we can prove consent was lawfully obtained without continuing to process you as an identifiable individual.

This Privacy Policy is effective as of October 16, 2026. Version 2026-10-16.