Privacy policy

What the hosted copy of Runlog stores about you, where it is, and how to have it deleted.

Version 2026-09-07 · applies from 2026-09-07

1. Who is responsible

Secret Headquarters, LLC, a company in Texas, United States, operates the service at runlog.scrthq.com and is the controller of the personal data described here. Contact: runlog@scrthq.com.

2. Using the app without an account

The app runs in your browser. Your packs, runs, settings and any license keys are kept in the browser's own storage on your device. They are not sent to us. The only requests your browser makes are for the app's files and, when you open the catalog, for the list of packs. Nothing about those requests is kept (see section 6).

The same app can be downloaded and run from a file on disk, in which case no request reaches us at all.

3. What an account adds

When you sign in, we store on our servers:

Your sign-in

Handled by WorkOS, which holds your email address, your name if you gave one, and the passkey, password or provider you sign in with. We receive an identifier, and the app reports the name and address to us so we can show them and address invitations.

Your runs

Every move in a synced run, with the time it was made and which account made it, so devices can share the run.

Your packs

Packs you have switched sync on for, in full, so your other devices can play them. Packs marked not redistributable are still only ever shown to you.

License keys

The keys for sealed packs you have bought or been given, so they follow you between devices.

Invitations

The email address you invite, who invited them, which run, and whether the invitation was used. We send one email to that address and nothing else, ever.

People you played with

A list of accounts you have shared a run with, so the next invitation is a name rather than an address.

Your profile

When the account was first seen and last seen, the run you touched last, which version of the terms you accepted, and, when plans are on, which plan you are on.

Command-line keys

A hashed copy of any API key you make for publishing from the command line, with its label and when it was last used.

Discord

If you link a Discord account: its Discord user id and display name, and when you linked it. If you claim a Discord server for the Runlog bot: the server's id and name, which role may host runs there and which channel they open in, and which runs the bot hosted there. A pack you delegate to a server is kept in full for that server, read only by the bot to host runs on it, and never sent to anyone. A run the bot hosts is stored like any synced run, under the host's account; a member who joins its roster or takes a seat is written into it by their Discord id and display name.

4. Payments

When plans and the marketplace are switched on, payments are taken by Stripe. Stripe holds your card details; we never see them. We keep the Stripe customer identifier, which plan you are on, and for a purchase: which pack, the amount, when, and the address the receipt went to. A publisher sees the sale in their ledger with the buyer's email address, because a license belongs to a person and they may need to reissue it.

5. Why we process this, and on what basis

• To provide the service you asked for: sync, invitations, purchases (performance of a contract).
• To keep the service secure and to answer support: service logs, key hashes (legitimate interest).
• To send the one invitation email a player asked us to send (legitimate interest of the inviter; you can ignore it).
• To meet legal duties around payments and tax (legal obligation).

We do not profile you, we do not advertise, and we do not sell or rent any of this.

6. Logs and counts

The edge keeps no access logs. The API keeps two kinds of line, both without addresses and without request bodies: a service log of when a request failed and why, and an access log of which route was asked for, when, with what result and how long it took. Both are kept for one month by Amazon CloudWatch and then deleted. Sign-in attempts are logged by WorkOS under its own policy.

We also count. The app tells us which of its screens were opened, which version of the app it is, and which country the request came from, and we keep those as totals per day. No identifier, no address and no cookie is involved, so the totals cannot be tied to a person, and the app sends none of this when your browser sends a Do Not Track or Global Privacy Control signal.

7. Who else sees data

We use these providers, each under its own terms, to run the service:

Amazon Web Services

Hosting, storage and email, in the United States (us-east-1 and us-west-2).

WorkOS

Sign-in and sessions.

Stripe

Payments and payouts, when plans are on.

New Relic

Monitoring of our servers: how long requests take and what went wrong, with no request bodies, no addresses and no tokens.

Discord

Where a server has added the Runlog bot: Discord sends us each command and press made on it, with the member's Discord id and display name, and we post the bot's messages (the run's card, the lines under it, its live link) into that server, under Discord's own terms.

Data is stored and processed in the United States. If you are in the EU, the UK or another place with rules on sending data abroad, ask us and we will tell you what safeguards apply to yours.

8. How long we keep things

• Account data: until you delete your account.
• Invitations: seven days if unused; the record of an accepted one lives with the run.
• Purchase records: for as long as tax law requires, typically seven years, even after the account is closed.
• Service logs: one month.
• Discord link and claim codes: ten minutes if unused.
• The record of which runs the bot hosted in a server: thirty days after the run ends; the run itself lives with the host's account.

9. Your rights

From your profile in the app you can download everything we hold about you as one file, and delete your account with one button, which deletes what we hold immediately. Purchase records stay for the period above. Depending on where you live, you also have rights to access, correct, restrict, port and object, and to complain to a supervisory authority; write to runlog@scrthq.com and we will answer within a month.

10. Children

The service is not directed at children, and we do not knowingly hold an account for anyone too young to agree to the terms. If you believe we do, tell us and we will delete it.

11. Changes

When this policy changes in a way that matters, the app asks you to read and accept it again, and the version and date at the top change.