privacy
Help Studio

plain language

Privacy notice

What this site keeps, why it keeps it, and how to have it deleted. Written to be read, not to be survived.

Last updated 23 October 2026

The short version

Your account

When you sign up we store your username, a password hash (scrypt, never the password itself), the time you signed up, and a session identifier tied to a signed cookie. If you connect Discord, Spotify or Google, we store the provider, the provider's account id, the display name it returns, and an access token so live status can be read.

We also keep a short security history: the last few addresses that signed in, so an admin can investigate a compromised account, and a flag if the account is banned. Passwords are never logged and never sent anywhere.

Deleting your account removes the account record, the profile, the inbox and the notification history. Backups roll over on a short schedule and are not used to resurrect deleted accounts.

Your public profile

Everything you put in the studio is published — display name, bio, links, socials, widgets, music, avatar and the design itself. Treat the profile page as public writing even when the profile is unlisted: unlisted means it is not listed, not that it is secret.

Private profiles are visible only to you and to admins. When a profile is private, its card image, its share preview and its presence endpoint stop returning content to anyone else.

Messages you send to another member are stored for both of you, and are readable by admins when a report is filed. Do not use the inbox for anything you would not put in an email.

Analytics

Profile views are counted in a local database. There is no third-party analytics script on any page.

A visitor is recognised with a one-way hash made from the request's address and user agent, combined with a secret and the current date. The hash changes every day, so it can count "one visitor today" but cannot follow anyone across days, and the original address is not recoverable from it. Likes use the same scheme so that a like can be limited to once per day.

We record the country, the device class, the referring site and the path of the visit. Country comes from a local lookup, not from a third-party service.

Your own analytics page shows your views, unique visitors, referrers, countries and devices. Admins see the same aggregates for the site, never another member's individual visitor list.

Cookies and browser storage

One cookie matters: the session cookie that keeps you signed in. It is HttpOnly, SameSite=Lax, and marked Secure over HTTPS. It exists to authenticate you and nothing else.

Browser storage is used for your editor draft, your motion preference, and a small local note of which profiles you already viewed so a reload does not inflate the count. None of it is shared with anyone, and clearing site data removes it.

There is no consent banner because there are no advertising or cross-site tracking cookies to consent to.

Third parties

We do not sell data, and there is no advertising network on the site.

Your choices

If you are in a region with a statutory right of access or erasure, the deletion button and the JSON export are the fastest route; an admin will confirm in writing if you need one.

Contact

Privacy questions go to the control room through the report button on any profile, or to an admin you already know on Discord. Include the username the question is about; do not send passwords.

This notice may change as the site changes. The date at the top is the date of the last substantive edit.

Home Help Terms yourcustomprofile.app