Privacy Policy

Effective date: October 28, 2026

Scope and contact

AIVane is an independently operated software product. This policy explains this website, support communications and Hosted AI accounts and paid purchases. Contact support@aivane.net for privacy questions or requests.

The current downloadable desktop software is described in the Desktop Privacy Policy. The browser extension is described in the Browser Bridge Privacy Policy. Those pages explain recording, local data, credentials and user-controlled AI processing in greater detail.

The Google User Data Privacy Supplement is part of this policy and describes Google Sheets permissions, local and organization connections, storage, sharing, deletion and Limited Use.

Information processed by this website

When you visit or download a file, our hosting and website-delivery providers process technical information needed to serve and protect the site, such as IP address, requested URL, browser information and connection or error logs. Cloudflare provides website delivery and security. The product video on this website is served as a website file; an external video link takes you to that provider's service.

Our inquiry form prepares a message in your own email application. It does not submit your message or create an order on this website. If you send the email, we receive your email address, message and chosen attachments. We use them to answer your request and provide support. Zoho Mail provides our support mailbox. Do not include API keys, passwords or unnecessary personal information in a support message.

We do not use advertising pixels or advertising cookies. Hosting or security services may use necessary technical storage for functions such as protecting a connection. External sites, stores and payment services have their own cookie and privacy practices. We will update this policy before introducing materially different tracking or uses of information.

Cookies, analytics and session replay

We use PostHog product analytics, provided by PostHog, Inc. from the United States (PostHog Cloud US), to understand how this website, the account pages at app.aivane.net and AIVane Desktop are used. The website and account pages send analytics through our own address, ph.aivane.net, which forwards them to PostHog. PostHog is set to discard IP addresses, so they are not stored with analytics data.

Analytics is on by default, and there is no cookie banner. PostHog stores one analytics cookie, shared by aivane.net and app.aivane.net, so your visits can be linked, and records session replays of how you use these pages so we can find usability problems. Session replays reproduce what the page shows and what you type into forms, for example your name, email address and message in the product inquiry form, and on account pages your email address, device names and the list of signed-in devices. Passwords, one-time codes, device pairing codes and API keys or tokens are never recorded: password fields are masked, and those fields are left out of replays. On account pages, clicks are not captured automatically; only specific actions are recorded as events. Pages whose address carries a sign-in code (email sign-in links and the Microsoft sign-in return page) do not load analytics, and analytics removes the part of an address after # and, on app.aivane.net, the query string.

You can turn analytics off at any time: Turn off analytics in this browser. This stops analytics and session replay on aivane.net and app.aivane.net in this browser and removes the analytics cookie and identifier. Your choice is remembered for two years in a first-party cookie named aivane_analytics; it applies only to that browser, so clearing cookies or using another browser or device resets it. The same link turns analytics back on. Browser tracking protection that blocks the analytics script also prevents analytics. We use analytics and session replay on the basis of our legitimate interest in understanding and improving the website, the account pages and AIVane.

When you sign in or create an account, analytics in that browser is linked to your AIVane account's internal identifier, never your email address. Our server also records, under the same identifier, when an account is created and when a payment or subscription succeeds, with its plan, amount and currency. We use this to understand which pages and features help people download, sign up for, use and buy AIVane. We do not use analytics for advertising and do not sell it. Analytics events and replays are kept according to PostHog's default retention for our project. To have analytics linked to your account deleted, contact support@aivane.net.

AIVane Desktop sends its own usage and error reports and records session replays of its main window, which include what you type and what the window shows, but never passwords or keys; both stop when you turn off "Send usage and error reports" in its Settings. The Desktop Privacy Policy describes what those reports contain.

AIVane Android app

The AIVane Android app (REPL) runs automations on your phone for AIVane Desktop and other clients you have paired with it. It sends usage and error reports, and session replays of its own screens, to PostHog Cloud US through ph.aivane.net. They are on by default, there is no consent dialog, and you can turn them off at any time with "Send usage and error reports" on the Setup screen of the app. The app then stops sending reports and replays.

A report contains a random installation identifier created by the app (never your email address or an AIVane account identifier), the app version and the phone model and Android version, and these events: the app opening (and whether this is its first start), an automation run succeeding or failing (with only the kind of run and how long it took), the local service failing to start (with the error type), and crashes (the error type, a short error description and the program locations where it occurred). Before a report leaves the phone, the app removes file paths, web and IP addresses, email addresses, passwords and access tokens from the error description.

A session replay records how the app's own screens are used, so that we can find usability problems. Screen content is recorded as it appears, including text you type into the app and the console output that lists what your automations did; passwords and pairing tokens (the pairing invitation QR code and manual code) are not recorded. Replays do not show other apps or the screenshots your automations take. PostHog is set to discard IP addresses, so they are not stored with the reports. Reports and replays are kept according to PostHog's default retention for our project and are used only to understand and improve AIVane, not for advertising. To have them deleted, contact support@aivane.net with the app version and phone model.

Desktop recording and optional AI

Recording and workflow execution can process page content, form values, screenshots, files, application controls and other information selected by your task. In the desktop application, this data is stored on your device. Your workflows can send data to destinations you configure, and your own synchronization or backup software may copy local files.

AI is optional. With your own provider configuration, relevant task context is sent to the endpoint you choose under that provider's terms. Using a free local edition does not make an external model provider free. We do not promise that third-party providers exclude all requests from retention or training; review the terms of your chosen provider before sharing confidential data.

Hosted AI accounts and credits

Hosted AI is available through an optional AIVane account. Credit packs and the Pro subscription are bought from that account. AIVane processes account identifiers such as email, authentication and device-authorization records, purchased and promotional credit balances, order, subscription and refund-request records, usage and settlement records, and security logs. These records are needed to authorize access, deliver credit, meter usage, investigate billing problems and prevent abuse.

For Hosted AI tasks, your approved instructions, workflow context, recording evidence and supported screenshots pass through AIVane's service to the assigned inference provider. Hosted AI is an online service, not a private local model. We do not sell recording or workflow data for advertising.

AIVane's server keeps a record of each Hosted AI request: the content sent to the model, the model's response, which account and device sent it, timing, the model used and the credits charged. Request and response content is retained for 30 days, then the retention job deletes the request and response files and response previews. Request metadata, including identifiers, timing, model and usage, remains, along with separate account, settlement and billing records, for their stated purposes. Only AIVane's operator can read request content in the administration system, and only to handle your support request or a security issue. Request content is not used to train AI models and is not sold.

Support reports from the desktop app

If you choose Send to support in AIVane Desktop, the report you confirm, your contact email and optional description are uploaded to AIVane's server at app.aivane.net, which is hosted in the United States. Support staff may access reports from outside the United States and may use third-party AI tools to help analyze them. Reports are deleted 30 days after receipt, or earlier on request. The Desktop Privacy Policy lists what a report contains and how to delete it.

Current Hosted AI provider

AIVane Hosted AI sends model requests to models served by DeepInfra, Inc. The models can change; their publishers are separate from DeepInfra, which provides the inference service. This disclosure concerns AIVane Hosted AI; a provider you configure yourself has its own terms and processing locations.

DeepInfra states that its inference infrastructure operates in US-based data centers. Its Privacy Policy describes international transfers, including processing in the United States. This is the provider's published description, not an AIVane guarantee that every service record or subprocessor stays in one country. AIVane remains an independently operated product.

DeepInfra's data-privacy documentation describes normal inference content as processed in memory and removed after the request, with operational metadata retained. Its policy says inference inputs and outputs are not stored, sold or used for training without explicit consent. These provider statements do not delete AIVane's separate account, usage, settlement or local workflow records.

All current Hosted AI requests use DeepInfra. Older tasks created on a retired route cannot continue; start a new task instead. We will update this disclosure before AIVane sends Hosted AI requests to another provider, and when relevant data practices change.

Payments

Payments are processed by Creem. Checkout and payment information is handled by Creem and its payment providers under their policies. AIVane receives the customer and transaction identifiers, amounts, status, refund and dispute information and order information needed to deliver the purchase, review refunds and handle support. We do not store full card numbers or card security codes.

Signing in with Google

You can sign in to your AIVane account at app.aivane.net with Google. When you choose Google, the account sign-in page loads Google's sign-in button from Google, and Google shares your Google account ID, email address and whether Google has verified that address with AIVane. We use this information only to sign you in, create your AIVane account the first time you use Google, and link Google to an existing AIVane account that uses the same address when Google is authoritative for that address. We store the Google account ID and email address with your AIVane account. Google's response also includes your name and profile picture; AIVane does not store them.

Signing in requests only basic sign-in information. We do not receive your Google password, and signing in does not give AIVane access to Gmail, Google Drive, contacts or other Google account data. Google Sheets connections require a separate, optional authorization described in the Google User Data Privacy Supplement. Our use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Google processes the sign-in under the Google Privacy Policy. You can remove AIVane's access in your Google Account settings. Contact support@aivane.net to delete your AIVane account.

Signing in with Microsoft

You can also sign in at app.aivane.net with a personal Microsoft account or a work or school account. When you choose Microsoft, your browser goes to Microsoft's sign-in page and returns to AIVane with a signed sign-in token. Microsoft shares your account's directory (tenant) ID and object ID, your email address, and, for work or school accounts, whether your organization has verified that it owns the email domain. We use this information only to sign you in, to create your AIVane account the first time you use Microsoft, and to link Microsoft to an existing AIVane account with the same address when Microsoft or your organization is authoritative for that address. We store the tenant and object IDs and your email address with your AIVane account. Microsoft's response also includes your name and sign-in username; AIVane does not store them.

We do not receive your Microsoft password, and we do not request access to your mailbox, OneDrive, calendar, contacts or other Microsoft account data. Microsoft processes the sign-in under the Microsoft Privacy Statement. You can remove AIVane's access to a personal Microsoft account in your Microsoft account privacy settings, and an organization's administrator can remove access for work or school accounts. Contact support@aivane.net to delete your AIVane account.

Signing in with Apple

You can also sign in at app.aivane.net with your Apple Account. When you choose Apple, Apple's sign-in window opens and returns a signed sign-in token to AIVane. AIVane asks Apple only for your email address, not your name. Apple shares a stable user identifier that is specific to AIVane, your email address and whether Apple has verified it. If you choose Hide My Email, Apple shares a unique relay address instead of your real address, and Apple forwards our messages to you. We use this information only to sign you in, to create your AIVane account the first time you use Apple, and to link Apple to an existing AIVane account with the same iCloud address. We store the Apple user identifier and the email address you shared with your AIVane account.

We do not receive your Apple Account password or any other Apple Account data. Apple processes the sign-in under the Apple Privacy Policy. You can stop using Sign in with Apple for AIVane in your Apple Account settings, and you can turn off email forwarding for a relay address there. Contact support@aivane.net to delete your AIVane account.

Why information is used and shared

We use information to provide requested functionality, answer support messages, maintain security, fulfill a purchase, review refund requests, resolve disputes and comply with applicable obligations. We share only information needed by the hosting, email, analytics, model or payment service involved, or when disclosure is required by law. We do not sell personal information or use recordings to target advertising.

Where a legal basis is required, processing is based on providing the service you request, legitimate interests such as security and support, legal obligations, or consent where applicable. Service providers may process information outside your country. Their own retention practices and applicable safeguards may differ from those of your local device.

Retention and your choices

We retain support correspondence and technical records only as long as needed for their stated purposes, dispute handling or legal obligations. Future order and accounting records may need to be retained after an account is closed where the law requires it. A model provider's retention is governed by the applicable provider terms.

You can contact support to request access, correction or deletion of personal information you have provided, or exercise other applicable privacy rights. We may verify your identity and retain information that we are legally required to keep. Where applicable, you may complain to the relevant data-protection authority.

You control local recordings, AI requests and workflow execution. Deleting an account or uninstalling the desktop app does not automatically remove local recordings, exports or backups. The Desktop Privacy Policy explains local data removal. Removing local files cannot recall information already sent to another service.

Changes

We will update this page when relevant practices change and show the effective date above. We will update the service-specific provider, billing and retention disclosures when these practices change.