Legal terms and conditions

1. Who We Are

Anayati SAS, a French société par actions simplifiée, operates the Service and acts as the controller for the personal data described in this Notice unless we state otherwise for a specific processing context.

For privacy questions, requests, or complaints, contact contact@anayati.com.

Our registered office and company-registration details are listed in the Legal Notice.

2. What This Notice Covers

This Notice explains how we collect, use, disclose, retain, and otherwise process personal data when you visit the public site, create an account, use learning and creation features, interact with billing flows, publish content, contact support, or receive product emails.

3. Data We Collect

We collect different categories of data depending on how you use the Service:

• Account and identity data: name, email address, login method, account identifiers, password-related records, verification status, and onboarding state. If you use Sign in with Apple, this includes the stable Apple account subject used to bind your Anayati account, the name and email you authorize Apple to provide (which may be an Apple Private Relay address), and an encrypted Apple refresh token retained only for secure authentication, account linking or unlinking, and provider revocation when you delete your account.
• Age, jurisdiction, and compliance routing data: country or region signals, residency confirmations, age-band or age-threshold handling, parental-authority workflow data, and related review states where required.
• Profile and preference data: language choices, profile fields, study and personalization settings, interface preferences, publication preferences, and related user-controlled settings.
• Usage and interaction data: pages viewed, features used, clicks and selections, search activity, progression through flows, mentor or feature-quota usage, timing and engagement signals, and related interaction summaries about how you navigate and use the Service.
• Course, prompt, and user-content data: prompts, uploaded source materials, saved-course links, publication requests, rights-clearance confirmations, feedback, notes, answers, progress, ratings, preferences, and other account-linked interactions. Platform-generated courses, Paths, generated PDFs, and delivery assets are distinguished from these account-linked records, although any personal data contained in a generated output remains personal data.
• Billing and transaction data: subscription status, customer identifiers, invoice identifiers, refund-request records, tax country, billing profile data, and payment-related metadata supplied by Stripe or generated by the web billing workflow. For Android purchases, Google Play and Google Payments provide or generate the product, base-plan and offer identifiers, purchase token, purchase, acknowledgement, renewal, cancellation, expiry and refund status, and a pseudonymous or obfuscated account identifier used to bind the purchase to the correct Anayati account. Google handles the payment instrument; Anayati does not receive or store full card or bank-account numbers for these purchases. For iOS purchases, Apple supplies StoreKit product, transaction and original-transaction identifiers, the pseudonymous app-account token used to bind the purchase, and purchase, renewal, cancellation, expiry, refund and revocation state. Anayati uses these records to verify and maintain Premium entitlement state. Apple handles the payment instrument; Anayati does not receive or store full card or bank-account numbers for App Store purchases.
• Support, safety, and administrative data: support emails, moderation or compliance decisions, account-protection events, deletion evidence, and related records needed to operate or defend the Service.

4. Data We Collect Automatically

We automatically collect device, browser, network, and usage information needed to operate, secure, and improve the Service. This can include IP-address-related country routing signals, browser and device characteristics, timestamps, authentication and security logs, visited pages, navigation paths, feature interactions, click and selection patterns, search activity, timing or engagement signals, performance measurements, error or diagnostic events, and storage state tied to your session or preferences. If you enable iOS push notifications, we create a per-installation identifier and collect the Apple Push Notification service device token, linked to your account, to send notifications requested by or relevant to your account.

We also use cookies and similar technologies such as local storage and session storage. For details, see our Cookie Policy.

Depending on the feature, this automatic collection can also support account security, billing-return continuity, publication governance, signed-in service telemetry, optional public-site analytics and marketing measurement, and product diagnostics.

5. Mandatory Signed-In Service Telemetry

For signed-in accounts, Anayati uses a mandatory service telemetry model because the Service is designed to deliver personalized learning, personalization-aware safety handling, governed feature activation, and age/jurisdiction routing as core functions.

This signed-in service telemetry can include, depending on the account context and product path, search activity within the Service, visited pages, navigation through product flows, feature activation events, clicks and selections, timing or engagement signals such as time-on-page, quota-consumption signals, session continuity signals, performance and diagnostic events, and other product-operation data required to authenticate access, adapt the experience, personalize recommendations or adaptive behavior, prevent abuse, or enforce the applicable governance rules.

The exact runtime scope may be reduced according to age, parental-authority status, jurisdiction, or feature sensitivity. We do not ask for a separate optional analytics consent for this signed-in mandatory service telemetry because it forms part of the service model for authenticated use of Anayati.

6. Public-Site Optional Analytics, Marketing Measurement, And Similar Technologies

When you are anonymous or signed out, non-essential analytics, advertising measurement, conversion measurement, or similar public-site measurement technologies are handled separately from the signed-in mandatory service telemetry model. Where required by law, we ask for consent before enabling those optional public-site technologies.

If you refuse or withdraw that optional consent, the public site should continue to rely only on strictly necessary technologies, subject to what is technically required for the service you request. Refusal also disables optional Meta Pixel and Meta Conversions API measurement for future public-acquisition events.

Optional Meta measurement is limited to public acquisition and billing-confirmed conversion events such as page views on public routes, newsletter signup, public create-course intent, account registration, checkout start, and an initial paid subscription. We do not send course prompts, uploaded learning materials, generated course content, learning performance, OODA/cognitive telemetry, or raw payment card data to Meta for this measurement.

When Meta measurement is enabled, the browser Pixel can disclose the page URL and referrer, timestamp, IP address and related coarse location, browser or user-agent, device and network characteristics, Meta cookie or online identifiers such as _fbp and _fbc, and the configured event and limited event fields. Our server-side CompleteRegistration event for an eligible consented adult Google or Apple web registration sends a SHA-256 hashed internal account identifier, event identifier and timestamp, source URL, provider method, and completion status. Our server-side Subscribe event additionally sends the Stripe invoice identifier as an order reference, amount, and currency and may include the _fbp or _fbc identifier already stored in the browser. We do not add email, phone number, provider subject, tokens, IP address, user-agent, or raw click identifiers to the registration event. The checkout attribution copy expires after at most 24 hours and is deleted earlier after durable delivery handoff where possible. Any delivery copy is retained only while delivery is pending or retrying, and is removed at a terminal outcome, consent withdrawal, a GPC signal, or account deletion. Hashing supports matching and does not make the identifier anonymous for this purpose.

7. Why We Use Personal Data

• To create and manage accounts, authenticate users, and keep the Service secure.
• To provide the learning, creation, personalization, export, publication, and billing features you request.
• To route age, parental-authority, and jurisdiction rules and to reduce or block features when governance requires it.
• To operate the signed-in mandatory service telemetry model used for personalization, safety, fraud prevention, debugging, and service integrity.
• To process subscriptions, invoices, refunds, taxes, billing support, and related financial records.
• To publish, review, moderate, unpublish, de-index, or otherwise govern content and public surfaces you choose to use.
• To communicate with you about the Service, support, security, or legal updates, including push notifications you enable.
• To send product-news or platform-update emails if you opted in and completed any required double opt-in flow.
• To measure the effectiveness of public acquisition and marketing campaigns where you consent to optional marketing measurement.
• To comply with legal obligations and enforce our rights.

8. Legal Bases

Depending on the context and applicable law, we rely on one or more of the following:

• Performance of a contract when processing is necessary to provide the Service you requested, including account operation, core personalization, required signed-in service telemetry, exports, billing, and publication flows you initiate.
• Legitimate interests for platform security, fraud prevention, abuse handling, service improvement, administrative operations, public-surface integrity, and other business operations that are compatible with applicable law.
• Consent where required, including public-site optional analytics, marketing measurement or personalization technologies, and marketing emails where consent is the appropriate basis.
• Legal obligations where we must retain or disclose information under tax, accounting, consumer-protection, safety, or other legal requirements.

When certain data is required to enter into or perform the contract for the signed-in Service, you may be unable to create, maintain, or fully use the account if you do not provide or accept that required data handling.

9. How We Share Data

We share personal data only as needed for the purposes described in this Notice.

• Payment providers: Stripe processes web payments, subscription billing, invoices, and related payment metadata. Google's Play billing services process Android subscription purchases and provide the transaction state needed to grant, reconcile, cancel, restore, or refund Premium access. Apple's App Store services process iOS subscription purchases and provide the transaction state needed to grant, reconcile, cancel, restore, expire, revoke, or refund Premium access.
• Authentication providers: if you choose Google sign-in, Google processes the authentication flow. If you choose Sign in with Apple, Apple processes the authentication flow and supplies the identity claims you authorize.
• Email and communications providers: we currently use Azure Communication Services to deliver operational and marketing emails.
• Analytics, performance, and marketing measurement tooling: where enabled, public-site optional analytics and marketing measurement may use Vercel Analytics, Meta Business Tools, or similar providers.
• Hosting, storage, security, and infrastructure providers: we use infrastructure providers including MongoDB for application data storage, Azure Blob Storage for certain archived or governed files, and Azure Web PubSub for some realtime messaging flows.
• AI providers: learning, creation, transcription, speech-generation, and enrichment features may rely on Google Gemini, OpenAI, DeepSeek, Mistral AI, or xAI when those features are invoked. Mistral AI may process audio for transcription or generated speech where the user requests those features.
• Search and transcript-retrieval services: when you explicitly request a fact-check or create a course from a YouTube video, Serper may process a search query generated from the selected claim or context and return search results and URLs, while SerpApi receives the YouTube video ID and preferred transcript language to retrieve its transcript. These are supporting retrieval services, not AI model providers.
• Legal or business transfers: we may disclose data when required by law, to protect rights and safety, or in connection with a corporate transaction.
• Public sharing: if you choose to publish content publicly, that content and related publication metadata may be visible according to the audience and publication state you selected.

10. Third-party AI processing and your choice

When you use an AI-enabled feature, Anayati may send the data needed for that specific request to one or more of these named third-party AI processors: Google Gemini, OpenAI, DeepSeek, Mistral AI, and xAI. The AI processor used depends on the feature and availability, and supports generation, analysis, transcription, speech, or enrichment.

Depending on the AI feature you invoke, the data sent may include your display name; prompts, messages and questions; private course content, notes, answers, learning history, activity and preferences; uploaded files and filenames, including documents and images; image-edit inputs; microphone audio and transcripts; and text selected for speech generation. You provide some of this data directly, and Anayati retrieves saved account or learning data only when it is needed for the feature you requested.

We use this data to produce the response, transcription, speech, image edit, course material, or other AI output you requested, and to apply safety, abuse-prevention, and service-integrity controls. In the Anayati iOS app, before any of this personal data is sent, account activation presents the named AI processors, data categories, purpose, and protection commitment and records your explicit choice with the disclosure version and timestamp.

Accepting during iOS account activation permits these transfers from the Anayati iOS app. If you do not accept, or later withdraw permission, the iOS app remains inactive and does not send personal data from that app to the listed AI processors. Your Web and Android access is unchanged.

Separately from AI model processing, when you specifically use a fact-check or YouTube transcript feature, supporting retrieval services process only the request data needed to return the source material you requested. Serper receives a search query generated from the claim or context you ask Anayati to fact-check and returns search results and URLs. SerpApi receives the YouTube video ID and preferred transcript language and returns the available transcript.

Anayati requires each listed AI processor and supporting retrieval service receiving personal data on our behalf to apply the same or equivalent level of privacy protection described in this Notice, including appropriate confidentiality, security, purpose-limitation, and transfer safeguards.

In the iOS app, you may withdraw this permission at any time by opening AI Data Sharing in the footer and selecting Not now. Withdrawal deactivates the iOS app and blocks future transfers from it; it does not reverse processing already completed for a request you previously authorized. You may also contact contact@anayati.com to exercise applicable data-protection rights.

11. International Transfers

Some providers may process data outside your country, including outside the European Economic Area. Where required, we use appropriate safeguards such as contractual protections and transfer mechanisms recognized under applicable law.

This may be relevant in particular when we rely on providers such as Stripe, Apple, Google, Microsoft Azure, MongoDB, Meta, OpenAI, DeepSeek, Mistral AI, xAI, Serper, SerpApi, or other infrastructure, analytics, marketing-measurement, or AI-related providers with international operations.

For measurement and analytics services, Meta may act as our processor. For collection and transmission used for ad targeting or delivery, Anayati and Meta Platforms Ireland Limited may act as joint controllers, and Meta may then act as an independent controller under its own privacy terms. Meta Platforms Ireland Limited is located at Merrion Road, Dublin 4, D04 X2K5, Ireland. The applicable allocation depends on the Meta feature and account configuration.

Meta's Business Tools Terms currently permit Meta to retain Event Data for up to two years; audiences, if enabled in the Meta account, can remain until deleted. Anayati keeps consent and billing evidence under the applicable legal, audit, and dispute-retention rules.

12. Retention

We do not apply one single retention period to all data. Retention varies by governance lane, product function, and legal obligation.

• Account-core and billing records can be retained for longer legal and audit periods.
• Signed-in service telemetry, behavioral signals, and related summaries may use shorter or medium-length retention windows depending on the governed lane.
• Generated courses, Paths, generated PDFs, and their delivery assets may remain in the platform library after account deletion once the account association is removed. Uploaded source materials and private source-based courses may be deleted. Account-linked notes, answers, progress, ratings, preferences, prompts, and other personal interactions are deleted or anonymized subject to applicable legal retention; personal data contained inside a retained output remains subject to applicable data-protection rights. Publication, unpublish, de-index, and deletion-evidence records may persist where needed for compliance and follow-up.
• Marketing consent, double-opt-in, and unsubscribe evidence may be retained to prove compliance with communications rules.
• Optional marketing-measurement event evidence is kept only as long as needed for campaign measurement, consent evidence, billing reconciliation, and compliance follow-up.

13. Minors, Youth Protections, And Publication Controls

Anayati applies age-sensitive and jurisdiction-sensitive restrictions to certain personalization, durable state, high-scrutiny inference, and publication flows. For some account contexts, public publication is reduced, disabled, or review-gated by default.

Where parental authority or additional review is required, related features may remain unavailable until those steps are satisfied.

14. Security And Automated Processing

We use access controls, encryption in transit, credential protections, logging, minimization, and governance controls designed to protect personal data. No internet service can guarantee absolute security.

Anayati uses automated systems to generate learning content, personalize features, route age or jurisdiction controls, detect abuse, and support moderation. These systems can affect content, recommendations, feature availability, or review routing. We do not currently use solely automated processing to make legal or similarly significant decisions about public-site advertising measurement. You may contact us to request information or human review where applicable law provides that right.

15. Your Rights

Depending on your jurisdiction, you may have rights to access, correct, delete, restrict, object to, or export certain personal data, and to withdraw consent where processing relies on consent.

To exercise rights, contact contact@anayati.com. If you are in France or the EEA and believe our response is inadequate, you may also lodge a complaint with the competent supervisory authority, including the CNIL in France where applicable.

16. United States State Privacy Disclosures

Depending on the state and whether a law applies to Anayati, US residents may have rights to know or access data, correct inaccuracies, delete data, obtain a portable copy, opt out of sale, sharing or targeted advertising, limit certain sensitive-data uses, appeal a refusal, and receive equal service without discrimination. Requests may be submitted to contact@anayati.com; we may verify the requester and accept an authorized-agent request where required.

We do not sell personal data for money. Meta advertising measurement can nevertheless be treated as a sale, sharing, or targeted advertising under some US state laws. You can opt out through Cookie Settings or a supported Global Privacy Control signal. We apply GPC to Meta advertising measurement on the device and do not knowingly sell or share personal data of users under 16.

During the preceding 12 months, the categories disclosed to service providers or advertising-measurement partners may have included identifiers and online identifiers, internet or network activity, coarse location inferred from IP, commercial or subscription information, and preferences or inferences. The recipients and purposes are described above. We do not use or disclose sensitive personal information to infer characteristics for advertising measurement.

Legacy Do Not Track signals do not provide the same standardized legal instruction as GPC and are not used to override your saved choices. Use Cookie Settings or a supported GPC signal to exercise the advertising opt-out described above.

17. Changes To This Notice

We may update this Notice to reflect legal, operational, or product changes. The effective date at the top shows when the current version applies.

Ānayati in ChatGPT — public course previews

When you use the Ānayati plugin in ChatGPT, our service receives the tool inputs needed for the request: a search phrase and optional result limit, or selected course identifiers. We use these inputs to retrieve public course previews from Ānayati and return course metadata, thumbnail links and course links.

No Ānayati sign-in is required. These tools do not access learner accounts, learning progress, private courses, full lessons or PDFs. The integration does not receive your Ānayati account credentials or store a learner profile.

Vercel hosts this service. The current plugin application does not persist tool inputs or log their contents. Hosting and public website infrastructure may process technical request and security data, including network metadata. Search phrases are included in the URL of requests to our public catalogue endpoint and may therefore appear in infrastructure request records. The retention principles in this notice also apply to personal data processed for this service; this is not a promise that no logs exist.

ChatGPT’s processing of your conversation and use of connected tools is governed by OpenAI’s applicable policies. When you follow a course or image link to Ānayati, the website receives a separate request governed by this notice, including its applicable account, cookie and analytics provisions.

For questions or privacy-rights requests concerning Ānayati’s processing, contact contact@anayati.com