Privacy policy

Who we are

QuireForge is operated by James Jennison, an individual. In this policy "we" means the operator. Questions go to[email protected].

What we keep about your account

• Your email address, and when you confirmed it.
• Your password as an Argon2id hash. We never see or keep the password itself.
• If you turn on two-factor codes: the secret your authenticator app uses, and hashes of your recovery codes.
• For each device you sign in on: the name the app gives it (for example "QuireForge on Linux" or your phone's model), its IP address and network, and when it was added and last used. We keep a hash of its sign-in token, not the token.
• A record of each sign-in attempt: time, IP address, the app's user agent, and whether it succeeded. This protects your account against password guessing.
• For a paired phone: its Firebase push token and your notification settings.
• How much you use the shared model: requests and token counts per hour. Not what you asked, or what it answered.
• If you signed up with an invite code, which invite it was.

Your server and your work

Each account has its own server: a container with its own storage (10 GB during the beta), on hardware we rent from a hosting provider. Your projects, files, conversations, settings and any provider keys you add live there, walled off from other accounts. We do not read your server's contents, except when needed to keep the service running or secure, or when the law requires it, and then only as much as needed.

The shared model

When the agent uses the shared model, what it sends (your messages, and the code and files the agent includes) goes to our model server, on a GPU we rent from a cloud GPU provider. The model answers and nothing is kept there: we record only request and token counts. If you connect another provider with your own key, what you send to it is governed by that provider's terms, not ours.

Who else handles data

• Cloudflare carries all traffic to quireforge.com and api.quireforge.com, runs the human check at sign-up (Turnstile), and sends our emails.
• Our hosting and GPU providers run the machines your server and the model run on.
• Google Firebase delivers push notifications to your phone. A notification carries only which session it is about and what kind of event it is (for example "turn finished"), never your project names or messages. The wording is added by the app on your phone.

We do not sell your data, show ads, or use analytics or trackers, in the apps or on this website. This website sets no cookies.

Email

We email you only about your account: confirming your address, resetting your password, a new sign-in, a changed password, or deleting your account, and about changes to these terms or this policy.

Keeping and deleting

We keep your account and your server while you have an account. You can delete your account from the desktop app, under Settings, then Account. Every device is signed out straight away, and your account, server, files and usage records are deleted within a day. Backups, if any, are replaced within 30 days. Sign-in records of failed attempts on addresses with no account are kept for up to 90 days.

You can ask us for a copy of what we keep about your account, or to correct it, by emailing [email protected].

Security

Connections are encrypted. Passwords and tokens are stored only as hashes. Each account's server runs in its own container with no access to other accounts, our network, or the model server beyond its own requests. No system is perfectly secure; if we learn of a breach that affects you, we will tell you by email.

Children

QuireForge is not for anyone under 16, and we do not knowingly keep their data.

Changes

If we change this policy in a way that matters, we will email account holders before the change takes effect. The date at the top shows the latest version.