1. Operator and scope
Twerity is operated under the public name Twerity. Our public contact for privacy and support is post@twerity.com. This notice applies to the Twerity website and its connected account services, including sign-in, reflection, Persona and credit purchases.
Twerity is intended for users aged 18 or older. An account requires confirmation of that age requirement. If you believe a child has provided personal information, contact us so we can investigate and remove it where appropriate.
2. Data we process
| Category | Examples |
|---|---|
| Account and login | Display name, email when supplied, password hash for email accounts, connected provider identifiers, provider label and email where returned, verification state, sessions and consent records. |
| Your reflections and Persona | Foundational choices, question and answer sources, current and previous memory wording, corrections, profile scores, progress, conversation messages and response references. |
| People, life events and private files | Names, relationships, aliases, importance and facts you enter; event descriptions, exact or approximate date wording, locations you supply, linked people and memories, optional photos, videos or audio, private filenames and change history. |
| Persona feedback and response context | Your response rating, optional correction, the question and reply, timestamps, evidence references and a bounded snapshot of the profile, relevant memory excerpts and recent conversation context used for that reply. |
| First-party product activity | Account-linked daily activity, opening Persona and fixed error categories such as network, timeout or rendering. Aggregate reports also count existing onboarding progress, message activity, feedback, credit use and referrals. |
| AI safety reports | The reported response identifier, reason, optional details, submission date and review status. |
| Credits and participation | Earning sessions, direct referral relationships, active-session overlaps, credit ledger entries, reservations, purchase quantities and use of paid, earned or promotional credits. |
| Purchases | Order and invoice identifiers, USD price snapshots, Pi quotes and rate sources, payment identifiers, transaction references, crypto currency and status, received amounts and reconciliation flags. For Google Play purchases: product identifiers, obfuscated account/order bindings, purchase receipts and consumption state. |
| Service and security | Request times, network and browser information in hosting logs, error details, token hashes, and pseudonymous rate-limit records derived from account or network identifiers. |
| Support | The email address, message and information you choose to send when contacting Twerity. |
We do not need your wallet seed phrase, private key, full payment credentials or government ID to operate this product. Do not put these secrets in memories, Persona messages, support emails or a referral code field.
Reflections can reveal sensitive information if you choose to write it. Keep questions and memories focused on information you are comfortable storing and processing. Do not submit someone else’s private information without an appropriate basis.
People and Timeline are optional spaces after your foundation is complete. You choose the people, relationships, dates and facts to record; Twerity does not read your address book or silently merge people with similar names. Approximate dates keep your wording rather than acquiring an invented exact date. Uploaded files are stored with your private account and require owner authentication to retrieve. They are not public announcement images.
3. Why we use the data
We use account and workspace data to provide the service you request: authenticate you, preserve answers, calculate profile progress, deliver Persona responses, record credits, verify purchases and answer support requests. Where contractual necessity applies, it is the basis for this processing.
AI processing is controlled through your account consent and AI setting. Advertising consent, where required, is separate from accepting these product terms or enabling Persona. Withdrawing consent applies to future processing and does not undo processing that already took place lawfully.
We use proportionate security and abuse checks to protect accounts, prevent duplicate credit claims, investigate payment discrepancies and maintain reliable service. Where applicable, our legitimate interests are protecting the service and its users. Financial records may also be retained to meet legal obligations or establish, exercise or defend claims.
We use limited first-party activity records to understand which features are used, whether new accounts reach Persona and where reliability needs improvement. The activity endpoint accepts fixed event/error categories, rather than private answer text, conversation text or raw error messages. Administrator analytics show aggregate counts; this measurement does not copy your media into analytics records or create an advertising profile.
The foundational profile uses deterministic scoring of the choices you provide. It guides product reflection and access after completion. It is not a credit score, a clinical diagnosis, or a decision about employment, insurance or other significant legal rights.
4. Persona and AI processing
The foundation’s initial scores and coverage are computed without an LLM call for each answer. Once Persona is unlocked and you use it, the current provider mode is shown in your workspace.
- Demo mode: a local template produces limited responses from selected saved memories.
- External AI mode: your current message, a compact foundational profile, relevant current memories and excerpts from recent completed conversation turns are sent to the configured model provider. The current integration supports OpenAI.
Responses and their evidence references are saved in your account. AI can make mistakes or misinterpret the supplied context. Review important statements, correct your memories and use your own judgment. Use Report response on a saved Persona reply to flag offensive or unsafe output to Twerity. Authorized reviewers can access that reported reply and the reason and details you submit to investigate it and improve safeguards. A report references the selected saved reply; it does not automatically copy your full conversation or earlier prompts into a report. Reports remain private and are removed with the account or referenced reply. You can disable future AI requests from Privacy. Data already sent to a provider is subject to that provider’s processing and retention terms; disabling AI cannot recall a completed request.
The written facts you enter about people and life events can become cited memory context for Persona when relevant to your question. Uploaded photo, video and audio bytes are not forwarded to the AI provider, transcribed or used as advertising targeting in this release. Persona uses the event description and other text you supply.
Suggested reflection questions use bounded templates grounded in saved areas, memory topics, incomplete user-entered relationships and earlier/current wording. Producing these suggestions does not make a paid AI request. The app asks you to clarify a change; it does not automatically decide that two names are the same person or that different memories are contradictory.
Each new Persona reply can retain a private snapshot of the question, answer and bounded context used to produce it. “Sounds like me” / “Not like me” feedback and an optional correction are attached to that reply. These records support review, source explanations and product improvement; a rating by itself does not rewrite your original answers or train an AI model. Authorized operators may inspect relevant records to investigate feedback or service issues. Evidence/confidence labels summarize citation support and are not calibrated probabilities that an answer is true.
Twerity’s current OpenAI integration requests that API responses not be stored as provider conversation state. That setting does not establish a general promise about a provider’s security logs, legal obligations, retention or model training practices. See OpenAI’s privacy information for its terms.
5. Other providers and visibility
Our hosting and email services process data needed to operate the website, database, delivery of confirmation and recovery emails, and support. Operational access may be used to diagnose problems, protect accounts or resolve your request.
Google or Pi processes your sign-in under its own terms. Twerity receives the identifiers and available profile information needed to authenticate you. A standalone Pi account does not require a separate email account. Connecting another identity requires an explicit account flow; it is not an automatic merger of two balances or histories.
Google Play processes Android in-app checkout under its own terms. Twerity verifies purchase receipts with Google and receives product, order, payment-state and obfuscated account/order identifiers. Private receipt records support verification, server consumption, duplicate-credit protection and reconciliation; they are not included in account data exports.
Pi and NOWPayments process checkout and payment information under their own terms. Blockchain transfers and public transaction references may be visible on the relevant network and cannot be erased by Twerity. Twerity verifies provider receipts before issuing purchased credits.
If you use a referral, your display name and earning activity are visible to your direct team. Your private answers, memories and chats are not shown to that team.
Providers may process information in countries different from yours. Applicable protections depend on the provider, service and jurisdiction. Contact us if you need information about a particular processing location or international transfer arrangement.
6. Optional advertising
Twerity supports Google AdSense on selected public informational pages and Google AdMob in the Android app. App interstitials are limited to the natural pause after a successfully saved daily answer, starting with your fourth ordinary daily earning session. The first three sessions, paid guided-questionnaire answers, diary entries and Persona conversations do not trigger these ads. Saving an answer and receiving its session credits never depend on an ad loading or being viewed.
Android advertising uses the Google Mobile Ads SDK and Google User Messaging Platform (UMP) for consent where required. Before requesting ads, the app checks the current consent state. This integration requests non-personalized ads. Depending on consent and the applicable configuration, Google may process IP addresses, approximate location inferred from the network, device or advertising identifiers, ad interactions and diagnostic information for delivery, measurement, security and fraud prevention. Non-personalized ads can still involve device storage and personal data.
When ads are enabled, Google and its advertising partners may use cookies, local storage, web beacons, IP addresses and other device or browser identifiers to serve ads, measure performance and detect invalid traffic. The current Twerity integration requests non-personalized ads and checks the consent or regional opt-out signals needed for that request.
Twerity does not send your reflections, private memory text, people and relationship details, life events, uploaded media, Persona conversations, response-feedback snapshots, email address or account display name to AdSense or AdMob as ad targeting data. Public-page ad requests still reveal information needed to deliver the ad, such as the page, network address and browser.
Where consent is required, the ad experience must offer a consent-management message before relevant advertising storage or processing is enabled. You can change or withdraw available advertising choices through the consent controls when ads are running. Refusing optional ads does not prevent use of the account’s required sign-in and security mechanisms.
In Android, open Privacy & account and use Advertising privacy when consent options are available to review or change your choices. A local, account-scoped display record helps avoid showing the same daily-session ad twice. Your account identifier is not set as an advertising user ID and your private answers are not passed to the ad SDK.
Read how Google uses information from sites and apps that use its services and manage your Google advertising preferences at My Ad Center. See our Cookies notice for storage details.
Android daily-session reminders are optional local notifications. If you enable them, the app stores a session identifier, its expiry time and a pseudonymous account binding on this device to schedule one generic reminder. Android notification permission is requested when you enable this feature. The reminder does not send an email or share your private answer text with a notification service. Turn it off in Privacy & account; signing out cancels the saved reminder. Android battery settings can delay delivery.
7. Retention, export and deletion
Request deletion of your Twerity account and associated data. This public page explains deletion from the app or website and an email request option if you cannot sign in or have uninstalled the app.
Account information, answers, memories, people and life events, private files, response-context snapshots, feedback and account-linked product activity are retained with the account for their described purposes while it exists. Editing a memory or entry keeps the original source and earlier/current wording or an entry snapshot with timestamps. Deleting a person or event removes its active entry and current memory context; the recorded change history remains until account deletion. Files can remain in private storage if merely unlinked from an event. From the Privacy area, you can export account data and initiate account deletion after confirming your identity.
Deleting the account removes its personal workspace and login records, including people, life events, private uploads, their change history, Persona response-context snapshots, feedback and account-linked daily product activity from the active account database. Financial order and receipt records may remain without a link to the deleted user account to support reconciliation, duplicate-payment protection, legal obligations and disputes. A late payment for a deleted account is recorded for review rather than automatically credited to another user.
An active checkout or payment with unresolved funds can temporarily prevent deletion until it is closed, settled or reviewed. Closing a local checkout alone does not cancel an external transfer. Direct referral relationships are removed, while historical activity may be retained without the deleted account to preserve another user’s earned-credit calculations.
Hosting logs, backups and provider-held copies follow operational and legal retention requirements rather than disappearing immediately with an account deletion. We keep such data for the period needed for those purposes and restrict its further use. Contact us for details about a particular record or deletion request.
8. Your choices and rights
- Review and correct current memories, manage the people and events you entered, check original sources and inspect saved profile evidence. Contact support if you need help removing a particular private file or historical record.
- Export your account data from Privacy before closing your account.
- Disable future AI use through the AI setting, or request deletion after identity confirmation.
- Manage cookies and browser storage, and change optional advertising consent when it is available.
- Contact post@twerity.com for access, correction, erasure, restriction, portability, objection or consent questions under the law that applies to you.
We may need proportionate confirmation of account ownership before disclosing or changing personal information. We do not ask you to send passwords, wallet keys or email recovery links. If EU or UK data-protection law applies, you may also complain to the relevant supervisory authority.
9. Security and changes
We use password hashing, expiring session and account-action tokens, authenticated account actions and durable rate limits. Production traffic should use HTTPS. No online system can guarantee absolute security; report a suspected account or payment problem to post@twerity.com.
We may update this notice as the product, providers or applicable requirements change. The date at the top identifies this version. Material changes to how your personal data is used will be communicated through an appropriate product notice or account channel.