GDPR
Your data, in plain operational terms
What we hold, how long, and the exact screens you can use to exercise each right. No form letters required.
Who is responsible
Contexta is operated by the team behind contexta.my.id, which acts as the controller for the data in your workspace. There is no separate legal entity or DPO to address yet; the contact page lists the routes that reach the operators.
Rights and how to use them
Access
Profile → export your data, or download the whole corpus as Markdown or JSONL from the documents panel.
Rectification
Fix your account details in Profile. Document content is corrected by deleting and re-uploading the file, which rebuilds its index.
Erasure
Delete a document to remove its file and its chunks, or delete the account in Profile to remove the workspace.
Portability
Export is available in two machine-readable formats and does not require contacting us.
Restriction of processing
Revoke API keys and remove the documents you do not want queried. Retrieval only sees what is still indexed.
Object and withdraw consent
Disconnect Google sign-in or an integration, switch off non-essential cookies in the banner, or close the account.
How long things live
- Documents and their chunks: until you delete them, or until the account is closed
- API call logs: pruned after 90 days by a scheduled worker job
- Chat history: kept with your workspace and removed with it
Who else processes it
Supabase
Postgres database, authentication and file storage
Vercel
Serves the web application
Qdrant
Vector index, running on our own server
OpenRouter
Embedding model calls for indexing and search
DeepSeek
Answer and brief generation from retrieved context
Stripe
Payment processing, for the plans that open after the beta
This page describes how the product works today. Where it differs from the Privacy Policy, the Policy is the legal document and this page is the operational one.