What we log during the beta

Nothing is collected for the beta that is not collected in normal use. This is what that is, because a tester spends the day making errors happen on purpose. Every period below is in the Privacy Policy.

What is recorded

Errors

Sentry, through our own domain at /monitoring. An error carries the page, your browser and a stack trace, with tokens and email addresses removed first. Sentry keeps it 90 days.

Speed

For a sample of page loads, how long the page and its requests took, scrubbed the same way.

Screen recordings

Only when an error happens, never on their own, with all text, every input and all media masked. They show the shape of the page and where you clicked, not what you typed.

A feedback report

What you wrote, the page, your browser, window size and time zone. It is a support ticket with your email on it.

Sign-ins

The time, your IP address, your browser and a rough location from it, for the new-device email and Settings → Security.

Rate limits

A count per account, or per IP address when signed out, for each limit. Not what the request contained.

What is not recorded

• What you type: notes, messages and drafts stay in your account, not in any analytics.
• Card numbers. Payment details go from your browser to Stripe or PayPal.
• Your password, which is stored only as a hash that nobody can read back. Backup codes are stored only as hashes too. Your two-factor secret is kept where only our server can reach it, and staff never see it.

Rules and limits

• A daily job deletes what has passed its period.
• Settings → Account → Data Export downloads what is yours, beta or not.
• The companies that process it are listed in the Privacy Policy, and Architecture maps what runs where.