Privacy

FreeSyntax and notch are operated by Driftrail (“Driftrail,” “we,” “us,” and “our”). This policy explains how we handle personal information when you use freesyntax.dev, create an account, buy gear, join a membership, use hosted model features, write to us, or download and run the notch desktop or command-line tool. It should be read with the terms.

The support mailbox for privacy requests, account questions, and legal notices is support@driftrail.com. Messages about your account or an order may be sent from an address on freesyntax.dev. Replies and privacy requests belong at support@driftrail.com.

“Personal information” means information that identifies you or can reasonably be linked to you. It includes an email address, an account identifier, a payment record, and the contents of a message you send us. It does not include project files that never leave your computer, and it does not include information that has been aggregated so that it no longer identifies you.

This policy covers:

• —The website at freesyntax.dev, including the landing page, shop, account pages, and these legal pages.
• —Accounts, access codes, membership, applications, and email we send about them.
• —Payments processed for gear, membership, credits, or hosted compute.
• —Hosted inference and other features that run on our systems or through a provider we call for you.
• —The notch desktop and CLI, including what stays on your machine and what leaves it only when you turn a network feature on.
• —Error reports and, on the production website, a sample of session replays.

It does not control a third party you choose yourself. When you send a prompt to OpenRouter, OpenAI, Anthropic, Google, Hugging Face, GitHub, or another service, that service’s own policy applies to what it receives. When you install a plugin, connect an MCP server, open a remote shell, or browse the web from the tool, that destination is outside this policy.

Depending on what you use, you may give us:

• —An email address, name, and password, or the identity returned by GitHub or Google if you choose those sign-in methods.
• —An access code, a repository URL, and anything you include in an application or support message.
• —Order details for gear or membership, including the shipping address and contact details you enter at checkout. Card numbers are collected by Stripe, not stored by us.
• —A provider API key, if you save one on an account so we can place the calls you request. A key saved in the local desktop or CLI stays on that machine.
• —Prompts, files, and other content you submit to a hosted feature. Content you keep in a local chat stays on your machine unless you send it to a provider.
• —The contents of email you send to support@driftrail.com, and any attachments you include.

You should not send us passwords for other services, full payment card numbers, government identifiers, or health information. If a prompt or a project contains secrets, remove them before you send that material to a hosted feature or to a cloud provider.

An account is optional. You can run the local desktop and CLI without one. If you create an account, we store the email address you give us and the authentication record needed to recognize you. If you sign in with GitHub or Google, we receive the profile fields that provider shares with us, typically a name, an email address, and a provider identifier. Supabase processes authentication and stores the account record. A session cookie keeps you signed in. We do not use that cookie to advertise to you.

You are responsible for the activity under your login. If you believe someone else is using your account, write to support@driftrail.com and change the password or disconnect the sign-in method.

Gear, membership, and other paid features are charged through Stripe. Stripe receives the card details, billing contact, and the amount. We receive a confirmation, a customer reference, the amount, the product or plan, and the status of the charge. We do not store full card numbers or card security codes. Stripe’s own privacy policy describes how Stripe handles payment data.

For a physical order we keep the shipping details you submit, the item, and the fulfillment status, so we can ship it, handle a delivery problem, and keep the tax and accounting record. For an access code we keep the code, where it came from, whether it was redeemed, and the account it was attached to.

Order, membership, and account email is sent with Resend. The visible from-address may be on freesyntax.dev. The mailbox for a reply about your data is support@driftrail.com.

The production website is hosted by Vercel. Vercel processes the request data needed to deliver the page, including IP address, browser type, and the URL you requested, under its own terms. Server logs of that kind are used to operate and secure the site.

We use a session cookie for accounts. We do not set advertising cookies, and we do not sell personal information. Page-view measurement stays off unless a product-analytics key is configured. When that measurement is on, it is kept in memory for the visit and is not written as an advertising cookie.

On the production website, Sentry receives error reports. About one in ten visits can include a replay of that visit so we can see what failed. A replay can include text that was on the screen, because the recorder is not set to mask all text. It can also include a replay when an error occurs. Replays and error reports are processed by Sentry in the United States and are kept under Sentry’s retention. This recording runs on the website. It does not run inside the local desktop or CLI.

If you use a model that we run or route for you, we process the request so we can send it, return the result, meter the charge, and enforce limits. That processing can include the prompt, files you attach to that request, the model you selected, token counts, timing, errors, and the account the request belongs to. Platform-paid compute is billed at the provider’s cost plus the margin stated at purchase. A bring-your-own-key call that we mediate is billed as stated at purchase, and the upstream provider bills the rest of that call.

Prompts and output on that hosted path may be kept for delivery, abuse review, and debugging, and are then deleted within 30 days, unless a longer hold is required for a security investigation, a legal claim, or a billing dispute. We do not use your prompts or output to train FreeSyntax models unless you explicitly opt in. An opt-in applies only to the material you agreed to share for that purpose. You can withdraw it by writing to support@driftrail.com. Withdrawal does not erase a model that was already trained, and it does not recall a copy you already sent to an upstream provider.

We may refuse or stop a hosted request that breaks the terms, overruns a limit, or looks like abuse. The record of that refusal can include the account, the time, and enough of the request to explain the decision.

The Windows desktop and the notch CLI run on your computer. Chats, project files, settings, undo history, and downloaded models stay on that machine. The local edition does not need a FreeSyntax account. It does not upload telemetry, crash reports, or your project files to Driftrail.

We cannot see a local chat, and we cannot delete it for you. Uninstalling the desktop does not remove conversations, settings, or downloaded models. Those files remain yours to keep or delete.

Update checks download public releases from GitHub. That request goes to GitHub, not to a private Driftrail profile of your projects. Model setup can download weights from Hugging Face, or from a runtime you choose, onto your machine. Those downloads are between you and that service, and they are subject to the model’s own license. A Windows installer is currently unsigned. Downloading it from the release linked on freesyntax.dev, and comparing the published checksum, is the check we provide. The download itself is logged by GitHub under GitHub’s policy.

Optional features stay off until you enable them. Those features include a cloud model, cloud voice, web search, a connected tool, a remote SSH host, and a provider key. When you enable one, the data that feature needs is sent to the destination you selected. A local model, local speech, and local files are not sent to us as part of ordinary use.

We use personal information to:

• —Provide the site, accounts, shop, membership, access codes, and hosted features you ask for.
• —Take payment, keep tax and accounting records, and show you what you were charged.
• —Authenticate you, keep the session, and detect unauthorized access.
• —Answer support mail sent to support@driftrail.com.
• —Enforce the terms, rate limits, and abuse rules, and investigate fraud or security incidents.
• —Fix the website, using error reports and sampled replays.
• —Send transactional messages about an account, an order, a code, or a security event. We do not send third-party advertising.
• —Comply with law, a court order, or a lawful request from a public authority.
• —Establish, exercise, or defend legal claims.

The legal bases, where a privacy law requires us to name them, are performance of the contract with you, our legitimate interest in running and protecting the service, your consent where we ask for it, and compliance with a legal duty. You may object to processing that rests on legitimate interest, and you may withdraw consent where consent was the basis. Objection or withdrawal does not affect processing that already happened, and it does not require us to keep providing a feature that depends on the data.

• —We do not sell personal information, and we do not share it for cross-context behavioral advertising.
• —We do not serve ads on freesyntax.dev.
• —We do not share your code, local chats, or project files with other users.
• —We do not train FreeSyntax models on your prompts or output unless you explicitly opt in.
• —We do not require an account to run the local desktop or CLI.
• —We do not upload local project files, local chats, or crash dumps from the local edition.

We may still disclose information in the narrow cases in the next section, including to the processors who run the feature you are using, and when the law requires it.

We use the following processors and, where you choose them, independent services. Each applies only when you use that part of FreeSyntax. Their own terms and privacy policies govern their systems.

• —Supabase — accounts and the database behind them.
• —Stripe — card payments and related fraud checks. See Stripe’s privacy policy.
• —Resend — delivery of account, order, and review email.
• —Vercel — hosting for freesyntax.dev.
• —Sentry — website error reports and sampled session replays. This does not run in the local desktop or CLI.
• —GitHub — public releases and update downloads, and sign-in if you choose it.
• —Google — sign-in if you choose it, and model calls if you select Google or save a Google key.
• —OpenRouter, OpenAI, and Anthropic — only when you select that provider or bring your own key.
• —Hugging Face and model hosts — when you download weights or a runtime to your own machine.

We may also disclose information to a professional adviser, an insurer, or a payment partner, bound to use it for that engagement; to a buyer or successor if we sell or reorganize the business, in which case this policy still describes the handling until you are told otherwise; and to a court, regulator, or law-enforcement authority when we believe disclosure is required or is reasonably necessary to protect people, the service, or our rights.

We do not authorize those parties to use your information for their own advertising. A model provider you select may retain prompts under its own policy. Read that policy before you send it customer data, source code, or secrets.

Account data stays while the account is open. Billing, tax, and fraud records stay as long as the applicable accounting and limitation rules require, which can be several years after the charge. Hosted prompt and output logs are removed within 30 days, unless a longer hold is needed for abuse, security, a dispute, or a legal duty. Support email is kept long enough to resolve the thread and to keep a record of what we told you, and then for as long as a claim about that thread could still be brought.

After you delete an account, we remove or detach the personal data tied to it within 30 days, except records we must keep, backups that expire on their ordinary cycle, and content you already sent to a third-party provider. Files on your computer are not deleted by an account closure. Sentry retains website errors and replays on its own schedule.

We may keep a minimal record that we deleted an account, that a charge occurred, or that a person was barred for abuse, so the same obligation or ban can be honored later. That record is limited to what is needed for that purpose.

We use access controls, transport encryption for the website, and a payment flow in which card numbers go to Stripe. No method of transmission or storage is perfectly secure. We do not guarantee that unauthorized access, a bug, or a failure of a supplier will never happen. You are responsible for the strength of your password, the devices you sign in from, and the secrets you place in a prompt or a project.

If we learn of a breach of personal information that the law requires us to announce, we will notify the people the law requires us to notify, and we will notify a regulator where the law requires that too. A notice does not admit liability.

Driftrail and its processors may handle information in the United States and in other countries where those processors operate, including where Vercel, Stripe, Supabase, Resend, Sentry, or a model provider hosts systems. Those countries may not provide the same privacy rules as your home country. Where the law requires a transfer tool, we use the mechanism that law recognizes, such as a contract with standard clauses. You may ask support@driftrail.com for a description of the safeguard that applies to your request.

Depending on where you live, you may have the right to access, correct, delete, or export personal information we hold; to object to or restrict certain processing; to withdraw consent; to opt out of a sale or share of personal information, which we do not do; and to appeal a refusal or complain to a supervisory authority. California residents may also request the categories of personal information collected and the categories of parties we disclose it to. We will not discriminate against you for exercising a privacy right. A feature that needs the data may stop if the data is deleted.

Write to support@driftrail.com. We may need enough information to find the account and to confirm that you are the person the account belongs to, or that you are authorized to act for them. We will respond within the time the applicable law requires. We may refuse a request that the law allows us to refuse, including a request that is unfounded, excessive, that would reveal someone else’s information, or that would force us to delete a record we are required to keep. We will explain a refusal and, where the law provides it, how to appeal.

We do not knowingly sell or share personal information as those terms are defined by the California Consumer Privacy Act. We do not use sensitive personal information to infer characteristics about you.

The site, shop, membership, and hosted features are for people 18 or older. We do not knowingly collect personal information from children. If we learn that we have collected it from a child, we will delete it. A parent who believes we have collected a child’s information should write to support@driftrail.com.

We may update this policy by posting a new version on this page and changing the date above. If a change materially expands how we use personal information already collected, we will provide the notice the law requires, which may include email to the address on the account. Continued use of an account or a paid feature after the effective date means the updated policy applies to that use, except where the law requires your consent for the new use.

Privacy requests, questions, and notices go to support@driftrail.com. Please use a subject line that says whether the message is a privacy request, a security report, or an account question, and include the email address on the account if there is one. The terms govern use of the service, payments, and liability.