Security and privacy

Signing in

You sign in with a six-digit code sent to your email, or with Apple (on iPhone) or Google. There are no passwords in the app, so there is no password to leak or reuse.

Sessions use short-lived signed tokens, valid for an hour and refreshed automatically. Functions that act for you build their database connection with your own token, so the same row-level rules apply inside a function as inside the app.

The database enforces access

Row-level security is on for every table. Your library, wishlist and notifications are readable only by you. The catalog is readable by signed-in users only, and an anonymous client can neither read nor run anything.

The free-tier game cap works the same way: a database trigger enforces it, not the app counting.

Secrets stay on the server

IGDB, Steam, Xbox, language-model and push credentials exist only as backend function secrets. The app ships only public identifiers. Even if someone unpacked the app, there would be nothing in it to steal.

Linking a platform is a connection, not a sign-in

Connecting Steam or Xbox starts from an account that is already signed in. The return trip from the platform is only useful together with a one-time token tied to that signed-in session, so a link made for one person cannot be redeemed by another. Prysm never sees your Steam or Microsoft password.

Payments

Purchases go through the App Store or Google Play. The backend learns who is Pro only from RevenueCat's notification, and the app cannot write its own subscription status.

Content safety

You can block and report people and posts. Blocked accounts disappear from each other's feed and search.

Deleting your account

You can delete your account inside the app, or on the web at /delete-account. Deletion removes the account, every row that references it, your uploaded images and your RevenueCat customer record.

What is stored and why is set out in the privacy policy.