Skip to content
SqwakieHome

Privacy Policy

Effective date: October 17, 2026 Provider: RC Studios, San Francisco, California Contact: support@sqwakie.si

What Sqwakie handles

The public site serves pages and assets and remembers a theme choice in your browser. The public site uses Vercel Web Analytics, which sets no cookies. It counts page views and a few events: clicks on the Buy, Copy and GitHub links, visits that arrive with campaign tags (utm_source, utm_medium, utm_campaign or ref), returns from checkout, and downloads of install.sh by type of client (curl, wget, browser or other). Page addresses are sent without the part after # (where join links carry their secret) and without the checkout session ID; campaign tags are the only part of the query kept. For a visit from another site, the address of the page that linked here, as your browser reports it, is also sent. For install.sh downloads, our site passes the request's user agent and IP address to Vercel Web Analytics and logs the client type and country. The site has no advertising SDK. Hosting providers may receive ordinary request metadata, including an IP address and keep it under their own logging and retention policies.

For purchases, Stripe handles checkout, payment details and billing portal access. Sqwakie's site API reads subscription ID, billing email, plan, seats, interval and status to issue and renew a team license. It stores team and renewal metadata with Stripe; the renewal token is stored as a hash. A team authority checks the license periodically. We use this information to deliver paid access, prevent duplicate subscriptions and handle billing changes.

Rental compute: when an owner rents machines, the compute API processes team and account identifiers, proof and token hashes, prepaid credit and ledger entries (including credit that expires 60 days after purchase), rental and machine identifiers, lifecycle dates, heartbeats, load and egress readings, and IP-based rate-limit keys. It also keeps, per team, which licence subscriptions are bound to it. Stripe processes credit purchases. A Postgres database stores the compute records, and DigitalOcean provisions the rented instances; everything on a rented machine is deleted with it when it stops. These records are used to authorize and operate rentals, account for credit, control abuse and support recovery.

Rental compute handovers: if your team uses rental compute, an owner's Sqwakie daemon also sends the team's roster to our site while a change of the team's compute account authority (a handover) is being confirmed. That happens only for a team whose compute account has been funded, holds credit or machines, or has a credit checkout open: on the daemon that proposed the handover until it completes, on a daemon whose compute account shows a handover pending while it is pending, and on any other current owner's daemon after another owner's daemon posted the handover notice in the team's #general channel, until it has acknowledged it or our site says there is nothing to act on, and for at most 72 hours after the notice. A team with no funded compute account (no credit bought or granted, no machines, no checkout open) sends nothing: not at install, not at start, not ever, unless an owner runs walkie compute handover object. A team that bought credit but never rented a machine is funded, so its owners' daemons can send the roster during a handover. That command sends one status check with the same roster, on any team, and, if a handover is pending, an objection that carries the roster too. Routine compute checks by an account holder send only the account's token. Each check is sent at once, then at most every 10 minutes, backing off after failures. It carries the team ID, the sending machine's public key, an expiry and a signature, and the team's signed roster: the team's founding record (team ID and name, the founding owner's login and handle, the founding machine's ID, hostname, public key, IP address and port), the admission records of everyone who was ever an owner (login, handle, role, display name) and of their machines (machine ID, login, hostname, public key, IP address, port and connection settings), and the records of every transfer of the team's roster authority. Your IP address reaches the site with the request. An owner's acknowledgement of a handover also carries the signed notice post. Our site keeps rate-limit rows holding the IP address, the team ID and the owner's key with an hourly count; they are deleted once older than 24 hours by a later clean-up, so on a quiet site one can stay longer. It keeps the roster only inside the record of a handover that is already pending, and clears it when the handover completes, is rejected or is cleared; for a team with no pending handover nothing from the check's content is kept. A status check (and an objection) does leave a lock row in our database keyed by the team ID, with no other content, which is not deleted; for a team that uses compute that row already exists. An objection to a pending handover is recorded in that handover's record (the objecting owner's public key), and the operator is alerted with it. Our code logs no roster content. Our host's own request logs (IP address, path, status) follow the host's retention, which our code does not set.

Release notes by email: if you sign up on the home page, our site API stores your email address, whether it is confirmed, when you signed up, last asked for a link and confirmed, a one-way hash of each confirmation code and a random unsubscribe code. To limit abuse it also counts signup requests per one-way hash of your IP address and of your email address. Resend sends these emails. We use the address only to send Sqwakie release notes. A confirmation link stops working after 48 hours. Counts older than a day, and an address that was never confirmed and has no working link, are deleted by the next signup request anyone sends (for an address, at the earliest 10 minutes after its last signup request); a confirmed address is deleted when you use the unsubscribe link that every one of these emails carries.

Data on your devices and in transit

The daemon stores team events on customer machines. Team members receive the agent and machine status, messages, questions and files they share. Account usage meters share a masked provider email, plan and usage by default; you can turn them off. Prompt titles and command text are shared only if you opt in, with best-effort secret scrubbing. Agent transcripts and project data remain on customer machines unless someone chooses to share content. The account vault and its login material stay on the owner's machine, although authorized lending can send a limited credential to an approved team machine for a run.

The paired phone keeps a device ID, room, labels and an encryption key in local IndexedDB or, when storage is unavailable, in memory for that visit. It remembers a dismissed install prompt in localStorage. Its narrower team view includes agents, machines, asks and channel posts, not files or provider-account details. The Fly.io-hosted phone relay can see connection details such as IP addresses, connection IDs, which phone connects to which computer, timing and traffic volume. It cannot read the end-to-end encrypted content.

Sqwakie Direct uses n0's public address lookup and, by default, its relays. n0 can see IP addresses and which endpoints connect; relay traffic is encrypted. Customers can configure their own relay, but this release still uses n0 discovery. A team using Tailscale also uses its tailnet service. Team content is encrypted between customer devices, not stored by our site API.

Who processes data

Vercel hosts the site and API; Fly.io hosts the named phone relay; Stripe handles payments and subscription metadata; n0 supplies Direct discovery and default relays; Tailscale is optional. Rental compute and the release-notes signup use a Postgres provider (Neon); rental compute also uses DigitalOcean; Resend sends release-notes email; Telegram receives selected, sanitized compute operational alerts containing identifiers and event details when configured. GitHub hosts linked source and release downloads. Claude Code and Codex use your separate model-provider accounts. Their own terms and logs may apply.

Retention and choices

Team data and the vault remain on your devices until you or your team remove them. You can change team sharing settings, turn off usage meters, remove a phone pairing, cancel a subscription through Stripe and stop using hosted features. For rental compute, we intend to keep the billing ledger for seven years and rental and request records for one year. Stripe, our hosting providers and other vendors keep their own records under their own retention policies.

For access, correction, deletion or other privacy requests, contact support@sqwakie.si. We will assess requests under applicable law and the limits of data we hold; customer-controlled device data may need to be handled by the team that controls those devices. Provider: RC Studios, San Francisco, California. Governing law for the related Terms: the laws of the State of California.

Sqwakie · RC Studios