Privacy

Joro Services Ltd operates ShouldAdd. Account and product activity is stored in Supabase PostgreSQL and served through Vercel. Unsigned votes count on the public board against a hashed browser token, not against you. Suggestions and comments need an account.

What is stored, and where

Verified email authentication connects a private account to a pseudonymous username. Posts may be displayed as Anonymous, but remain associated internally for security and moderation. A signed-in session is held by the Supabase client in this browser. Unsigned votes are stored as a hash of a token kept in this browser's localStorage; the token itself is never sent in the clear to a table anyone can read. Drafts, follows and theme preference also live in this browser until you sign in.

Public records are retained while useful to the board. Account deletion anonymises retained public contributions and removes unnecessary private account data, subject to limited security and legal retention.

Service providers and contact

Supabase processes authentication and database records; Vercel hosts the application. Contact privacy@shouldadd.com for privacy requests and security@shouldadd.com for security reports.

What is not here

• No advertising identifiers or third-party embeds.
• The unsigned voter token is hashed before it is stored; it is not an identity and is never shown.

Fonts

The three typefaces are served from this site rather than from a font CDN, so loading a page does not tell anybody else that you visited.

What the database keeps

An account needs an email address so a suggestion or a comment can be attributed. An unsigned vote is one per browser, recorded against a hash of a token that lives only on that device. A signed-in vote is one per account. Retention periods are published here as they are set, and you can ask for an account and everything on it to be deleted.

Pseudonymous participation

Supabase privately stores the verified email used to secure an account. Public participation uses a username; a real name, employer and location are not required. Public profiles and APIs do not expose email addresses, authentication providers, IP addresses, private reports, moderation notes or private vote context. Companies cannot access the private identity behind a community or Anonymous contribution.

Choosing “Post without my username” hides the public profile connection, but it is not complete anonymity: ShouldAdd still associates the contribution with the account for security and moderation. Limited legal disclosure may be required. We collect only what is needed for verification, security and operation.