Legal
Privacy Policy
TalkNova is built around privacy. Here's what we collect, how we use it, and what you control.
Effective 14 November 2026 · Version 2026-11-14.1
Who this policy covers and how to contact us
TalkNova is the public-facing name of the service at talknova.site and its official applications and API. This policy explains our processing of account and service information. Contact talknovaa@gmail.com for privacy requests, complaints, rights questions or account deletion. An organization integrating our API is responsible for its own end-user privacy notices and lawful instructions.
Referrals and saved usage resets
The optional referral program uses website invitation attribution, verified Google account identifiers and content-free successful-use records to qualify genuinely new Free accounts. We use a resettable first-party device cookie and keyed network signals to detect suspicious patterns; shared networks alone are not proof of abuse. Temporary attribution is valid for24 hours. Temporary risk signals are removed after the configured retention period, initially30 days (administrator range7–90 days). Restricted reviewers can inspect recorded reasons and evidence; account-holder rewards views do not disclose other participants’ email addresses or private risk records. Pseudonymous Google identity history, referral relationships and append-only reward/redemption/audit records are retained to prevent repeat claims, reconcile earned rewards and handle appeals, including after account deletion where necessary for those purposes. Referral processing does not retain Google OAuth access tokens, passwords, raw IP addresses or a browser fingerprint. Saved legitimate resets have no expiry or storage cap and require explicit manual redemption; normal redeemed usage follows the current UTC month. Only the configured shared Free Text allowance is refreshed. See Rewards for qualification, monthly eligibility, review and program-pause terms. Contact support for an appeal or privacy request.
What is stored
Chat history is kept on your device and, while you are signed in, saved to your TalkNova account by chat sync, which is on by default and cannot be turned off. Synced conversations are stored with your account until you delete them; other users cannot read them. The owner administrator can read saved conversations through a restricted, audited, read-only history view for service administration and support. API requests are never saved as conversations automatically. Separately, request content and AI responses are copied to temporary support logs, enabled by default, for 72 hours. Authorized administrators can review those logs for support, troubleshooting, safety and security; each administrator access is recorded. The 72-hour limit does not delete saved chat history. Saved personalization is stored with your account. If you use Agents, their instructions, messages and run/tool records are stored on the server. Video jobs retain their prompts and settings; generated video files normally expire after 14 days. Clearing browser data removes local history, not synced conversations or these server-backed records. These features are not end-to-end encrypted; see the Privacy Policy for access, backup and deletion details.
Information we collect
We process information you supply, information needed to produce AI responses and technical records needed to operate the service.
- Account: verified Google email and account identifier, display name, profile image, sign-in sessions and account/plan status. Google handles your Google password; TalkNova does not request it.
- Requests: prompts, conversation context, responses, uploaded text/files/images, generation settings, tool instructions/results and other material you choose to send. Attachments or project content included in a prompt may therefore reach our processing infrastructure.
- Operations: account/key references, client category (web, Mac, Windows, Android or API), public model selection, timestamps, success/errors, estimated or reported token usage, USD deductions, limits, security and administrator-access events. Network infrastructure processes IP addresses, browser/user-agent and connection information; TalkNova does not promise every field is stored for every request.
- Purchases/support: plan grants, purchase/support correspondence, account email, payment amounts, account-bound orders, public receiving/sending addresses, network, token, signed references, transaction evidence and status, and purchase-term acknowledgement supplied through checkout or a private ticket. Purchased API credentials are stored as hashes with access-controlled encrypted delivery for up to24 hours, cleared earlier after acknowledgement; never expose a token publicly. Payment records are retained for reconciliation, disputes, financial records and legal obligations; account deletion can detach the account while retaining necessary transaction evidence. Cryptocurrency transactions may be public on their network. Never send a wallet seed, private key or unnecessary identity document.
Temporary support logs
Temporary support logs are enabled by default, without a per-user opt-out setting. Covered web, desktop, Android, API and supported agent requests can include prompts, conversation context, AI responses and limited attachment/tool descriptions, plus account or key reference, client category, model, status, timing and usage metadata. Some content is omitted or truncated. Authorized administrators may read relevant logs for support, debugging, safety and security, and each administrator access is recorded. Entries expire 72 hours after capture, are excluded from administrator reads at expiry, and are physically deleted by an automatic sweep normally running every 10 minutes. Expiry of support logs never deletes saved conversations. Authentication headers and cookies are excluded; recognizable secrets in message text are redacted, but detection is not perfect. Do not submit passwords, API keys or other unnecessary sensitive information. Statutory privacy rights remain available.
- A support record is a diagnostic copy of a request, not a complete archive of every chat. Re-sending earlier conversation context creates a new request copy with its own 72-hour expiry.
- Saved chat history is separate from support logs. The owner administrator can read saved conversation bodies, reasoning, tool calls and stored attachment data through a restricted, audited, read-only history view for service administration and support; other administrator roles cannot use that view. Recent support logs can contain the same words because request context is recorded independently.
- There is no per-user diagnostics toggle. You can contact us about access, deletion, objection or restriction rights that apply to you; these rights are not replaced by an account setting or waived by these terms.
Chat sync
Chat sync is on by default for every signed-in account on the web, desktop and Android apps and has no off switch. Saved conversations, including supported attachments and generated content, are stored with your account until you delete a conversation or choose "Delete all saved conversations" in Settings. Chats in desktop projects, tool activity and attached image files stay on the computer. Only devices with a compatible released sync feature participate; unsupported or older clients keep their history locally. The owner administrator can read saved history through a restricted, audited, read-only view for service administration and support. Other customer accounts cannot access your saved conversations through the service, but this is access control, not end-to-end encryption or a promise that authorized system operators cannot access server storage.
Phone and web control
Phone and web control is optional and off until enabled in a compatible desktop app. It sends coding-session messages, project/session labels, tool activity, permission requests and proposed changes to your account for viewing and control from compatible web/Android clients. Other accounts cannot access these records through the service. The AI runs on your computer; existing approval settings still apply. Disabling sharing stops future updates but does not delete earlier server records. You can remove a shared session without deleting your computer's own copy. Inactive sessions are purged after 30 days; completed/expired command records have shorter cleanup periods. Availability depends on the installed app version; newly implemented native features are not available until that version is released.
Agents, files and generated media
Agents store instructions, messages and run/tool records on the server. Connected services receive the data needed for the tools you authorize. Desktop project files remain on your computer unless content is sent in a request, shared session, tool call or upload; approval controls are not an operating-system sandbox. Video jobs store prompts, settings, progress and error records; generated video files normally expire after 14 days, but the job metadata does not automatically expire at the same time. Generated images and ordinary chat media are held on your device and, through chat sync, also stored with your account. Audio controls or remote-session capabilities are offered only where actually supported; a feature description does not imply every installed version includes it.
Imagine account history
Images generated while signed in can be saved to encrypted, account-owned Imagine history for up to 14 days, within storage limits. Image prompts and image bytes are encrypted at rest. Video history reuses the original jobs and media expiry. Download creations you want to keep. Removing an Imagine image deletes that gallery copy; hiding a video does not cancel its job or erase historical chat attachments. Local previews can remain in a bounded device cache. Content-free account change notifications keep signed-in devices current; notification payloads contain no chat, prompt, tool output or credential.
Historical speech files
Standalone text-to-speech was retired on 17 November 2026. Existing saved audio remains subject to the normal chat retention and deletion controls. Previously, speech generation sent submitted text through our backend to the selected speech provider. Fish Audio Free requests may be retained and used to improve its models; do not submit confidential information without an appropriate arrangement. Generated speech can be saved with your conversation and synchronized like other supported chat media. Stop ends local playback and cancels pending work where possible; an already submitted provider request may still consume usage.
Purposes and legal bases
We process necessary account, request and usage data to provide the service and fulfill our contract with you; security, fraud prevention, limited support diagnostics and service reliability may rely on legitimate interests where applicable law allows, after considering your rights; required financial/legal records rely on legal obligations. Where law requires consent for a particular activity, notice or acceptance of Terms alone is not that consent: we must obtain it before that activity. Chat sync is part of providing a signed-in account and has no off switch, but you can delete any or all synced conversations; remote sharing requires your affirmative feature choice. Default content diagnostics require an appropriate lawful basis; the absence of a toggle does not remove objection, restriction or other rights under applicable law. We do not use your conversations to train a TalkNova model.
No sale of personal information
TalkNova does not sell users’ personal information to advertisers, data brokers or other companies, and does not share it for cross-context behavioral advertising. Sending a request to AI processing infrastructure, using authentication/hosting services, or making a legally required disclosure is different from selling information. We do not operate an advertising profile or place behavioral-advertising trackers in the application. These statements describe TalkNova’s practices, not a promise that every external site you choose to visit has the same policy.
Third parties and international processing
Prompts and relevant attachments are transmitted through our backend to the model-processing infrastructure that supplies the chosen feature. This may include independent model service operators, not just the manufacturer named on a model. They may process content and technical metadata under their own retention, safety and service terms. Some text-processing routes retain prompts and responses for internal research or evaluation, and premium access on those routes can include model training under the operator’s account settings. A model name or successful request does not independently verify the intermediary’s underlying model weights or retention practices. Automated redaction is imperfect; these routes do not provide a zero-retention or no-training guarantee. We cannot promise zero provider retention or that a provider never improves its services using requests without verified contractual controls. Other recipients include hosting and network/security infrastructure, Google for sign-in, email/support providers and Discord if you choose to use our support/purchase server. Integrations or MCP tools you configure receive information you send to them. Processing can occur outside your country. Where transfer safeguards or processor contracts are required, they must be established; this policy is not a claim that every jurisdiction or transfer has already been certified. Do not send regulated, privileged or highly confidential information without an appropriate agreed arrangement.
Security and encryption
Public requests use HTTPS. The network proxy terminates TLS, so this is transport encryption, not end-to-end encryption. Access to the application database, backups and credentials is restricted; administrator support-log access is authenticated and audited. Backups are encrypted using a key whose private part is kept separately from the server. The live SQLite database is not application-level encrypted: authorized application/system operators and a compromised host could read stored content. Device-local history may also be readable by people or software with access to your device. Redaction and access controls reduce risk but cannot guarantee confidentiality or perfect security. Keep your devices, account and personal API keys secure; report suspected incidents to our contact email.
Operational analytics
For reliability, usage administration and security, TalkNova records account or custom-key request metadata such as public model ID, client category, subscription tier, request time, duration, status, token totals and usage charges. This separate analytics stream excludes prompts, replies, credentials and authentication headers. Bounded individual metadata is retained for up to 30 days. Aggregate request, registration, page-navigation and account-activity summaries are retained for historical charts. Page analytics store only approved page paths, without URL queries, prompts, replies or credentials; navigation views are not unique visitors. Historical tracking gaps are shown as unavailable. Authorized administrators can review and export this metadata; exports and sensitive administration are audited. These records do not change the separate 72-hour support-content logs or saved-chat retention.
Retention, deletion and backups
Retention depends on the purpose, not one universal three-day rule.
- Website project workspaces preserve original files, binary assets and edited files in encrypted, account-and-conversation-scoped temporary storage. Workspaces expire after 24 hours without a successful import or edit, with a maximum of seven days after creation; generated downloads and earlier text-only attachments expire after 24 hours. Expired files become unavailable immediately and are physically removed by a sweep normally every 10 minutes. Temporary workspaces, artifacts and extracted uploads are excluded from routine backups. Supported tests/builds run only on a disposable, restricted, no-network copy; secret files are excluded from AI reads and execution, but remain in owner downloads. File names, quoted snippets and AI responses saved in a conversation follow saved-chat retention; workspace expiry does not delete your chats.
- Active support-log access ends at 72 hours after capture; normal automatic physical cleanup follows within the next scheduled sweep. Database secure deletion reduces residual free-page content, but is not a guarantee of forensic erasure from every storage layer.
- Saved synchronized history remains until deleted. Clearing browser storage does not delete server copies, and chat sync cannot be turned off. Conversation deletion leaves content-free synchronization tombstones so other devices do not recreate it.
- Optional shared coding sessions expire after 30 days of inactivity; completed/expired command records normally have a one-day cleanup period. Agents/personalization and video-job metadata have no blanket 72-hour expiry and can remain while the account or feature is in use; use feature controls or request deletion.
- Operational database backups normally rotate after 14 days on the server, with encrypted off-server copies normally retained up to 30 days. Prior backups or restricted release/recovery snapshots can retain older deleted content until their retention or a justified legal hold ends. They are not available in the normal support-log viewer. Restoring a backup requires reapplying deletion/expiry before ordinary access. We do not promise immediate removal from every backup or immutable cryptocurrency record.
- Account, usage, financial, fraud/security, agreement-acceptance and complaint records may be retained where necessary for legal duties, resolving disputes and protecting rights, subject to purpose and access restrictions. We will explain applicable exceptions when handling a deletion request rather than silently promising complete erasure.
Your controls and privacy rights
Use Settings to manage saved personalization, delete individual/all synced conversations, and revoke or rotate your personal key. Contact talknovaa@gmail.com from your account email to request access, correction, deletion, a portable copy, restriction, objection or withdrawal of a consent you previously gave, where applicable. We verify requests proportionately and may need to retain legally required records; we do not ask for passwords or API keys. You may complain to your competent data-protection authority. Applicable response deadlines and appeal/non-discrimination rights remain intact. Account deletion is handled through verified support and removes supported live content records; it does not erase other users’ lawful records, public blockchain entries or all backup copies immediately. Native device-local content must also be cleared on the device.
Children and sensitive information
TalkNova is not directed to children under 13. Do not create an account if you are below the minimum age permitted by the Terms or local law. Minors who are otherwise eligible need a parent or guardian’s permission and supervision. We do not claim that an age statement alone satisfies children’s privacy law. If we learn we processed a child’s information without a required legal basis or parental authorization, we will investigate, restrict the account where needed and arrange appropriate deletion. Contact us with a child-privacy concern without sending unnecessary sensitive details.
Policy versions and material changes
The effective date and version appear on this page. We provide a visible service notice for material changes and record an account-linked acknowledgement where implemented. A new use requiring legally valid consent must wait for that consent; continuing to use TalkNova does not waive mandatory rights or automatically authorize incompatible new processing. Archived policy versions and acceptance records are retained for accountability.