Privacy policy

Updated October 7, 2026 · Applies to neurvona.com, neurvona.ai, and the Neurvona apps.

Neurvona, Inc. operates this service. Contact brett@neurvona.com for privacy, deletion, or support requests. Do not send payment credentials or API keys by email.

Your twin and agents

You can sign in with X or Google. Google-only accounts can use email twins and developer tools. A secure session cookie keeps you signed in. X sign-in supplies your stable account ID, display name, handle, public bio, and profile links; X sign-in requests profile, posting, and refresh access; it does not start automatic posting. Optional reconnection can request confirmed-email access. We do not read X direct messages. OAuth tokens are encrypted in storage. We store your account ID, twin profile, X handle, product documents, drafts, agent connections, and transaction records. Your paired agent can read your profile, products, drafts, and sales context. It can create drafts but cannot publish or approve payments. Agent credentials are hashed in our database. Pairing codes expire after ten minutes; connections expire after 30 days and can be revoked in your workspace.

In manual review mode, X receives draft text when you open its composer. In an enabled autopilot mission, Neurvona sends generated posts or selected reposts directly through X’s API. We do not collect your X password. Posting and refresh tokens are stored encrypted separately from ordinary sign-in. Your selected mission, limits, and authorization are recorded. Only X’s authenticated account information verifies account ownership.

Automatic preparation from X

After you connect X, Neurvona caches the public bio and links returned during sign-in to prepare your editable twin and suggest a mission. After you approve paid preparation with prepaid credits, it can read up to 20 recent original posts. Advertising credits are not required. Neurvona processes this material with Sol 6.1 Max through its OpenAI account to prepare private profile and post drafts within your approved credit budget. API keys are stored only as one-way hashes. API requests, usage, and credit purchases are recorded to run billing, limits, and security. Text you send to the post-generation API is processed by OpenAI to write drafts. If you purchase an AI writing sample, the goal, facts, and saved profile you provide are sent to OpenAI the same way; samples stay private and are never posted. Without an active plan, the profile and mission are prepared from available X profile information without a paid AI call. Replies and reposts are excluded. You may provide your own description instead. Profile auto-fill does not import direct messages, your home feed, followers, or another account’s posts. We do not use this content to train models.

Imported post bodies are processed for the request and are not retained as a separate dataset. We retain the number of posts used and generated drafts. A preparation record prevents repeated imports on every visit. We also look for LinkedIn and Instagram profile links in your X profile and the public website linked from it. We save candidate URLs and their source for you to confirm or reject; candidates are not verified identities or account connections. Older import records may also contain source post IDs. Your paired agent can read the resulting drafts and profile, not an archive of imported posts. Auto-fill does not publish, change your X account, or make payments. You review generated content before sharing it. Product sales do not permit selling Google user data or private correspondence. Request removal of imported-source records or derived drafts at brett@neurvona.com.

OpenAI processes supplied posts or descriptions, approved profile context, and generated drafts under its API terms and data policy. Neurvona uses Sol 6.1 with Max reasoning and disables stored Responses. OpenAI does not use API inputs and outputs for training unless the customer opts in; abuse-monitoring logs may be retained for up to 30 days. Neurvona does not opt your content into training.

Autopilot data and receipts

When enabled, autopilot uses your saved profile, mission, public facts you supply, and recent activity to generate posts through OpenAI. It can read up to 20 of your own recent posts with public engagement counts to estimate timing, search up to ten recent posts for a selected repost topic, or read up to five recent mentions for private reply suggestions. Source material is untrusted and cannot authorize actions. Direct messages, likes, follows, and private conversations are not imported.

We store mission settings, consent version and time, action text and source IDs, X confirmation IDs, usage reservations, and email delivery status. Raw search or mention feeds are not kept as an archive; chosen action text and source IDs are retained in your activity. Posting receipts go to the confirmed email X supplies, or an address you verify. Cloudflare delivers verification codes and activity emails. You can pause or disconnect autopilot in the workspace. Contact support to delete stored activity and source records.

LinkedIn, Instagram, and a paired Mac

When configured, connecting LinkedIn or a professional Instagram account grants the displayed profile and publishing permissions. We verify the provider account identity and store its account ID, display name, permission status, and encrypted access token in Cloudflare D1. Instagram access may be renewed while the connection remains active. Connecting an account does not start publishing. Scheduled publishing remains unavailable until the integration is ready; available autopilots require you to approve specific drafts and explicitly start the selected account.

These channels store your mission, draft text, Instagram media URLs, approvals, provider post IDs, and activity status. Publishing sends an approved draft to LinkedIn or Instagram. Instagram retrieves the public media URL you supply to create a photo or Reel; use only media you have permission to publish. These connections do not import private messages or send direct messages or connection invitations.

Pairing a Mac stores a hash of its separate connection credential, a device label, expiry, and last connection time. Website iMessage drafts include the recipient, message, approval, and submission status. The companion keeps its credential and recipient allowlist locally. It does not read your Messages history or Contacts. Pairing and checking the connection do not authorize sending; sending additionally requires the integration to be available, your approved queue, explicit activation, local recipient permission, and Apple’s Messages permission.

Disconnecting these channels removes their active credentials and pauses new work. Drafts and activity remain in your account; a request already submitted to a provider may finish. You can also revoke access with the provider. See data deletion instructions to request removal of your account or retained content.

Continuous autopilot

Gmail, LinkedIn, Instagram, and paired-Mac iMessage can keep generating new content after you explicitly approve continuous autopilot. Your shared purpose, enabled background, optional account instructions, selected recipients or media descriptions, and relevant recent draft text are sent to OpenAI for each writing check. Gmail replies also include the new inquiry text. Your selected contact addresses, media links and descriptions, settings, approval time, draft provenance, credit receipts, and activity status are stored under your account in Cloudflare D1. The cloud receives the iMessage recipients you explicitly enter here; your Mac’s full local allowlist and Messages history are not uploaded.

You choose automatic delivery within your saved controls or approval of each draft. Daily credit and delivery limits, cadence, and an optional delivery pause apply. Writing checks may use credits even when they skip, need review, or fail after starting. Gmail outreach research uses public professional sources, and Instagram uses each supplied photo or Reel once. Uncertain delivery is not retried automatically. Pausing stops new writing and delivery; already submitted provider requests may finish. Changing your purpose, account, or controls requires renewed approval.

Review links and native messages

Heads-up emails contain a private, expiring link granting control of one pending action. Anyone with that link can view the draft and edit, skip, or pause it while eligible. We store a hash of the control token, its expiry, and notice status. Opening a link never changes a post. Edits generate a new link and review window. You may reply with SKIP, PAUSE, or EDIT: followed by replacement text from your verified notification email. The private reply address expires with that review window.

Native app message drafts, explicitly allowed recipients, limits, and submission status are stored in the app’s local outbox on your device. We do not read your Messages history or Contacts. Mac delivery uses Apple’s Messages app after OS permission and your local opt-in. iPhone and personal WhatsApp delivery use the platform composer. Delivery status may be unknown. Local notifications may show a recipient and a message preview according to your notification settings. Website drafts copied into the app become local drafts; this does not authorize sending.

Talking to your twin

We retain instructions and replies from the console and any bot channel you connect so you can see their history. SMS uses Twilio, which processes your phone number and message content. OpenAI processes natural-language instructions, recent messages in your twin conversation, your account-control summaries, and approved background to interpret commands or write private drafts. Neurvona records requested setting changes, time-limited approvals, usage charges, and SMS delivery receipts. A text note you explicitly ask your twin to remember becomes owner-approved background across your accounts. Connection credentials are never included in these AI requests. We do not use your messages to train models. Phone destinations and private email control addresses are encrypted; pairing codes and lookup identifiers are hashed. SMS consent is separate from purchase and recorded with its time. We do not sell or share mobile opt-in information with third parties for marketing. We share it only with providers needed to deliver the service. Text STOP or disconnect in your console to revoke SMS access.

The email bot accepts instructions only at your private control address from your verified notification email. Keep this address private. Bot commands use your saved permissions and limits; draft requests share the purchased service credits and may send the supplied context to OpenAI. We do not import personal text history. Optional Google imports are described below. Message records remain until account deletion or a deletion request, subject to operational and legal retention needs.

Your twin’s photo

If you choose a custom profile photo, your browser creates a smaller square JPEG before uploading it. We store that photo in private Cloudflare R2 storage and its account ownership in D1. Image metadata is removed. Your original upload is not retained by this feature. Only your signed-in account and authorized API keys can retrieve the saved image. You can replace it or return to your X/default photo on My AI Twin; the previous image is removed from active storage. This feature changes your photo on Neurvona.

Optional persona sources

You can save notes and extracted document text as private persona sources. PDF and text extraction happens in your browser; original files are not stored by this text-upload feature. New imports remain inactive until you approve them. Enabled excerpts are sent to the writing provider as context. Review them before allowing public writing; generated posts may reveal approved facts.

Optional Google access uses Google’s own consent screen. Only granted permissions are used. Imports are bounded samples, not a complete Google archive: your sent-mail writing samples, recent owned documents, primary calendar context, broad professional contact context, YouTube profile and subscriptions, and open tasks. The optional Gmail writing-sample import uses sent-mail excerpts for writing style; separate Gmail workspace permissions support the email features described above. LinkedIn imports basic profile information; Facebook and professional Instagram import supported profile/post data when their integrations are approved and configured. No Outlook connector is provided.

Provider access and refresh tokens are encrypted with account-specific context. Imported text is stored in Cloudflare D1 under your account. Disconnect deletes the saved connection tokens and its imported sources. You can also revoke the provider grant in its settings. Your API keys can read your saved source text, so share keys only with trusted integrations.

AI usage and old connections

Neurvona uses its own server-side OpenAI key for writing and xAI key for research and supported media services. You do not need to provide an AI key. We store request IDs, request hashes, billing periods, provider usage costs, credit reservations, and generated results to enforce allowances, prevent duplicate charges, and show your balance. Paired agents cannot read our provider key or spend your subscription allowance or build balance.

If you saved a personal AI key in an earlier version, it remains encrypted, is no longer used, and can be deleted under “Remove your old AI key” in your workspace. Disconnect deletes it from the active database; infrastructure backups may retain encrypted records for their normal retention period. You can also revoke it in the provider’s console.

Products and payments

Product descriptions become public when you publish. The full document is shared with you, your paired agent, and buyers with a verified paid receipt. Receipt links grant access to the purchase; keep them private. Stripe holds card details and verifies seller identity. We store connected-account IDs, subscription customer and invoice IDs, billing periods, payment IDs, credit balances, automatic top-up settings and consent, payment attempts, amounts, fees, refunds, and immutable copies of purchased documents for fulfillment.

Email twins and Gmail

Connecting Gmail is an explicit Google permission step separate from sign-in and persona imports. You choose sending and/or inbox access on Google’s screen. We store the verified Google account ID, mailbox and accepted send-as addresses, granted scopes, and encrypted access and refresh tokens in Cloudflare D1. Gmail messages are sent only from a verified connected address after you approve specific drafts or explicitly approve continuous writing and delivery within your saved controls. We store mission settings, prospect business contacts and their public sources, drafts, approvals, sending states, and Gmail message/thread IDs.

Refreshing the inbox copies up to 20 recent messages into your private workspace. Copies older than 30 days are removed unless referenced by a saved reply draft. Paid AI writing sends the selected inquiry or prospect context, mission, saved profile, and approved persona sources to OpenAI to produce a draft. Writing is optional: you request an individual draft or explicitly approve ongoing writing. Continuous inbox replies use only new nonautomated inquiries received after activation. Manual drafting does not invoke an AI provider. Your Gmail content is not used to train or improve generalized AI models, sold, or used for advertising targeting. Neurvona’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including Limited Use requirements.

When you request prospect research, your chosen business audience, mission, and sender name go to Tavily and Grok to find publicly listed business contacts. Selected public source context and approved sender information go to OpenAI to prepare tailored draft introductions. We save public source links, brief evidence, relevance, contact details, drafts, and progress privately in your account. This research does not use your private inbox or business mailing address. Your account and authorized API keys can review and control these drafts. Email contents and public research are treated as untrusted input, never sending authorization. Sales emails include the sender’s business address and an unsubscribe link; suppression records are retained to honor opt-outs. There are no open-tracking pixels. Disconnect Gmail to remove the mailbox grant and pause queued sending; this preserves your sign-in, drafts, and delivery history. Revoke provider access in your Google account or contact brett@neurvona.com to request deletion of retained content. Transaction and necessary suppression records may be retained.

iPhone companion

The iOS 27 companion uses your Neurvona account for the same cloud autopilots and credit controls as the website. Native Messages and WhatsApp drafts, device action history, selected contact details, calendar events, and reminders remain on your device and in your own Apple accounts. They are not automatically uploaded to Neurvona or its AI providers. Apple’s contact picker shares only the phone number or email you choose. Calendar, Reminders, and AlarmKit request permission when you use those features; manage or revoke access in iOS Settings. Messages opens Apple’s composer and requires you to send. Siri and Shortcuts prepare actions for review. A configured widget or named shortcut runs your chosen Apple Shortcuts action under its own permissions. Files or photos you separately upload through Your information follow the upload and provider terms below.

Token payments

If you pay with NEURVONA, we store your account-linked quote, receiving wallet, token amount, price, credit quantity, timestamps, payment reference and transaction signature in Cloudflare D1. Solana transfers and wallet addresses are public blockchain records. Your wallet shares its public address to prepare the transaction; no private keys or seed phrases are collected. Our server queries DEX Screener for the public token price and a Solana RPC provider to verify payments. Payment records are retained for fulfillment, accounting and support.

Boosting requests

If you request paid boosting, we record your verified X account ID, handle, permission version, time, and request status. We may share the handle, account ID, and permission with X to request promotion access. A request is not an advertising approval or payment authorization. You can withdraw it in your boost controls; withdrawal pauses promotion. For enabled boosts, we read recent original posts and organic engagement counts, then send a bounded selection with your mission and brief to Grok. We retain recommendations, post IDs, spending limits, consent, campaign IDs, delivery results, and credit charges. Stripe settlement records verify the USD funds available for advertising.

API tools

Upstream bearer tokens and cached API results are encrypted at rest. Buyer payment tokens go to Stripe and are not stored in our application database. API input goes only to the seller’s configured upstream; we retain its hash for duplicate protection, not its body. Cached results expire after 24 hours and are removed when API traffic next runs cleanup.

Providers and retention

Google user data remains subject to the Google user data and Limited Use restrictions above; the descriptions of other features do not expand its permitted uses.

Cloudflare hosts the application and delivers notification verification and autopilot emails. Session and security records may include your IP address and browser information. Stripe processes payments. The configured AI providers process the context needed for the features you choose, subject to the Google user data restrictions above when that context includes Google data. Application rate limits use hashed source IP addresses. We use no advertising trackers and do not sell your product contents.

Profiles and drafts remain until deleted on request. Transaction and fulfillment records may be retained for accounting, refunds, and legal obligations. Disconnect agents and pause products from your workspace. Request account deletion at brett@neurvona.com.