Privacy Policy

1. What we collect

Account

When you sign in, we receive your user id, username, primary email address and avatar URL from the sign-in method you use. We do not receive your password and we do not read your repositories unless you install the ParallelSandbox app on them.

ParallelSandbox API keys

These are the keys you create in ParallelSandbox so that an agent can connect to your account (they start with psbx_). We keep only a hash of each key (used to check the key sent with each connection; it cannot be turned back into the key), its first few characters (so you can tell keys apart in the list), its name, and when it was created, last used and revoked. The full key is shown only once, when you create it. Keys for your other services that you store as secrets are not covered here; they are stored encrypted (see section 6).

Usage

For every box: its id, start and stop times, the services and wiring you declared, the state changes, and usage events (minutes run, bytes transferred, bytes of logs written and stored, bytes of files kept) with the credits charged.

Files, screenshots and recordings

Screenshots and recordings taken in your boxes, files you fetch from a box, the build cache (sandbox_build) and the images you push to your account's registry are stored in the Service's storage; section 5 says how long each is kept.

Logs you send

Pages that use the log SDK send whatever you configure them to send: messages, stacks, URLs, release ids, box ids. You decide what goes in. If it includes personal data of your own users, you are the controller of that data and responsible for informing them.

Messages

Messages you send to the agent on a box from the app, with any images you attach, and the messages the agent posts there are kept for 7 days, together with the box's activity record: a short summary of each action, such as the command that ran, never its output.

Voice input

When you press the microphone in the app, the audio is streamed through our server to a speech-to-text service, with your account's language, and the text comes back to the app. Our server does not store the audio or the text; its logs only note that your account used voice input, in which language and for how long. The text you then send is stored like any other message you write.

Push notifications

When you sign in on the iOS or Android app, the app registers with us the device's push token, with the platform (iOS or Android), tied to your account. We use it to tell you when a box asks for a person to take over and when your account runs out of credits, including a reminder before your boxes are reclaimed. The token is deleted when you sign out on that device, when it stops being valid, or when you delete your account. The content of each notification (for a takeover: the box id, the note the agent wrote when it asked for you, and a link to the takeover; for credits: when your boxes will be or were reclaimed, and a link to billing) passes through push notification services on its way to your device.

Billing

A payment processor handles payments. We receive a customer id, subscription status and invoice records. Card numbers are handled by the payment processor and never reach us.

Support and website

Emails you send us are kept to answer them. The website uses no analytics or advertising cookies; web servers keep standard access logs (IP address, browser type, requested page) for security, deleted after 30 days.

2. What we do not collect

We do not inspect the contents of your boxes, your code or your logs in the ordinary course of operating the Service. We do not sell personal data and we do not use it for advertising.

3. Why we use it

• to provide the Service: start boxes, route takeovers, store what you asked for;
• to bill you and keep the accounting records the law requires;
• to keep the Service secure and detect abuse;
• to answer your support requests;
• to comply with legal obligations.

4. Who receives it

The Service is hosted on Amazon Web Services (AWS). iPhone simulators run on dedicated Mac hosts: when you use an iPhone simulator, the app you run on it is sent there. Payments, sign-in, speech-to-text and push notifications are handled by their own service providers, and each of them receives only what their role requires. We disclose data to authorities only when legally compelled, and we tell you when we are allowed to.

5. How long we keep it

• Box contents: destroyed when the box stops.
• Screenshots and recordings: 7 days.
• Files fetched from a box (sandbox_get, sandbox_pull): about 1 day.
• Contents of frozen boxes (memory and /work): deleted when the box resumes or stops, at most 10 days.
• Frozen-box posters and review card images: only the latest one per box, until you close your account, then removed within 30 days.
• Build cache (sandbox_build): at most 20 GB per account, oldest removed first; removed within 30 days after you close your account.
• Images in your account's registry: until you close your account, then removed within 30 days.
• Logs and source maps: until you delete their log project or close your account, then removed within 30 days.
• Messages and activity records: 7 days.
• Voice input: neither the audio nor the text is stored.
• Push tokens: until you sign out on that device or delete your account.
• Account and usage records: for the life of the account, then removed within 30 days, except the billing records below.
• Billing records, including credit purchases and usage: as long as tax and accounting law requires, also after you delete your account, without your profile.
• Web server access logs: 30 days.

6. Security

All traffic uses TLS. Boxes are isolated from each other, except through links you declare between boxes of your own account, and hold no cloud credentials of their own (if you name an AWS role on an environment, boxes started in that environment receive temporary credentials for that role), and accept only one-time tokens issued by the control plane for takeovers. Secrets are encrypted at rest and never written to platform logs. API keys are stored as hashes.

7. Your rights

You can delete your secrets and log projects (with their logs and source maps) and revoke API keys over the API at any time, and delete your account from the account page. For a copy of the data we hold about you, a correction, or deletion of anything you cannot remove yourself, email us; we answer within 30 days. Depending on where you live you may have further rights under laws such as the GDPR or the CCPA, and we honour them.

Delete your account explains the steps, what to do when you cannot sign in, and what is deleted and what is kept.

8. Children

The Service is not directed at children under 16 and we do not knowingly collect data from them.

9. Changes

We may update this policy. The current version is always at parallelsandbox.com/privacy/ with the date of the last change; material changes are announced in the app.

10. Contact

Privacy questions and requests: runvo.tech@gmail.com