Privacy Policy
v1 · October 2026
Draft for legal review — the operating entity name, registered address, registration number and privacy contact email go here before launch.
This policy explains what [entity TBD] ("Methora", Budapest, Hungary — the data controller) collects through methora, why, where it goes, and your rights under the GDPR.
1. What we collect
Account data. Your email address for magic-link sign-in; the name you optionally give your public creator profile. No passwords exist — there is nothing to leak.
Creator content. The source files you upload and the generated drafts derived from them. Source files stay private forever; only the published storefront text is public.
Order data. For purchases: product, version, price, status, an optional buyer email, and Stripe references (session and payment-intent identifiers). We never see or store card numbers — Stripe collects those directly.
Survey answers. Respondents answer without an account. We store the answers themselves against the campaign — nothing else (no name, no email, no tracking ID). Campaign reports aggregate answers; individual submissions are only visible as de-identified samples to the buyer.
Operational logs. Audit events (who did what), rate-limit records keyed by session or IP, and server-side error logs. These never contain passwords, access tokens, or card data.
Cookies. Exactly one: a 30-day httpOnly session cookie. No analytics, no tracking, no third-party cookies.
2. Why we process it (legal bases)
Contract — signing you in, processing purchases, delivering results, paying creators. Legitimate interest — security, fraud prevention, rate limiting, abuse detection. Consent — the upload-time attestation that you have rights to the source material, and its transmission to OpenAI for generation.
3. Who processes it (processors)
Vercel (hosting, US) · Convex (database, file storage and background jobs, US) · Stripe (payments and creator payouts, US/IE) · OpenAI (uploaded source text is processed to generate drafts, results and reports, US) · our transactional email provider for magic links. Each processes data under a data-processing agreement; US transfers rely on Standard Contractual Clauses or the EU–US Data Privacy Framework. We do not sell personal data.
4. Retention
Account data lives until you delete your account. Sign-in access is revoked immediately; durable background deletion removes your account email and name, public profile, sessions, old magic links, builder application, source files (including stored bytes and extracted text), drafts and creator-test runs with their inputs and outputs. Products without orders and unpurchased versions are deleted; retained products are unpublished. Queued private-content work is cancelled. A temporary deletion task holds the identity only until cleanup finishes. Orders, ledger, content-free receipts and purchased version snapshots are kept, as are paid results buyers still need and their delivery links. Pending paid results awaiting creator release are released to their buyers. Order, payment and version records are retained as required for accounting and tax (up to 8 years under Hungarian law). Buyer emails (including if you bought your own product) and identity embedded in purchased snapshots or paid results are retained with those buyer records; hash-covered purchased content is not rewritten by account deletion. Survey answers persist with their campaign; they carry no personal identifiers.
5. Your rights
You can access, rectify, port, restrict, object to, and erase your data. Deletion is self-serve from the dashboard; for anything else write to [privacy contact TBD]. You may also complain to the Hungarian data-protection authority (NAIH, ugyfelszolgalat@naih.hu) or your local DPA.
6. Automated processing
Uploaded sources are processed by AI models to generate product drafts, test responses, deliverables and reports. No automated decision produces legal effects about you; every publish and every creator_review release is a human action.
7. Security
TLS in transit, encryption at rest via our processors, hashed access tokens (raw tokens exist only in URLs), server-side validation, and least-privilege credentials. No system is perfectly secure; if a breach risks your rights we will notify you and the authority as the GDPR requires.