Virillio accounts · Updated October 6, 2026

Account and product privacy notice

This notice describes the information used by Virillio LLC for website accounts, Virillio Code, and Virillio Mobile.

Account and profile information

For email sign-in, we use the email address you enter and send a one-time sign-in link. For Google or ChatGPT sign-in, we receive the account identifier and basic profile information the provider supplies, such as your name, email address, and, when available, profile image. We store account and provider identifiers so you can return to the same Virillio account.

If you upload a profile photo, it is resized to a square web image, stored in private account storage, and served only through an authenticated account route. If you do not upload one, we use an available identity-provider image or the first letter of your name.

Google sign-in requests only basic identity, email, and profile information. Virillio does not request Gmail messages, Google Drive files, or access to ChatGPT conversations for sign-in.

Provider keys and connected devices

When you connect an AI provider, Virillio stores the provider name, configuration, a non-secret fingerprint, and the API credential. Provider credentials are encrypted before database storage with a separate server-side key. The full credential is not displayed again on the website.

An authorized Virillio Code device can request the connected-provider configuration it needs. That response can include the provider credential and is restricted to a short-lived, device-scoped access token over HTTPS. Device refresh tokens are stored as one-way hashes, and you can revoke device access from Account.

Bring-your-own-key requests are billed by the provider you connected. They do not silently fall back to Virillio-managed billing.

Connected apps and AI requests

Optional app connections request permissions separately from account sign-in. Virillio’s Apps and Calendar services use Supabase for account mappings, selected sources, encrypted connection or action state, and operation records. For managed connections, Composio stores provider credentials and executes authorized requests against the app you connected. Requested source content may pass through these services to your phone and the AI provider selected for your text or voice conversation. External changes require the action review shown in the app.

AI recipients depend on the feature you select: OpenRouter and its selected model provider for text and supported media; OpenAI for dictation and its voice mode; xAI or ElevenLabs for their voice modes; and the model provider configured for an ElevenLabs agent, including Google Gemini. A configured Calendar scan may use a separate server model. Their processing and retention terms apply. The Mobile privacy notice explains device storage and feature-specific controls.

For bounded paging and incremental transaction reads, Virillio temporarily stores an encrypted snapshot of selected source results on its server. Each snapshot expires within 10 minutes and is removed by recurring cleanup, disconnection, source-selection changes, or account cleanup. Execution receipts retain status and limited operation metadata without returned source content; content-free action outcomes can remain until account-data deletion.

Composio normally retains execution arguments, responses, and associated logs for up to one year, and staged tool files for 24 hours. Disconnecting an app stops its use by Virillio and requests provider revocation, but does not erase historical processor logs or the destination service’s records. Account closure revokes Virillio sign-in sessions and queues connected-app suspension and server cleanup; provider or delivery failures can delay completion. Local conversation deletion is a separate device control. See Composio’s retention policy.

Our use of information received from Google Workspace APIs follows the Google API Services User Data Policy, including the Limited Use requirements. We use that information only for the visible features you authorize and do not use it to train general AI models. Read Google’s Workspace data policy.

Billing and usage information

If you choose a paid plan or add credits, Stripe processes checkout and payment details. Virillio stores Stripe customer and transaction identifiers, subscription and invoice status, invoice links, amounts, and limited payment-method details such as brand, last four digits, and expiry. Virillio does not store full card numbers or card security codes.

For Virillio-managed model requests, account records can include the model and provider route, token counts, credit charges, timestamps, request status, and billing references. The billing ledger is kept separately from prompt and source-file content. Dollar values shown beside credits are estimates for account planning; Stripe receipts and issued invoices are the payment record.

Preferences, security, and service providers

We store account preferences such as model routing, balance warnings, managed-usage budget targets, product-email choices, and whether you permit optional technical diagnostics when supported. The diagnostics preference excludes prompts and source files.

Authentication and security records can include IP address, browser information, device details, session timestamps, rate-limit records, and security audit events. Essential cookies maintain the signed-in session and protect account requests.

Account information is stored in the website’s server-side database and private object storage. Virillio uses OpenAI Sites and Cloudflare for hosting and storage, identity providers for sign-in, Resend for requested sign-in or account email, and Stripe for billing. These providers process the information needed to perform their respective services.

Website analytics

We measure visits to public pages, referring websites, installer download-link clicks, and aggregate account registrations. Analytics records contain the public page path, referring domain, event type, download platform, and UTC date. We do not store URL query strings, raw IP addresses, names, email addresses, or account identifiers in website analytics events.

To estimate daily visitors, our server briefly uses the network address and browser information to create a private hash that changes each UTC day. We do not set analytics cookies or store analytics identifiers in your browser. Traffic records are retained for up to 90 days and older records are removed as new traffic is recorded. Reports are restricted to the site owner. We skip browser traffic that sends Do Not Track or Global Privacy Control signals and filter common automated visitors.

Your controls and questions

You can change your name and verified email, replace or remove your profile photo, disconnect provider credentials, revoke Virillio Code devices, and manage billing through Stripe. Self-service account closure revokes account sessions and enters a 30-day recovery period. Final deletion removes the profile and sign-in credentials after that period; necessary billing, security, and legal records may be retained. Connected-app cleanup and revocation can remain pending while a processor is unavailable. Deleting a Virillio account does not erase local conversations on a phone or issue a refund. Contact us to request access, correction, or deletion of account information.

To ask about this notice or request access, correction, or deletion of account information, contact nikolaivintenjohansen@gmail.com.