Privacy
What SparkUp stores, what it deliberately does not, and how to have it removed.
SparkUp is built so that the parts of the system that could see the most see the least. Traffic runs directly between devices over WireGuard, so the coordinator that introduces them never carries it. A relay, when one is needed, forwards packets it cannot decrypt.
What the network stores
| Where | What | Why |
|---|---|---|
| Coordinator — account | Account id, and the email address and display name from the Google account used to sign in | To recognise you across devices |
| Coordinator — devices | Device id, its signing public key, its WireGuard public key, a name you choose, the platform, when it was enrolled and when it was revoked | To prove a device belongs to your account and to let you revoke it |
| Coordinator — Circles | Circle id and name, the owner, member device ids, roles, when each joined or was revoked | To keep a Circle working when the machine at home is offline |
| Coordinator — nodes | Country, the public exit IP the node reports about itself, the limits its owner set, and when it was last seen | So people can see where a connection leaves from and the owner’s limits are enforced |
| Coordinator — sessions | Session id and the signed ticket binding both ends’ WireGuard keys | So each end can verify the other without asking a server mid-connection |
| Ledger | Signed byte counts per session, the device ids and roles that signed them, settlements between the two sides, and credit entries | To settle credit and to catch over-claiming |
| This website | Nothing, unless you use the early-access form: then your email, the options you picked, your language and the time | To send your invite |
What it does not store
- Destinations. No domains, URLs or destination addresses are recorded for user traffic, in the app or on our servers.
- Traffic content. WireGuard encrypts it end to end between the two devices.
- Your IP address in a database. The coordinator uses the address of an incoming request in memory to rate-limit it, and does not write it to storage. The web server in front of the coordinator keeps ordinary access logs, as any web server does.
- Browsing history for the person sharing. The app shows an owner totals — sessions, data, blocked connections — never where anyone went.
This website
No analytics, no tracking cookies, no advertising scripts, no embedded third-party content. Fonts are served from this site rather than from a font provider, so loading a page tells nobody else that you visited. The only data we receive is what you type into the early-access form, and the standard request logs kept by Vercel, which hosts the site.
Who else is involved
- Google, when you sign in with a Google account, and the passkey provider your device uses.
- Vercel, which hosts this website.
- Upstash, if the early-access list is enabled, which stores the sign-ups.
- Relay servers (coturn), which forward encrypted packets when two devices cannot reach each other directly. A relay can see that two addresses exchanged packets and how many; it cannot read them.
How long we keep it
Honestly: we have not yet set fixed retention windows, and we would rather say that than publish a number we do not enforce. Account, device and Circle records live as long as the account does. Ledger records are kept because credit has to be auditable. Setting and publishing real retention periods is part of getting out of early access.
Your choices
- Revoke a device at any time from the app. It loses access immediately.
- Write to contact@sparkupco.net with “Privacy” in the subject to ask what we hold about you, or to have your account and its data deleted. Ledger entries that back settled credit may be kept in a reduced form; we will tell you exactly what remains.