Privacy, in plain language.
What we process, where your information goes, and the choices you have.
Business details and policy approvals are still being finalized. New production subscriptions remain unavailable until the required launch checks are complete. No commercial refund window is promised by this draft.
Who operates this service
Plainspoken is the product name. The legal operator has not yet been supplied.
The business mailing address and operator country are pending.
A verified, monitored support address is required before paid subscriptions open.
Your conversations and the AI provider
Plainspoken stores conversation titles and message text in its database to provide saved history. When you request a reply, the server sends your current message, relevant recent conversation context, and service instructions to Venice AI. Context may be shortened to fit the request limit.
Venice AI processes that text to generate a response under its own terms and privacy policy. Its handling may depend on the selected model and service. We do not extend a provider’s marketing claims to the whole Plainspoken service.
We do not promise end-to-end encryption, zero retention, anonymity, or that every provider uses the same training or retention practices. Do not submit passwords, API keys, card details, or confidential information you do not want processed by the service and its providers.
Accounts, infrastructure, and service records
Production email authentication uses Supabase. Account identifiers, email addresses, conversations, usage, and billing records are stored in the configured PostgreSQL database. The application runs on Vercel, which processes requests and associated network and technical data to deliver the service.
The optional local development mode uses a local SQLite database and an unverified demo identity. It is not production authentication and must not be used for real customer accounts.
An essential signed session cookie recognizes your browser, enforces trial limits, and links conversations to your account. Account sign-in also uses authentication cookies. Service records include registration and first-response milestones, timestamps, model identifiers, token counts, cost estimates, subscription status, and rate-limit signals. These internal records support account operation, abuse controls, billing, and service measurement even when optional marketing analytics are declined. Internal event records do not contain conversation text.
Payments
Stripe hosts checkout and the billing portal and processes payment details. Plainspoken stores customer and subscription IDs, invoices, payment and refund amounts, and verified billing status to manage access and reconcile payments. Full card details are handled by Stripe. A return from checkout alone does not activate a subscription.
Optional analytics and advertising attribution
With consent, we collect marketing visits and campaign attribution: allowed campaign parameters, landing pathname, Google click identifiers, and first and last attributed visits. Configured Google Analytics and Google Ads integrations may receive approved event data and verified purchase data to measure acquisition. Conversation text is not included in these events.
Optional marketing collection is off until you accept. Declining does not prevent chat. Change your choice here: . Withdrawal stops future optional collection and suppresses undelivered marketing conversions; it does not automatically erase previously delivered records. Essential service, security, and financial records continue to be processed.
Retention and deletion
Retention periods for account data, inactivity, financial records, provider processing, hosting logs, and backups are still pending operator confirmation. No fixed deletion deadline or backup purge schedule is promised. These details must be confirmed and approved before production payments open.
Saved conversations remain available until deleted, subject to the approved retention policy. Delete individual conversations from the sidebar or request account deletion in account settings. Resolve active billing first; account deletion is blocked while billing remains active. Financial records needed for accounting, security, or legal obligations may be retained separately.
Deleting a conversation removes it from the application’s active conversation history. It does not itself erase provider records or immediately remove backups. Requests concerning those records follow the relevant provider and approved retention policies.
Your requests and changes to this policy
Use contact support to request access, correction, or deletion. We may verify ownership before acting. Rights and obligations depend on your location. Service providers may process information outside your country. This service is intended for adults aged 18 or older.
Material changes will be reflected in this policy and communicated where required. The effective date appears above once the operator approves the policy.