How we protect your Nest

Plain language, no security theatre. Last updated: 28 July 2026

The short version

Your Nest is visible to exactly two accounts — yours and your partner's — and that rule is enforced by the database itself, not just by the app's screens.

Isolation between Nests

Every table carries row-level security policies: a signed-in user can only ever read rows belonging to their own Nest. All game actions run through server-side functions that re-check membership on every call. Even a modified or malicious client cannot read another couple's data.

Consent enforced in the database

The sensitive reveals have their rules in the database layer: your daily quiz answer is unreadable to your partner until they have answered too, and monthly Weather check-ins are unreadable unless both partners submitted and both consented. This is not a UI curtain — the database refuses the read.

Encryption

All traffic uses TLS (HTTPS). Data is stored on encrypted-at-rest EU infrastructure (Hetzner, Finland/Germany), fronted by Cloudflare. Passwords are hashed with bcrypt; magic-link tokens are single-use and expire within one hour.

Invite codes

Invite codes are 6 characters from an unambiguous alphabet, single-Nest, and become useless once your Nest has two members. You can regenerate your code at any time in Settings if one leaks.

Who can technically access data

Honestly: the founders can access the production database for maintenance and support, as at nearly every small company. We do not browse user content, access is limited to two people, and every access happens over audited SSH. As we grow, we will add stricter internal controls and publish them here.

Payments

Card data never touches our servers — Stripe handles the entire payment. We store only which pack was bought and a Stripe reference.

Backups and deletion

Encrypted backups exist for disaster recovery and roll off within 30 days. Account deletion takes effect immediately in the live database and reaches backups as they expire.

No tracking

No analytics scripts, no ad pixels, no fingerprinting, no third-party cookies. The only cookies/storage we use keep you signed in.

Reporting a vulnerability

Found something? Please email [email protected] with the details. We reply within 72 hours, fix in good faith, and happily credit you. Please do not access other users' data while testing.