Privacy Policy
Last updated: October 26, 2026
This policy describes Motoba’s data, purposes, recipients, retention and your rights. It accompanies the Terms of Use and Subscription. A French version is also available.
1. Data controller
Liam Augu EI, a French individual entrepreneur under the micro-enterprise regime, trading as Motoba, SIREN 131 718 066, is responsible for the application processing described here.
Business address: 26 rue Saint Léon, appartement 103, 31400 Toulouse, France. Contact: support@motoba.app; +33 7 65 74 97 00.
2. Data we process
- Account: name, email, hashed password if used, Google identifier if chosen, email verification, plan and creation/login dates. A last authenticated-use date and an inactivity-warning date support account retention.
- Questionnaire: study topics, languages and levels, tools and device, discovery source and free-text answers. Questions can be skipped. Older Anki answers and any referral code are also retained.
- Content: workspaces, decks, notes, fields, tags, formats, instructions, templates, styling, drafts, generations and media; format-assistant conversations (last 20 messages and a preference note of up to 400 characters), saved AI readings and resumable operations.
- Imports: files and content you choose, including Anki decks, formats, fields, tags and media read by your browser. Sync identifiers match local and external items. Where source analysis is available, it processes uploaded text, PDFs or images, selected pages, extractions and selected results.
- Settings: language, appearance, display, generation and Anki preferences.
- Billing: Stripe customer, subscription, payment and invoice references, plan, status, amounts and periods. Motoba does not receive complete payment-card numbers.
- Support: message category and text, email, plan, application version and technical context you choose to attach: page, browser, viewport, language, Anki status and time zone. The message is stored and emailed to support; you receive a copy.
- Usage and technical data: AI feature, provider, model, token/character counts, costs, quotas, technical outcome and duration; product results and activity days; IP addresses for rate limiting and access logs; error diagnostics. Financial AI records do not store prompts or responses. Separate resumable operations can retain content for the periods below.
3. Purposes and legal bases
- Contract: account, authentication, generation, storage, synchronisation, exports, subscription access and support. Data needed for these functions is necessary to provide them.
- Legitimate interests: security, abuse prevention, technical/cost monitoring, improvement and product statistics. You can skip optional questions and object to product statistics at support@motoba.app. Operational quotas, security and retention records remain separate.
- Legal obligations: GDPR rights and any legally required supporting documents. Records needed for a complaint may be restricted to handling it and defending rights for the applicable period.
- Consent: optional audience measurement and signup attribution. Refusal does not prevent use or signup.
Service emails cover verification, account recovery, welcome, quotas, support and retention notices. Stripe / Link also sends receipts and transaction communications. Motoba shows no advertising. Accepting terms does not allow audience cookies.
Authorised administrators can inspect decks and cards where needed for support. Access is audited without copying the content viewed. A diagnostic copied outside the application cannot be revoked there; it is not automatically sent to external AI.
4. Optional audience measurement
Production audience measurement runs only after your agreement. Google Analytics is a recipient distinct from Google sign-in. It measures public pages and guides, language, button activations and signup origins. Closing the banner is not agreement. Refuse or withdraw through Audience preferences on public/authentication pages and in Account settings.
This feature sends page type, language, published guide, button location and offer intent, random identifiers, approved campaign codes, a cleaned referring origin and technical metadata Google needs, including estimated country or unknown. URLs have no query strings or fragments. No email, Motoba account ID, authentication URL, studied content or free text is sent by this feature. Google Signals, User-ID, cross-domain linking, advertising and pre-consent replay are not enabled.
Choices last 180 days. _ga, _ga_* and motoba_audience_epoch cookies have an absolute 90-day maximum without visit-based renewal. Google explorations retain data for 14 months without activity reset; aggregated reports can last longer. Motoba signup attribution retains first and last non-direct origins for up to 365 days. Minimal versioned choice evidence lasts up to 180 days after expiry or withdrawal, without IP, browser or browsing history. Linking signup requires server consent checks.
Withdrawal stops this browser’s collection, discards queued events and clears audience cookies. It requests server-context revocation and removal of acquisition contributions. Failed requests remain pending for retry without restarting collection. Google deletion is a separate procedure; submission is not proof of completed erasure. Aggregates and recovery copies may remain. Without an anonymous identifier, we may be unable to locate a browsing epoch and do not reconstruct it from an IP address.
Withdrawal does not make earlier processing unlawful. Contact support@motoba.app about access or erasure. No BigQuery export is enabled.
5. How AI processes content
Generation and completion send the data the task needs: words, text, fields, format instructions and deck language/level. The assistant receives the format, recent context and its adaptation note; some operations use up to three saved cards as examples, limited to 1,500 characters for assistant examples. Source analysis, where available, may send selected excerpts or pages. Audio sends the text to read.
Motoba does not add your account name or email to AI requests. If you include personal information in content or messages yourself, it may be transmitted. Avoid unnecessary sensitive, confidential or third-party personal data.
Text: OpenRouter routes requests to the selected model’s provider. The code requires data_collection: deny and zdr: true to exclude training collection and require zero content retention at inference providers. Prompt logging and training use are disabled in Motoba’s OpenRouter account. These controls do not erase operational, security or billing metadata and do not guarantee EU-only processing.
Audio: ElevenLabs produces speech. Training use is disabled for Motoba’s account. This is not zero retention: synthesis history can remain. Its DPA does not require automatic erasure after 180 inactive days for self-service plans. Contact us to exercise rights through this provider.
Results can be wrong. Motoba does not make automated decisions about you producing legal effects.
6. Recipients and providers
- Vercel: website hosting, server functions configured in Frankfurt.
- Render: API and PostgreSQL in Frankfurt.
- Cloudflare R2: media storage in EU jurisdiction.
- OpenRouter and routed model providers: text generation and source analysis where available.
- ElevenLabs: audio generation.
- Resend: service and support emails, sending region Ireland.
- Sentry: error and performance diagnostics. Code filters cookies, request bodies, user, URL parameters and emails. This does not guarantee complete anonymisation of error messages or remove transport-level technical metadata.
- Grafana Cloud: availability monitoring and aggregate metrics, with no card content or account IDs in metric labels.
- Google: sign-in if chosen; separately, Google Analytics after agreement.
- Stripe / Link: subscription sales, payments, receipts and fraud prevention. For its own seller/payment activities it also acts as an independent controller under its Privacy Policy.
Internal access is restricted to authorised operations and support personnel. Legally required disclosures may be made to authorities. Motoba does not sell your personal content.
7. Transfers outside the EEA
European database/media hosting does not mean all processing stays in Europe. AI providers, Google, Stripe / Link and other international providers may process data in the United States and their subprocessors’ countries, including for operations and support.
Published agreements provide, depending on the recipient and flow, European Commission standard contractual clauses and applicable adequacy decisions for recipients actually covered. Safeguards and subprocessor details appear in the agreements of OpenRouter, ElevenLabs, Google Analytics and Stripe. Request copies or details about your data’s safeguards at support@motoba.app.
8. Cookies and device storage
- Authentication: access_token (30 minutes) and refresh_token (up to 7 rolling days, maximum 30-day session), inaccessible to scripts; csrf_token for session protection; oauth_state and motoba_oauth_completion for Google (5 minutes).
- Preferences: motoba_locale stores language for one year. Appearance and interface preferences stay on the device. Local/session storage can include work drafts, AI suggestions, display and Anki states until replacement, removal or the relevant storage session ends.
- Audience: motoba_audience_choice stores a choice and versions for 180 days; it alone is not server proof. After consent, motoba_acquisition_context binds the browser to its server context within the same absolute 90-day audience epoch. A minimal pending withdrawal may remain for retry. Google cookies and durations are described above.
- Strictly necessary service/requested-preference cookies do not require audience consent. Optional trackers require agreement. Motoba hosts its own fonts.
9. Retention periods
- Account and content: while used, until deletion or the inactivity process. After two years without authenticated use, free accounts without outstanding billing are emailed a warning, then deleted only after at least 30 more days without return. Admin and still-paid accounts are excluded from automatic deletion. Existing accounts receive a new two-year period when this tracking is introduced.
- Support: stored application messages are deleted with the account. Emailed copies are not erased by that button and follow handling of the support case; contact us to request erasure.
- Links and sessions: verification 24 hours, password reset one hour, sessions 7 days since renewal and at most 30 days since sign-in.
- Imports and source analysis: temporary sources and analysis state are available for 24 hours then collected by cleanup. Kept cards and media follow deck retention.
- Resumable fills: resumption up to 30 days; metadata up to 90 days after completion and an absolute 120 days from creation; bounded content receipts removed after application or expiry. Financial usage records have a separate lifetime.
- Product history and completed AI calls: 12 rolling months, purged daily. Product contributions are removed with the account. Costs may remain for those 12 months without account, quota-period and batch references; this does not guarantee anonymisation. Unresolved reservations require explicit resolution before removal.
- Administrative audit: 6 months; journey exports 24 hours; preparation audit 90 days.
- Sentry diagnostics: error and performance events are retained for 30 days on the current Developer plan, in the organisation’s European storage region. Aggregate issue counters can remain after event expiry.
- Logs and backups: Render access logs 7 days, database point-in-time restore 3 days and backup exports 7 days under the current hosting plan. Copies expire on their cycle after active-data deletion.
- Providers: Google follows the audience periods above. ElevenLabs retention is explained in the AI section and its DPA. Stripe / Link retains sale records under its own legal obligations; deleting Motoba does not automatically erase them.
10. Deleting your account
Request deletion in Settings › Account › Your data by confirming your email. This removes the account and its workspaces, decks, cards, formats, drafts, conversations, preferences, questionnaire, support messages, sessions and Anki links. Where a subscription must be stopped, this must succeed before local billing links are deleted.
Unreferenced media is scheduled in the storage cleanup ledger. Failures can delay physical erasure and are retried. Provider residual data, costs, audits, logs and backups follow the limits above. Audience withdrawal and erasure use a separate procedure.
Export decks first, for example as Anki packages, CSV or JSON. Account deletion does not delete anything from local Anki.
11. Your rights
Subject to GDPR conditions, you can access, correct, erase, restrict, object and receive portable data, withdraw optional consent and give instructions for data after death. Contact support@motoba.app to object to product statistics.
Change your name and delete your account in Settings. For a complete export, email change or other right, write to support@motoba.app. We normally respond within one month; any lawful extension is explained within that period. Identity evidence is requested only where there is reasonable doubt about the requester.
You can complain to the CNIL or your local supervisory authority.
12. Security, minors and changes
Stored passwords/tokens are hashed; session cookies are HttpOnly, public connections encrypted and actions protected against cross-site requests. No system is perfectly secure. Breaches are handled according to statutory notification duties.
Below 15, joint agreement from the child and legal representative is required where processing relies on this consent. Contractual capacity is separate and follows applicable law. Report an unauthorised child account for review and deletion where appropriate.
The date identifies this version. Substantial processing changes are announced before taking effect, with fresh consent where required.