1. Who is responsible
Onecord is operated by Tommy Kingsleigh in Farnham, United Kingdom. Contact support@onecord.ai for support, billing, privacy, safety or copyright enquiries.
Onecord's operator is the controller for account administration, payments, service security and its own product operations. Where an organization instructs Onecord to process member or customer data in a connected server or bot, that organization may be the controller and Onecord may act as its processor for that activity. The parties must agree any required data-processing terms separately; Discord and payment providers also have their own roles and notices.
This notice covers the Onecord web application and the features described here. Independent Discord communities and third-party services have their own privacy notices. The forthcoming iOS app will have its relevant privacy disclosures when it becomes available.
2. Information we process
Live voice features process microphone audio and transcripts with the AI provider to deliver the conversation. Onecord does not add call audio recordings to its application database; saved chat transcripts or messages can still remain in your history. Provider handling differs from our application storage.
Do not submit passwords, unrelated bot credentials, payment-card numbers, sensitive personal records or someone else's private data unless the feature requires it and you have a lawful basis. Uploaded images can reveal identities or sensitive details. We do not need precise location or identity documents for ordinary account use.
| Information | Purpose and source |
|---|---|
| Discord account profile | Discord ID, username/display name, avatar, email where supplied, locale and other profile fields returned by authorized OAuth scopes; used for sign-in, account display and billing identity. |
| Account and workspace content | Your prompts, chat history, uploads, generated images, bot files, server drafts, settings and saved tasks, submitted by you or created during your use. |
| Discord server and bot information | Authorized server/channel/role metadata, permissions, IDs and relevant message context for requested features; application credentials and server snapshots where you connect them. |
| Billing and Team records | Stripe Customer/payment/subscription references, billing contact and address, invoice history, plan and credit balances, usage costs, Team membership and seat allocations. |
| Activity, referrals and attribution | Account activity dates, bounded campaign labels, external referrer hostname, coarse browser/OS category, referral relationships and reward eligibility. |
| Technical diagnostics | Redacted error messages/stacks, normalized routes, environment/release, timestamps, request references and duration. Certain authenticated billing errors can retain an account association. |
| Website statistics | Short-lived in-memory visit references, reviewed static page paths, campaign labels, external referrer hostname, approximate country where supplied and broad browser/device categories; visible-tab time when available. |
| Reports and correspondence | Information you provide in a support, safety, privacy or copyright request, and records necessary to investigate it. |
3. Purposes and legal bases
Providing an account identity and requested content is necessary for the relevant service; declining it can prevent that feature from working. Optional uploads and voice use are your choice. We do not use a contractual basis merely to justify unrelated marketing. When relying on legitimate interests, we must balance those interests against your rights, with particular attention to young people.
| Purpose | Basis where UK/EU data law applies |
|---|---|
| Provide requested accounts, generation, saved projects and purchases | Performance of our contract with you. For member data processed for an organization, its documented instructions and applicable controller basis. |
| Protect accounts, prevent misuse, reconcile usage and investigate faults | Legitimate interests in a reliable, secure service, balanced against users' rights, especially children's rights. |
| Accounting, lawful requests and required safety disclosures | Legal obligation where an identified law requires the processing. |
| Necessary support and complaints | Contract, legitimate interests or legal obligation, depending on the request. |
| Non-essential marketing or storage requiring permission | Consent where required. It must be optional, specific and withdrawable; this notice is not that consent. |
| Service statistics and campaign effectiveness | Legitimate interests where justified and any separate storage/access permission or exemption required by local law. Cookie-free does not automatically mean exempt. |
5. International processing
Providers can process information outside your country, including in the United States. A UK/EU transfer requires an applicable adequacy decision or appropriate contractual safeguards, such as EU standard contractual clauses and the UK Addendum/IDTA where needed, with a transfer assessment. The provider inventory below alone is not proof those arrangements are in place.
Contact Onecord support for information about the countries, provider arrangements and safeguards applicable to your data. We may redact confidential details where legally permitted; your information rights remain available.
6. Retention and deletion
Settings → Manage account supports account deletion. The current flow checks subscription cancellation, removes linked Stripe Customer and saved image originals, deletes the account and associated sessions, and clears the session cookie. Some related records cascade; separately retained anti-replay, diagnostic, statutory or provider records can remain as described above. Removing a Stripe Customer does not necessarily erase invoices or provider records retained under law.
Deletion does not erase already published Discord content or copies others made. Local browser preferences, drafts and legacy caches can remain on a device; clear site data when appropriate, especially on shared devices. Where a legal exception or backup retention affects an erasure request, we will explain the relevant limitation. We do not claim every copy disappears instantly.
| Record | Current implementation / limits |
|---|---|
| Account, settings and saved content | Generally retained while the account exists or until you delete the relevant content. Account records have no automatic inactivity expiry. |
| Sign-in sessions | Up to 400 days, renewable on return near expiry. Sign-out removes that session; expired database rows are cleaned during session creation. |
| OAuth handoff records | Browser cookies generally expire after 10 minutes and are cleared by the callback; the login-attempt limiter expires after 60 seconds. |
| Authenticated activity days | A 365-day reporting window, pruned when activity is written; dormant rows can remain until the next write or account deletion. |
| Application error events/groups | A 30-day window, pruned on an admitted write. Quiet storage can retain expired rows until another write. Hosting logs follow separate provider retention. |
| Anonymous visitor records | Retained to prepare and review website usage statistics. The current collector has no automatic raw-event expiry; deletion requires administrative cleanup. These records do not identify returning visitors or link visits to accounts. |
| Referral anti-replay record | After account deletion, a separate Discord ID-only eligibility marker can remain indefinitely to prevent repeated referral rewards; it contains no profile or inviter history. |
| Payments, legal correspondence and backups | Retained as necessary for accounting, legal obligations, active disputes and recovery. Provider backup cycles and legally retained records can outlast deletion of an active account; ask support for the retention applicable to your request. |
7. Your rights and choices
Use Onecord support. We may request proportionate information to verify identity, but never your Discord password, full card number or bot token. Applicable time limits govern responses—normally one month under UK/EU data law, with a permitted extension for complex requests and an explanation. Rights have legal exceptions; an account, server or Team identifier alone does not entitle someone to another person's content.
- Ask for access to your personal data and correction of inaccurate information.
- Request erasure, restriction, or portability where the applicable conditions are met.
- Object to legitimate-interest processing and to direct marketing; withdraw consent without affecting earlier lawful processing.
- Use account deletion, subscription cancellation and browser site-data controls for the specific effects described above.
- Complain to the UK Information Commissioner's Office or your local supervisory authority, without first having to resolve the issue with us.
8. Young people and automated processing
Onecord's minimum age is 13, subject to higher local/platform requirements. We do not knowingly invite children below the applicable age to use the service. Contact the privacy or safety address if you believe an account is below that age. Do not send identity documents without a specific, secure and proportionate request.
Onecord does not provide a separate parent dashboard or a verified age-check service. Young users must meet the age rules and involve a parent or guardian where required. To report an underage account or a concern about a child's data, contact support with the relevant account identifier; do not send identity documents or harmful material unless a secure, proportionate process specifically requires them.
AI responses and automated routing can be wrong. Credit accounting and access checks are automated for service operation. Onecord is not offered as a tool for solely automated employment, credit, housing, educational admission, legal or other similarly significant decisions about people. If a restriction or other automated result materially affects you, request human review through Contact support.
9. Service providers
| Provider | Function and relevant data | Role |
|---|---|---|
| Discord | OAuth identity, authorized guild/application access, bot interactions and content you send to Discord | Connected platform with its own terms and privacy notice; not a substitute for Onecord's policies |
| OpenAI | AI text/code/image generation, routing and live voice; submitted content and relevant context, usage and safety identifiers | AI processing provider; API data handling and retention depend on the feature and provider terms |
| Stripe | Checkout, saved payment methods, subscriptions, top-ups, invoices, fraud prevention and refunds | Payment provider; roles differ between processing payment data and its own legal/fraud purposes |
| Cloudflare | Application/API Worker, D1 database and related hosted infrastructure when configured | Database, private image storage and hosted application infrastructure |
| Vercel | Web hosting/Preview functions and delivery where deployed | Hosting and delivery provider where Onecord is deployed on its infrastructure |
| Twilio | Operator incident SMS/calls from redacted diagnostic context, when enabled | Operational integration, not a product-user chat/messaging feature; review what identifiers can appear in diagnostics |
10. Storage on your device
Cookies, local storage, session storage and IndexedDB can keep information on your device. We explain them together because storage/access rules are not limited to cookies. Essential technologies support a feature you request; optional purposes need the permission or exemption applicable in your location. A label in this notice does not itself establish an exemption.
11. First-party inventory
The current visitor collector uses no cookies, local storage, persistent visitor ID or fingerprint. Its in-memory visit ID resets on reload. That does not automatically exempt all analytics or campaign attribution from privacy/storage rules. Development-only preview storage is not a promise that every listed item runs on every production page.
| Name / category | Purpose | Lifetime |
|---|---|---|
| onecord_discord_session | Opaque sign-in session; HTTP-only, Secure on HTTPS, SameSite Lax | Up to 400 days, renewed on return near expiry; removed at sign-out |
| onecord_discord_oauth_state | Bind the Discord callback to your sign-in attempt | 10 minutes; cleared by the callback |
| onecord_discord_oauth_return | Return to the requested dashboard or checkout after sign-in | 10 minutes; cleared by the callback |
| onecord_discord_oauth_invite | Carry an invite code you followed through sign-in | 10 minutes; removed on callback |
| onecord_discord_oauth_utm | Carry bounded signup campaign information | 10 minutes; removed on callback; attribution purpose needs separate legal review |
| onecord_discord_login_attempts | Limit repeated sign-in attempts | 60 seconds |
| onecord-balance-{account ID} | Remember Personal or Team billing selection | Session cookie; validated for each request |
| Appearance, panel width and composer drafts (local storage) | Restore requested display settings and unsent text on this device | Until overwritten, deleted by the feature or cleared in browser site data |
| Navigation/keyboard state (session storage) | Return from checkout and carry a selected action between pages | Current browser session |
| Legacy chat/cache storage (IndexedDB and local storage) | Local chat recovery/migration or feature previews where used | Until feature cleanup or browser site-data deletion |
12. Payments and other services
Stripe's payment UI may access device information or use its own storage for payment operation, fraud prevention and authentication. Discord handles storage on its own sign-in pages. Hosted resources can disclose ordinary connection metadata to their providers. Their current notices describe their own purposes and retention; Onecord must review which technologies load before a user opens those features.
We do not add advertising or marketing trackers through this legal-page change. If optional trackers are introduced later, they must not be enabled before the required permission, and their notice and controls must be updated.
13. Choices and limitations
Your browser can show, block and delete cookies and site storage. Clearing them can sign you out, remove unsent drafts and reset preferences; it does not delete your cloud account. Sign-out removes the active authentication session. Account deletion is a separate action.
Onecord does not currently provide a dedicated optional-cookie consent manager. Browser controls can block or clear site storage, and you can contact support about storage or analytics objections. Merely using the site is not consent to optional tracking. Where a purpose requires consent or another specific storage/access condition, that requirement continues to apply; this notice does not substitute for it.