TaleVein Privacy Policy
Effective date: 14 November 2026
This policy does not authorize a new use of previously collected information where additional notice or consent is required. We provide that notice or obtain that consent before making the change.
QomoArch LLC ("TaleVein", "we", "us") provides the TaleVein writing app at app.talevein.com and website at talevein.com (the "Service"). This policy explains the personal information we collect, its sources and uses, recipients, retention, and your choices. "Your Content" and "Output" have the meanings given in our Terms of Service.
United States launch. Our accounts, subscriptions, and app services are currently offered only to eligible customers in the United States under our Terms of Service. This Privacy Policy still explains how we handle information collected from website visitors or others who contact us, including from outside the United States. Service eligibility does not limit privacy rights that applicable law gives you.
1. Key points and who is responsible
- You retain your rights in your writing. We do not sell manuscripts or personal information and do not use Your Content or Output to train our own AI models.
- We do not routinely read your stories. The limited human-access exceptions appear in section 4.
- AI features send relevant content to model providers. Local storage does not prevent those transfers or the separate server copies described below.
- Novel files have an additional layer of encryption, but it is not end-to-end encryption against TaleVein. We can access the keys needed to read encrypted work.
- Deleting a novel does not automatically delete the corresponding AI-request history. Account closure also removes the key needed to open encrypted local novels: export readable copies first.
- Optional signup and advertising measurement is off until you allow it. You can decline or withdraw through Privacy choices. Necessary service functions, security checks, and error reporting still process technical information.
QomoArch LLC is responsible for deciding how and why personal information is processed for the Service, except where a provider independently determines its own processing as described below. Contact us at support@talevein.com, or QomoArch LLC, 30 N Gould St Ste N, Sheridan, WY 82801, USA.
2. Information we collect and where it comes from
Information you provide
- Account and profile information: email address, name, profile image, and optional details such as a biography or gender. Our authentication provider processes sign-in credentials and verification codes. We do not receive your password.
- Writing and uploads: manuscripts, notes, world and character information, prompts, instructions, character conversations, reference material, and uploaded images, audio, video, and documents, according to the features and storage mode you use.
- Voice input: microphone audio you submit for transcription and the resulting text. We send the recording for transcription and do not retain the recording as an account file. Text incorporated into a prompt or saved work follows the retention applicable to that material.
- Purchase information: plan or credit purchase, payment references, amounts, currency, tax information, transaction status, refunds, and associated billing details. Stripe collects payment details and billing addresses; its checkout may also request an address labeled as a shipping address. These payment addresses may differ from your residence. A card's issuing country does not, by itself, determine eligibility under our US service-area rule. We do not receive your full card number or card security code.
- Communications: support requests, complaints, feedback, and the information needed to handle them. If you make a rights or infringement request, this can include identity, authority, and contact information needed to assess it.
Information received from providers
Where you choose a supported social sign-in, the identity provider supplies account information such as your name, email, and profile image. Our authentication provider supplies account and sign-in status. Our payment processor supplies payment and subscription records. AI providers return Output and processing information. We do not buy personal-information lists from data brokers.
Information generated through use
- AI request records: prompts, relevant context, the provider and model used, results, status, and usage or billing information.
- Account and usage records: settings, plan benefits, coin and diamond transactions, request times, and records of agreement to legal terms, including the version, time, and source of agreement.
- Technical and security information: IP address, browser and device details, request information, sign-in sessions, and information used for abuse prevention, rate limits, and incident investigation.
- Optional measurement: if you consent, we record a random visitor and journey reference, signup-stage events, a broad device category, campaign tags and the advertising click reference from your arrival link. We associate a completed registration with your internal account reference to measure conversion. We do not collect form contents or writing through this feature.
- Diagnostics: error reports, page addresses, browser details, and recent interactions with the app. We limit personal information in these reports, but a report or support message can still contain it. Avoid including manuscript passages or sensitive information in support reports unless needed.
You may decline optional profile information or features that require additional processing. Account, payment, and request information necessary for a chosen function is needed to provide that function.
3. How we use information
We use personal information for the following business and service purposes:
| Purpose | Information involved |
|---|---|
| Create and manage accounts; save and retrieve work; provide requested AI functions and exports | Account, content, requests, results, settings |
| Process purchases, subscriptions, credits, and billing support | Account, transaction, usage, correspondence |
| Protect accounts and the Service; prevent fraud and investigate specific abuse or rights reports | Technical, account, transaction, and relevant reported material |
| Diagnose errors and improve reliability and usability | Diagnostics, technical and feature-use records; this does not authorize training on manuscripts |
| Respond to support and rights requests; send account, security, and service notices | Contact, account, correspondence, relevant request records |
| Comply with tax, accounting, lawful-disclosure, and other legal requirements; establish or defend claims | Relevant account, transaction, agreement, and other required records |
| Send optional marketing communications, if offered and you opt in | Contact details and consent record; you may opt out of those communications |
With your consent, we also measure where visitors leave the signup process and which advertising visits lead to registrations. This choice is separate from the information needed to create your account.
We do not use Your Content or Output for our own model training or advertising profiles. We do not make solely automated decisions intended to produce legal or similarly significant effects about you. Automated technical controls, such as rate limits and bot checks, still operate. You can contact support about an account or payment restriction.
Sensitive information about real people. Fictional themes are not automatically personal information, but identifiable people's health, beliefs, sexual life, biometric identifiers, or criminal-history information can receive special legal protection. Avoid submitting unnecessary sensitive information or third-party confidential material. You must have lawful authority for what you submit. We handle such information for the purposes described in this policy, subject to applicable law. Accepting the Terms does not replace any separate consent or other legal requirement for our processing.
4. Manuscripts, local mode, and human access
Human access. Our systems process content automatically to provide the Service. TaleVein personnel do not routinely read your manuscripts. Human access to story content is limited to:
- assistance you ask us to provide, limited to the material relevant to that request;
- a legal requirement, such as a valid court order; where legally permitted, we notify you before disclosure;
- investigation of a specific report that content violates our Terms, limited to what is reasonably needed for that investigation.
These limits govern TaleVein personnel. Provider processing is explained in sections 5 and 6. We do not represent that provider security or legally required review can never involve a person.
Local mode. The manuscript folder you select is stored on your device rather than synchronized as a cloud manuscript. However, content sent in AI requests and their results is separately stored on our systems. Uploaded and generated media also uses server storage, and PDF exports involve server processing. A passage in a local novel can therefore also exist in one of those separate records.
Cloud mode. Saved novel versions and the working draft are encrypted before cloud storage. Some information is outside that additional encryption, including novel titles, folder and version names, writing instructions, and story-analysis results used to organize the work.
Access to encrypted work. This encryption is not end-to-end encryption against TaleVein: we can access the keys needed to read encrypted work. Sign-in and access to your account key are also needed to open encrypted local novels. Closing your account deletes that key and can make those files permanently unreadable. Export readable copies before closure. Our limits on human access still apply.
Other copies. New private object-storage copies of AI requests and results are encrypted on our servers with your account's content key. Existing copies may remain in their previous format until their retention period ends. This is not end-to-end encryption against TaleVein, and providers can read the content they process. Separate database records and media have different protections and retention. Someone who receives a valid private media link may be able to use it while it remains valid. Do not share it with an unintended recipient.
Exports. Most exports are prepared in your browser. PDF exports send the book text to our servers, where the processing copy and generated PDF are kept for 7 days. Exported files you retain or publish are under your control and may contain personal information or external resources.
5. AI providers and training
An AI request contains the input and context needed for the selected task, which may include manuscript passages, character and world information, instructions, reference images, or media. These can be readable to the provider even if the saved novel is encrypted. Output may itself contain personal information.
We use external AI services, including OpenRouter and OpenAI. OpenRouter sends requests to the company operating or hosting the selected model, which may differ from the model's developer. Voice transcription uses OpenAI. Depending on the feature and model, processing may occur in the United States, China, Europe, or another country; section 7 explains international processing.
Training controls. TaleVein does not use Your Content or Output to train its own models. Both paid and free requests we send through OpenRouter exclude providers that use submitted data for training, and OpenRouter's optional storage of prompts and responses is disabled. This does not mean that processing involves no temporary storage, security review, or legally required retention. Our own request copies have separate retention below.
OpenAI does not use data submitted through the services we use for model training by default. Its published policy lists no retention of recordings for the voice-transcription service we use; other AI features may have different retention periods and exceptions. Provider handling also depends on the applicable service agreement and feature. See OpenAI's data controls and OpenRouter's provider privacy information.
Service providers also temporarily process requests and results to deliver them to you and recover interrupted delivery. These copies are separate from your AI-request history and do not necessarily disappear as soon as a response finishes. Section 8 addresses retention.
6. Who we share information with
We share information with the following categories of service providers as needed to operate the Service. Providers acting on our instructions process it for those functions under applicable contractual and legal requirements. Some providers, including our payment processor Stripe for fraud prevention and payment compliance, also act independently for purposes described in their own privacy notices.
| Type of provider | Information shared and purpose |
|---|---|
| Cloud hosting, storage, and content-delivery providers | Account, content, request, transaction, and technical information needed to host the Service, store work and records, and deliver files and exports |
| Account authentication and communications providers | Account, profile, sign-in, and technical information needed to verify identity, manage sessions, and send sign-in and security messages |
| Payment and financial-service providers | Payment, billing, subscription, and transaction information needed to take payments, calculate tax, prevent payment fraud, and handle disputes |
| AI generation and voice-transcription providers | Inputs, relevant manuscript context, reference material, recordings, results, and usage information needed to provide the AI features you request, as explained in section 5 |
| Live-response delivery providers | Requests, results, account references, and technical information needed to deliver AI responses and recover interrupted delivery |
| Security and error-reporting providers | Account, access-protection, technical, and diagnostic information needed to protect the Service, prevent abuse, and investigate errors |
| OpenAI advertising measurement, only with your consent | Completed-registration event, event time, unique event reference, advertising click reference and a page URL without query parameters. We do not send names, email addresses (including hashes), manuscripts, prompts, or other writing through this integration. We set the event opt-out for future user-level personalization |
| External font and diagram-editor providers | Technical connection information, such as IP address and browser details, when you load their resources. The embedded diagram editor operates in your browser; we do not send diagram content to its provider for storage |
External font requests arise from certain book previews or exports; our landing website serves its own fonts. Section 7 explains processing locations. You may contact us for information about the recipients of your personal information, including their identities where applicable law entitles you to them.
We may also disclose information:
- at your instruction, for example when you export, share a link, or publish through another service;
- to comply with applicable law, a valid legal demand, or necessary protection of legal rights and safety, subject to the limits on human access to stories above;
- to relevant parties when handling rights complaints, including notice or counter-notice contact details where the applicable process requires them;
- in connection with a merger, acquisition, financing, reorganization, or transfer of the business, with confidentiality and other safeguards appropriate to the transaction. We give notice before a materially different privacy policy applies.
We do not sell personal information or share it for cross-context behavioral advertising. We do not disclose manuscripts for a provider's unrelated advertising use.
7. Where information is processed
QomoArch LLC is a United States company. Although our app services are currently offered only to eligible US customers, we and our providers may process information in the United States and other countries. AI features can involve the locations described in section 5. A US-only customer market does not mean that all information stays in the United States.
Privacy laws and available protections can differ by country. We handle information as described in this policy and must meet any applicable legal requirements for its processing or transfer. Your acceptance of the Terms does not waive those requirements.
Contact support@talevein.com for information about where your personal information is processed and any applicable transfer safeguards.
8. Retention and deletion
Different copies have different retention. Deleting one item does not automatically erase every record that contains some of its information.
The table gives fixed periods where specified and the criteria used for other records. For those other records, retention depends on the time needed for the stated purpose, the relevant service's storage and recovery cycle, and any applicable legal duty or specific dispute. We do not retain personal information for longer than reasonably necessary for those purposes. A request to delete an account is handled under the process below; it is not a promise that all provider records or backups disappear on the same day.
| Information | Retention and important exceptions |
|---|---|
| Account and profile information | While the account is open, followed by the account-closure process below |
| Cloud manuscripts | Until you delete the manuscript or close the account; deletion of its storage does not delete separate request, billing, diagnostic, or backup records |
| Media and other uploaded or generated files | Until deletion or account closure. Deleted files can be restored from trash for 30 days and are erased from storage about 7 days later, including where trash is emptied sooner. File-name and size records remain until account closure |
| Private object-storage copies of AI requests and results | Available for 7 days after the generation or agent run finishes, then removed by scheduled cleanup. This includes copies containing passages from novels you have already deleted. Save any Output you wish to keep in your own work before then. Active generations do not expire based on their creation date |
| AI-request database records | Until account closure, including usage and delivery metadata and any prompt or story passages stored in those database records. The 7-day object-storage rule does not erase these separate database copies. They support recovery, checking charges, and investigation of problems |
| PDF processing copies and generated PDFs | 7 days |
| Billing and usage records | Retained after account closure for tax, accounting, fraud prevention, dispute handling, and legal claims. The applicable recordkeeping duty and claim period determine the required period; identifying account fields are removed as described below |
| Agreement and account-closure records | Retained after closure as described below; no fixed deletion date currently applies |
| Error reports and diagnostics | Retention depends on the report's age, the diagnostic service's event-history period, and the time needed to investigate the relevant error and check a fix. Records needed for a particular unresolved incident, complaint, or legal duty can be retained separately for that purpose |
| Hosting and security logs | Retention depends on the type and age of the log, the hosting or security service's log-history period, and the time needed to detect and investigate abuse or service failures. Evidence preserved for a particular incident or legal claim follows the needs and applicable time limits of that matter |
| Database backups | Deleted information may remain until the backup or recovery copy containing it expires or is replaced. The period depends on the recovery history needed to restore the service and the backup schedule; separate recovery copies can have different expiry dates. Deleting an active record does not immediately remove older backup copies |
| Temporary AI-delivery copies and related provider records | Retention depends on the time needed to deliver or recover a response, the delivery service's expiry and message-history settings, and investigation of a failed delivery. Related provider security or legal records can follow a separate period. These copies are distinct from the account's AI-request history described above |
| Optional measurement | Your consent or refusal is remembered for 180 days. Advertising click references expire 30 days after the click is recorded. Detailed journey, attribution and delivery records expire after 90 days. Scheduled cleanup removes expired records; expired consent and click references are not eligible for new collection or attribution. We retain daily totals without visitor, account or click identifiers |
| Support and rights-request correspondence | For handling the request and necessary follow-up, and where needed to document a complaint, comply with a recordkeeping duty, or establish or defend a legal claim; the purpose and applicable claim period determine retention |
Closing your account. Request closure at support@talevein.com. We verify the request and delete account details, stored content and files, AI-request copies, and the associated authentication-provider account within one month of your request, subject to legal retention exceptions and the backup retention described here. Where we cannot erase particular information because the law permits or requires its retention, we explain the basis when responding.
We retain payment and usage records needed for the purposes above with your account name and email removed; evidence of which terms you accepted and when; and limited account identifiers, including a protected reference derived from your email address, to prevent a deleted account from being reconnected. These records can still be personal information even without your name or readable email address. We do not treat them as anonymous or use them to recreate your manuscript.
Backups may retain earlier copies until their configured history expires. Provider-controlled records may also follow their independent legal obligations. We do not promise erasure of a file you exported to someone else or published on another service.
Export before closure. Closing the account deletes the key used for both local and cloud novels. TaleVein can no longer open encrypted local novels after that deletion, even though the files remain on your computer. Cancelling a subscription alone does not request account deletion.
9. Security
We use encrypted connections, the storage protections described above, sign-in verification, and access controls to protect information. Access to systems is limited to people who need it for their work, subject to the restrictions on story access. No service can guarantee complete security or recovery from every incident.
Protect your device, account, backup copies, and exported files. If an incident triggers a duty to notify affected people or authorities, we provide the notifications required by applicable law. Report suspected account or data-security problems to support@talevein.com.
10. Your rights and how to exercise them
You can manage supported profile information in the app, export your writing, cancel subscription renewal, and contact us to request access, correction, or account deletion. Exporting a manuscript is different from requesting a copy of all personal information we hold.
Send privacy requests to support@talevein.com, preferably from your account email. If you no longer control that email, tell us so that we can consider another appropriate way to verify you. We request only the information reasonably needed to verify identity or authority and protect others' information. An authorized agent may act for you with appropriate proof of authority.
We respond within one month, and any shorter period required by applicable law. If a legally permitted extension is necessary, we explain it and the reason within the original response period. We do not charge for ordinary requests. If a request cannot be fulfilled, we explain the applicable reason and available review or complaint options. We do not retaliate against you for exercising privacy rights.
Rights under US state laws
Where applicable state privacy law covers our processing, rights may include knowing and accessing information, correcting or deleting it, receiving a portable copy, and opting out of sale, targeted advertising, or certain profiling. Some laws also provide rights concerning sensitive information and appeals of denied requests. We do not sell information, share it for cross-context behavioral advertising, or use it for targeted advertising; those activities therefore do not require you to submit an opt-out to stop them.
To appeal a denied request where that right applies, reply to our decision or email support@talevein.com with "Privacy appeal" and the relevant request reference. We review the appeal, respond within the applicable statutory period, and provide information about further complaint rights required by law.
The categories collected in the preceding 12 months, to the extent you used the relevant features, include identifiers and account information; commercial and billing records; internet or technical activity; audio and other content; and personal information that may appear in prompts, manuscripts, or Output. Sources, purposes, recipients, and retention are described in sections 2 through 8. Sensitive categories can arise in user-supplied content or authentication and payment information. We use them for the disclosed service, security, and legal purposes rather than unrelated advertising or sensitive profiling.
Additional rights
You may have additional rights under applicable law. Contact us to exercise them. Our US-only service eligibility does not remove rights that apply to information we have already collected, and you do not have to be eligible to open an account to make a valid privacy request.
11. Cookies, local storage, and external resources
We use a first-party cookie to remember your optional measurement choice. When you allow measurement, it also links consenting visits on our website and app through our backend. Optional session storage carries a random journey reference across signup navigation. We do not load an OpenAI advertising pixel script or automatically collect form fields. Choose Privacy choices on the website or app to decline or withdraw. Withdrawal stops future collection and prevents unsent conversion reports; a report already sent or in flight cannot be recalled by changing the choice. Your ability to register and use the Service does not depend on accepting measurement.
We also use browser storage and provider functions to operate the Service:
- Our authentication provider uses cookies and related storage for sign-in and session security.
- Our security providers perform bot checks and may use storage associated with that function.
- Stripe's payment interfaces use their own cookies and technical information for payment and fraud prevention.
- The app stores your preferences, local-folder permissions, and information needed to recover unfinished requests. Some local records include story or character names.
- Certain book previews or exports load external fonts, and the embedded diagram editor loads from another provider. Loading these resources sends technical connection information, such as an IP address and browser details, to the provider. The landing website serves its own fonts.
Browser privacy signals. TaleVein does not currently change its own data collection in response to the legacy "Do Not Track" browser signal. We do not sell personal information, share it for cross-context behavioral advertising, or use it for targeted advertising, whether or not your browser sends an opt-out signal such as Global Privacy Control. This statement does not limit any obligation to honor a legally applicable privacy signal.
Collection across other services. Independent providers may collect personal information about your activity over time and across different websites or services when you interact with their features. For example, Stripe may combine transaction and device information from different merchants for fraud prevention and security. If you choose a separate provider service, such as saving payment details with Stripe Link, that provider's own notice explains its additional uses and choices. See Stripe's Privacy Policy. Our statement about TaleVein's advertising and analytics practices does not mean that these independent services collect no information.
You can use browser controls to clear or restrict storage, but this can sign you out, remove local preferences or recovery information, and affect features. Clearing browser storage is not a request to erase server records or cancel a subscription. Optional measurement starts only after your choice to allow it; it does not reconstruct earlier unmeasured visits.
12. Children
TaleVein is intended only for adults aged 18 or older. We do not knowingly collect personal information from people under 18. If you believe a minor has provided information, contact support@talevein.com so that we can investigate, close the account where appropriate, and delete information subject to applicable legal obligations. The age rule is not a claim that we have verified every user's age.
13. Changes and contact
We publish updates with a new effective date and notify you of material changes by email or in the Service before they take effect. Where the Terms require a longer notice period, that period applies. A change does not itself authorize incompatible reuse of previously collected information; we obtain any new consent the law requires.
For privacy questions, rights requests, or complaints:
QomoArch LLC
30 N Gould St Ste N
Sheridan, WY 82801
USA
support@talevein.com