Privacy policy

What Ruffian keeps about you, why, and who else handles it.

The short version

Who runs Ruffian

Ruffian runs ruffian.ai and git.ruffian.ai. Contact: william@ruffian.ai.

What we keep

Your account. From Clerk, our sign-in provider: your email address and name. If you sign in with Google, the profile Google shares with us: name, email address, picture. If you sign in with Apple, the email address Apple shares with us (which can be a private relay address Apple makes for you). Our own record: your plan, your account status, the devices you have signed in (their keys are kept only in scrambled form), and when you last used Ruffian.

Your workspace. The files in your workspace, your conversations and their history, on the computers that run Ruffian. Projects you save to git.ruffian.ai, on our server.

What you attach. A photo, file or picture you take with the camera is uploaded into your workspace (or into the group chat you post it in) only when you choose it. The apps never read your photo library, files or camera on their own; Android's photo picker hands over only the photos you pick.

Group chats. What you post in a group chat (messages, photos, files, voice clips) is kept on our server and seen by the people and agents in that chat.

People and invites. When you invite someone, we keep the invite and, if you typed one, their email address, and we may send them one invitation email. The apps never read your phone's contacts.

Live rooms. Where live rooms are on, a group chat can start a call. Your audio and video go between the devices in the room (WebRTC, encrypted); when two devices cannot reach each other directly, our relay server passes the encrypted stream along. We do not record calls. A shared video or music card opens YouTube or Spotify, under their own privacy policies.

Published pages. A page or project you publish is public: anyone with its link can see it, until you unpublish it or delete your account.

Reports and blocks. If you report a reply or a message, we keep its text, who wrote it, the chat it was in, and your reason. If you block someone, we keep that you did. The person you report or block is not told.

Logs. Server records of requests and connections (times, account id, sizes). They hold no passwords, tokens or keys.

Devices. The kind of device and app each connection comes from: app or browser and version, operating system and version, phone or computer model, processor type, language, time zone, screen class, and terminal type. We link it to your account and to your sessions, crashes and errors, to see which devices need work. No device names, contacts, location, advertising ids or IP addresses go in it. Entries not seen for 180 days are deleted.

Crash reports. If an app crashes, it sends a short note: the kind of error, its message and the line it happened on (300 characters at most), with the device details above. It holds none of your conversation.

Location. Ruffian does not collect your location. The apps do not ask for it.

How we use it

To run the service and to improve it. Your sessions on Ruffian can be read by the Ruffian admin (William) to improve the product. They are read from backup copies, never in your live workspace. Your data is not used to train models without your explicit consent.

The assistant and outside AI services

The assistant runs on Ruffian's own computers (rented from Vast.ai); your conversations are not sent to an outside AI company to answer you.

Personal suggestions. A new chat shows starter ideas. Personal ones, made from what you have been doing lately in Ruffian (your recent chats and projects) and seen only by you, are being rolled out and may not be on for you yet. To write them, about once a day an extract of that recent activity (your recent chats' titles and your own words in them, not the assistant's replies; your published project names; which devices and features you use) is sent to an AI model run by Anthropic, under its commercial API terms, which do not allow it to train on that data. They are optional: turn them off in Settings > New chat > Personal cards (Off), and nothing of yours is sent for them.

Your own keys. If you give Ruffian your own key for another service (for example an AI API), the requests you ask for go to that service under your own account with it, and its privacy policy applies to them.

Web browsing for you

When you ask, the assistant can open public web pages with a browser on Ruffian's computers. It uses its own browser, with none of your cookies or passwords. If you install the Ruffian Chrome extension and allow it, the assistant can also act in your own Chrome tabs; you approve each new site and each sensitive action there, and your cookies and saved passwords never leave your computer. Only what the task needs (page text, small screenshots) comes back into your chat.

Domains and payments

Domains. If you buy a domain through Ruffian, your registrant contact details (name, address, phone, email) go to our registrar, Porkbun, and to the domain's registry, as every domain registration requires. WHOIS privacy is on, so they are not published.

Payments. Where paid plans are offered, payments are handled by Stripe. We keep your plan, its status and Stripe's reference for you; we never see or keep your full card number.

Notifications

The Android app checks for new group chat messages by itself about every 15 minutes, and tells you when a reply you left running is done; it uses no outside push service. The iPhone app and browsers can get push notifications through Apple's or the browser maker's push service; those messages name no words of your chats.

Who else handles it

Your data is not sold, and it is not shared except with the companies that run parts of the service:

Clerk
sign-in and accounts
DigitalOcean
the server for ruffian.ai and git.ruffian.ai, and its backups
Vast.ai
the computers where workspaces and the AI run
Cloudflare
bot protection in front of Clerk's sign-in
Our email provider
sends the welcome and invitation emails
Stripe
payments, where paid plans are offered
Porkbun
registering a domain you buy
Anthropic
personal suggestions, only while Personal cards is on for you

Google handles your sign-in only if you choose to sign in with Google.

Cookies

A sign-in cookie, set by Clerk when you sign in; Clerk's sign-in page also gets Cloudflare's bot-protection cookie. A passcode cookie, set when you open the site with a passcode. No tracking or advertising cookies, and no third-party analytics.

Google Calendar and Gmail

Only if you connect them (Settings > Connected accounts): Ruffian reads your calendar and mail when you ask it to, and sends an email only when you tap Send. The access tokens are kept encrypted on our server. Disconnect any time; deleting your account revokes them.

Voice

In the iPhone app's voice mode, what you say is turned into text by Apple's speech recognition (on your iPhone when it can; otherwise Apple's servers handle the audio, under Apple's privacy policy), and only the text is sent to Ruffian, like a typed message.

On Android, voice mode uses your phone's speech recognition service, and only the text is sent to Ruffian. That service may send the audio to its maker (usually Google), under its own privacy policy.

A voice clip you send in a group chat is different: it is uploaded and stored as a file in that chat, like a photo.

Children

Ruffian is not meant for children. You must be at least 13 to use it. If we learn that an account belongs to someone younger, we close it and delete its data. How we deal with child sexual abuse and exploitation: child safety.

Deleting your data

In the Ruffian app on iPhone: Settings > Account > Delete account. On Android: Account > Delete account (tap your name at the bottom of the chat list). Or email william@ruffian.ai. We delete your account and sign-in, your conversations and workspace, your projects, your published pages and your Google and GitHub connections. A deleted workspace is held for up to 7 days in case of a mistake, then erased; daily backups of the account database are kept for 14 days, then replaced.

Changes

Changes are posted on this page. In effect since October 23, 2026; last changed November 8, 2026 (what you attach, invites, live rooms, published pages, crash reports, outside AI services, personal suggestions, web browsing, domains, payments, notifications). See also the terms of use.