Privacy Policy

The short version

VIXENTIO is a Mac app that turns what you see on screen into context for AI coding agents.

Your screenshots, Boards and notebooks are stored on your Mac. They leave it only when you choose: when you turn on Sync, share something, ask our AI features (Pro and Max), or send a screenshot to a coding agent. An account is optional. We don't sell personal information, we don't show ads, and we don't use your content to train AI models.

Our marketing pages use Vercel's privacy-focused analytics, which work without cookies and report aggregate visits. The web editor and shared-link pages don't load it.

Who we are

VIXENTIO is operated by Saygin Saman ("VIXENTIO", "we", "us"), who is responsible for the personal information described here. For questions or requests about your information, email support@vixentio.ai.

What this policy covers

This policy applies to:

this website, including the guided demo and the newsletter sign-up;
the VIXENTIO Mac app (the "App"), including versions released under its earlier name;
the optional account, Sync, sharing and AI service (the "Service"), including the web editor and shared-link pages.

Coding agents, GitHub and other tools you connect are run by their own providers under their own terms. How the App hands work to them is described below.

Information we handle

On your Mac

Screenshots, annotations, Boards, notebooks and settings are stored in your user library on your Mac. The App captures your screen only when you start a capture, and keeps only the region you select. Without an account, none of this is sent to us.

This website

Our host, Vercel, receives standard request information when you visit a page or download the App: IP address, browser type, the page requested and the time. Vercel uses it to deliver the site and protect it from abuse, and keeps it for a limited time.

On the marketing pages (the home page, this policy, the Terms and the not-found page) we use Vercel Web Analytics and Vercel Speed Insights. Web Analytics records page views with the page address, referrer, approximate location (country, region and city), browser, operating system and device type. It sets no cookies and recognizes a returning visitor only within a single day. Speed Insights records how fast pages load, with the page, browser, device type and country. We see aggregate reports, not individual visitors.

The guided demo on the home page runs entirely in your browser on a bundled sample page. Nothing you type or select in it is sent anywhere.

Your account

An account is optional. When you create one we keep your email address, a display name and your password, which our authentication provider stores only as a secure hash. If you sign in with Google, Google shares your email address, name and an account identifier with us. Signing in uploads no documents, but it does register the device you sign in on: a random installation identifier, the device's name (for example "Alex's MacBook Pro"), its platform, the app and macOS versions, and when it was last seen. Your session is kept in your Mac's Keychain.

Sync

Sync is off until you turn it on. When it's on, we store the Boards and notebooks you sync with the images, PDFs and files inside them, and the workspace records that belong to them (such as Spaces, study cards, links, Inbox items and memory entries you've created). Screenshots are uploaded only if you separately turn on Screenshot sync. We keep up to 20 earlier versions of each document so you can restore them. Synced content is private to your account by database rules and encrypted in transit, and our provider encrypts it at rest. It is not end-to-end encrypted, so it isn't hidden from us or our provider.

When you share a Board or notebook, we store the share's settings and, for invitations, the invitee's email address and role. Invitations are sent by email and include your display name and the document's title. People you share with can see the shared content, comments and, while you're working together, your name, cursor and selection. Comments and edits you make in someone else's document stay with that document; if you delete your account they remain, shown as from a former collaborator.

Shared links contain an access token. Like any address, it appears in our host's request logs. Shared-link and editor pages are hidden from search engines and don't send your address to other sites.

The web editor and shared links

The web editor at /app and shared links at /s/ use your browser's storage, not cookies, to keep you signed in, remember your preferences and tools, keep a random identifier for the browser, cache your library's titles, and hold edits that haven't reached our server yet. Unlocking a password-protected link is remembered for 30 days. Clearing your browser's data for this site removes all of it; signing out clears the cached library.

AI features (Pro and Max)

The App's AI features are part of Pro and Max and need an account. The first time you use them, the App explains what is sent and asks for your consent. A request is sent only when you ask, and contains your instruction and the material you chose, shown as chips you can remove before sending. Depending on the feature, that can be a selection, a page, a screenshot with your redactions applied, PDF pages, or the text of files you choose, including source code. Before anything is sent, the App removes keys, tokens and private keys it recognizes, and our server checks again.

Requests go to our server, which checks your plan and fair-use limits and passes the content to Anthropic to create the answer. We send Anthropic no name, email address or account identifier, though the content you choose may itself contain personal information. Our server doesn't store the content of requests or answers. For each request it keeps usage information linked to your account: the feature, model, platform, time and duration, token and image counts, estimated cost, the outcome, what you did with the result and any rating you give.

Sending to coding agents

When you send a screenshot to Claude Code, Codex or Cursor, the App writes the exported image to a cache folder on your Mac (removed after about a week) and opens the tool you chose with your instruction and project folder. For Cursor, the image is placed on your clipboard for you to paste. If you allow it in macOS, the App can also type the request into a Claude Code session you already have open in Terminal or iTerm. The App doesn't upload these exports. The agent you choose runs under your own account with its provider, which may send your instruction, images and project files to its own servers under its terms.

Developer Platform

The Developer Platform (live component selection, agent tasks, visual review and publishing to GitHub) is set up for teams through onboarding. The development integrations send component and source details from your local dev server to the App on your Mac only, over a local connection. Agent tasks run your own Claude Code in your project under your Claude account, and the App keeps a record of each run on your Mac. Changes you publish to GitHub use your own git and GitHub sign-in; we never store those credentials. Visual reviews send before-and-after captures of your app to Anthropic through our AI service, as described above.

You can share a Claude Code session you started yourself in Terminal, iTerm2 or tmux with a piece of your team's shared work. It's off for every session until you choose Share with Team… for that one session, and the App shows you what will be shared before anything leaves your Mac. The App reads that session's transcript on your Mac only after you choose to share or preview it.

What's shared: the session's title or first request, short summaries of its steps and tools (like "Edited 2 files" or "Ran tests"), the files it changed, its status and times. Files are shown by name unless you choose, for that share, to add a fingerprint of each file's path or to show paths inside the project. Never an absolute path.
Only if you choose it for that share: the assistant's messages from then on, with likely secrets redacted on your Mac and again on our servers. They can quote code or files.
Never shared: the transcript itself, your other prompts, the assistant's thinking, diffs, commands and their output, and titles or file names that look like secrets.
Guidance: teammates with the right role can send guidance. The App types it into your session only after you accept it, or right away from people you named for that share.
Who sees it: everyone in the team, according to their role, as with any run of its work.
Ending it: a share ends when you stop it, the session closes, you sign out or lose your role, or your Mac stops reporting. Teammates see that it ended.

Cloud workspaces

Cloud workspaces are off unless your team's owner turns them on for a project and chooses its GitHub repository. The owner also chooses how the agent reaches the model: with Vix Credits ("Vix", the default), through our model service, or with the team's own Anthropic API key. Then an editor the owner allowed can run a piece of shared work on a cloud workspace instead of a teammate's Mac.

What's processed: the repository the owner chose (cloned for the run), its dependencies, the project secrets your team added for the dev server, the work's instructions and guidance, and what the agent writes. Each run has its own short-lived virtual machine, created for the run and deleted when it ends (at most two hours).
Where: in the United States (Vercel Sandbox, us-east-1, Virginia). Other regions aren't available yet.
Credentials: the run gets a GitHub token for that one repository only, valid for about an hour. Neither it nor any model credential is stored inside the workspace: the workspace's network firewall adds them to requests, so Vercel handles them in transit.
*With Vix Credits,* the agent's requests go through our model service to Anthropic, under our account with Anthropic and its commercial terms (described above for the AI features). Our service passes them on and reads only the token counts Anthropic reports; it doesn't keep the prompts or the answers.
*With the team's own key,* the agent's requests go to Anthropic with that key, billed by Anthropic to the team under its terms. We store the key encrypted and never show it again, to anyone.
What's kept: the code changes leave the workspace only as a branch it pushes to your repository when its starter asks for it. Teammates see the run's progress, pictures of your app it captured, and the review, as with a run on a Mac, according to their role. To charge Vix and apply your team's limits, we record each run's duration, compute, the model its starter chose (or Auto), the models it used and their token counts, and its cost in Vix (no content).

Payments

Pro, Max, Team seats and Vix packs are billed through Stripe. We give Stripe your email address and account identifier, and you enter your payment details on Stripe's own checkout page, so we never see your card number. Your purchase may be sold through Link, LLC, a Stripe affiliate that then acts as the merchant of record and handles payment, tax, receipts and transaction support; your receipt shows who sold it. We keep your subscription's status, plan (Pro, Max or Team, and a team's number of seats), price, trial and billing dates, and for Vix, which pack a team bought and when, the Vix a plan includes each month, your account's welcome Vix, and the team's balance and its history. We also keep whether your account has had a trial or a Team subscription, so each trial is given once.

The newsletter is opt-in. When you sign up on this website we email you a confirmation link, and you're added only after you confirm; until then we don't store your address. We keep your email address and when you subscribed. Newsletter emails may include a small image and links that pass through our email provider, Resend, so we can see whether an email was opened and which links were clicked, with the time and basic technical details. Account, invitation and confirmation emails don't measure opens or clicks.

Updates and diagnostics

The App checks our website once a day for updates. The request includes the App's name and version and, like any request, your IP address. You can turn automatic checks off in the App's settings. The App contains no third-party analytics or crash-reporting code. Diagnostics and feedback are created only when you choose Export Diagnostics or Send Feedback, saved as files on your Mac, and sent to us only if you send them.

When you contact us

We keep the emails you send us and our replies so we can help you.

How we use information

We use the information above to:

provide, secure and maintain the App, your account, Sync and sharing;
apply plan limits and your Pro, Max or Team subscription, and give each plan its Vix;
provide the AI features and understand their cost, quality and fair use;
understand, in aggregate, how the website is used and how fast it loads;
send the newsletter you've confirmed, and learn which issues are useful;
answer support requests;
detect and prevent abuse; and
meet legal obligations.

We don't sell or rent personal information, we don't use it for advertising, and we don't use your screenshots, Boards, notes or code to train machine learning models.

We use a small number of service providers, who handle information on our behalf under their data protection terms:

Vercel to host this website, the web editor, shared-link pages, update checks and downloads, and to provide Web Analytics and Speed Insights;
Supabase for sign-in, the database, file storage and real-time collaboration;
Anthropic to create answers for the AI features. Under its commercial terms it doesn't train models on this content, and it deletes it within a limited period (currently 30 days by default, longer if a request is flagged for a policy review or the law requires it);
Resend to send account, invitation, confirmation and newsletter emails, and to keep the newsletter list;
Stripe to process payments for Pro, Max, Team seats and Vix packs;
Vercel Sandbox to run cloud workspaces, if your team turns them on (see Cloud workspaces).

Some parties act independently under their own terms and privacy policies:

Link, LLC when it sells your purchase as merchant of record;
Google, if you choose to sign in with Google;
the coding agents you send to (such as Anthropic for Claude Code, OpenAI for Codex, and Cursor) and GitHub, which you use under your own accounts;
people you share documents with, who see what you share.

We may also disclose information if the law requires it, to protect people's safety or our rights, or as part of a sale or reorganization of the product, in which case this policy continues to apply.

International transfers

Our service providers are based in the United States, and your information may be processed there or wherever they operate. Where the law requires it, we rely on appropriate safeguards such as standard contractual clauses.

How long we keep information

Account and synced content: while your account exists. Turning off Sync or signing out deletes nothing. Earlier versions are limited to 20 per document.
AI usage records and device records: while your account exists.
Account deletion: when you delete your account in the App, we immediately cancel any subscription and delete your account, synced documents, files and usage records from our live systems. Some information remains: the customer record and billing records Stripe and Link keep, records of payment events, and your comments and edits in documents others own (anonymized). Our providers' backups and logs expire on their own schedules. Documents on your devices aren't affected.
Shared Claude Code sessions: kept with the work's runs (the 20 newest runs of each piece of work). The assistant's messages are limited to the newest 50 per share. Deleting your account deletes what was shared from your sessions.
Cloud workspaces: each workspace is deleted when its run ends, with everything in it. The team's Anthropic key is kept until the owner removes it or the project or team goes. Run records (duration, compute, token counts and cost, no content) and the team's Vix history are kept while the team exists.
Newsletter: until you unsubscribe. Our email provider keeps sending records for a limited time.
Website requests and analytics: for the limited periods Vercel keeps them.
Support emails: as long as needed to help you and keep a record of the conversation.

Your choices and rights

You can use the App without an account, keep Sync off, and turn Screenshot sync off at any time. You don't have to use the AI features; you can remove any material before a request is sent, and you can withdraw your consent in the App's AI settings (Ask Again Before Sending). You can unsubscribe from the newsletter with the link in every issue or by emailing us, and you can turn off automatic image loading in your email app.

Depending on where you live, you may have the right to access, correct, export or delete your personal information, and to object to or restrict certain processing. You can delete your account yourself in the App's settings. For anything else, email support@vixentio.ai. We'll answer within the time the law requires, and we won't treat you differently for asking. If you're in the European Economic Area or the United Kingdom, you can also complain to your local data protection authority.

Security

Connections between the App, the website and the Service are encrypted. The key used to reach Anthropic for the AI features exists only on our server, never in the App. Database rules limit each account to its own documents and the documents shared with it. No system is perfectly secure, so please use a strong, unique password.

Children

VIXENTIO isn't directed to children under 13 (or the minimum age where you live), and we don't knowingly collect their personal information. If you believe a child has created an account, contact us and we'll delete it.

Changes to this policy

If we make a material change, we'll update the dates at the top of this page and, when the change affects account holders, tell you in the App or by email before it takes effect.

Contact

Questions or requests: support@vixentio.ai.