Privacy policy

What we collect

• During verification, your work email is sent to our email provider and converted into a keyed, one-way hash. The plain address is not written to the Open Label database.
• Your pseudonym, broad verification badge, posts, replies, votes, reports, and any images you choose to publish.
• Salary-survey answers, including role, employer information, location, compensation, experience, and optional comments. The survey is not linked to a member account or email.
• Short-lived, keyed hashes of network identifiers used to prevent automated email and survey abuse. These rate-limit events expire after 48 hours and are purged during recurring maintenance. Copies may remain in rotating backups for up to seven days.

How we use it

We use verification data to create a persistent anonymous member, community activity to operate and moderate the forum, and survey responses to publish compensation benchmarks only after a cut has at least eight responses. We do not sell personal information or use advertising trackers.

Providers and international processing

Railway hosts the application and its primary storage. Resend delivers one-time verification emails. Cloudflare provides domain and email-routing infrastructure and, when configured, private off-volume backup storage. Their systems may process technical request or delivery data under their own privacy and security terms.

Retention and deletion

Member accounts and published contributions remain until removed by the member or through a verified support request. Moderation records may be retained to prevent repeat abuse. Salary responses are intentionally unlinked; because we cannot identify which row belongs to a respondent, we generally cannot retrieve or delete a particular response later. Do not put your name, patient details, study identifiers, or confidential information in a survey or post.

Your choices

You may ask for access, correction, deletion, or another privacy request by emailing privacy@openlabelhq.com. We may ask you to verify control of the work email associated with the account hash before acting on an account request.

Security and changes

We use signed sessions, short-lived login links, access controls, abuse throttles, encrypted transport, and recurring backups. No system is perfectly secure. Material policy changes will be published here with a new effective date.