Trust
Trust, privacy and safety
What we commit to, what is built, and what is not. Where something is only a plan, this page says so.
Status first
Nothing in the network is implemented
The network, the Jetpack app and the marketplace do not exist yet. Every commitment below about devices and workloads is a design we intend to build.
How we label maturity
- Implemented
- Built and running in production.
- Tested
- Built and exercised in a controlled test, not yet in production.
- Planned
- A design we intend to build. No working code yet.
- Conceptual
- A direction with open questions. It may change or prove unworkable.
What exists today
- ImplementedThis website, its calculator and its demo dashboard.
- ImplementedSign-up and compute-request forms: validated on the server, rate limited, and saved privately when storage is connected.
That is the whole list.
For device owners
Commitments to contributors
How Jetpack is designed to treat your device. None of this is built yet.
You choose the hours and the limits
Jetpack would only work in the hours you set, up to the power and usage limits you set.
PlannedYour use always comes first
The moment you start using the device, work would pause and step aside.
PlannedNever on battery
Laptops, tablets and phones would only take work while plugged in. Phones and tablets only on Wi-Fi.
PlannedTemperature and power caps
Caps you set would be enforced outside the sandbox, so a job could not override them.
PlannedSandboxed away from your files and home network
Each task would run in an isolated virtual machine with no access to your files, accounts or other devices on your network.
PlannedPlain statements of the electricity used
You would see how much extra electricity the work used and what it cost at your rate, next to what it earned.
PlannedLeave any time
You could stop contributing and remove the app whenever you like, with nothing left running.
Planned
For buyers
Commitments to buyers
The architecture page answers ten questions a careful buyer should ask, at the maturity we can honestly claim. Three limits matter most.
- 01
No confidentiality guarantee. A device owner controls their own hardware, so early workloads should use data you could afford to have seen.
- 02
No uptime or latency guarantees. This is for interruptible batch work, not services that must stay up or answer quickly.
- 03
No regulated data. Health records, payment data and anything covered by privacy law should not run here.
Built
This website today
The only part of SpareGrid that exists. Everything in this list is true now.
- ImplementedBoth forms are validated on the server, not only in your browser.
- ImplementedSubmissions are rate limited, protected by a same-site check, and screened by a hidden spam trap.
- ImplementedSubmissions are stored in a private store when storage is connected. When it is not, the form tells you that nothing was saved.
- ImplementedYour IP address is not stored with your submission. It is used briefly in memory to limit abuse, and our hosting provider keeps standard request logs.
- ImplementedNo advertising or analytics trackers, no third-party scripts, and no cookies set by us.
Lines we will not cross
What we will not do
No cryptocurrency or token
Buyers would pay, and contributors would be paid, in ordinary currency.
No selling of residential internet traffic
Your home connection would not be used to route other people's traffic.
No unlawful workloads
Work that is unlawful, or meant to cause harm, would not be accepted.
No hidden mining
Nothing would run on your device that you have not been told about, and cryptocurrency mining would not run at all.
No sale of personal data
We do not sell the personal data you give us, and we do not intend to.
Missing
Not yet available
Security contact, privacy policy, terms and company details are not published yet. We intend to publish them before any beta.
Until then, the most accurate description of what we do with data is this page and the notes beside each form, for example on the early-access form.