Privacy and contributions

What is stored when you contribute

• Corrections and suggestions: your message, selected platform or suggested name, topic and optional source link. These enter a private review queue.
• Experiences: your message, platform, applicant or worker relationship, and any display name, work type or experience period you provide. A display name can be a pseudonym.
• Discussions and reports: topics, replies, edits, mentioned platforms and reports about published posts. Discussions are linked to your account.

Submissions also have a receipt ID, submission time and review history. Guest submissions retain a hash derived from a random browser identifier to limit abuse and recognise retries. Submitting while signed in links the contribution to your account.

Who can see your contribution

Site administrators can read submitted content and moderation records, and can export them for review. Corrections, suggestions and reports are not displayed as public comments; they can inform updates to the directory.

Experiences, discussion topics and replies become public only after review. Moderators choose the published text and may remove private details. Published experiences include the reviewed message, your chosen display name if supplied, relationship, optional work details and publication date. Discussion posts show the reviewed text, public name, platform mentions and dates. Sign-in email addresses and browser identifiers are not included in these public views.

By submitting an experience or discussion, you agree that its reviewed text and supplied public details may appear on the site. Write only what you are comfortable making public. Leave out account credentials, contact details, identification documents, other people’s personal information and confidential task material. A pseudonym does not prevent someone recognising details of your experience.

Published experiences and discussions have report links for raising concerns. A report enters the private review queue; it does not automatically remove the post.

Browser storage

Card display choices, automatic loading preferences, saved platforms, application status and personal notes stay in this browser’s local storage. They are not sent to the server or synced to an account. Anyone using the same browser profile can read them. Removing a platform from Saved keeps its notes for later; use “Clear notes and status” to erase them, or clear site data to remove all saved items and notes.

Unsaved note drafts are kept in this tab’s session storage while you browse. Use “Save notes" to keep them after closing the tab. Drafts are not sent to the server.

The private backup controls in Saved can download your shortlist, application statuses, saved notes and unsaved drafts as a JSON file, including notes for platforms you unsaved. Import reads a selected file on your device and previews changes before writing browser storage. Backup contents are not uploaded or synced to an account. Downloaded files are plain text without encryption; anyone with the file can read them. Exporting a draft does not save it as a finished note.

Search terms, filters and comparison selections can appear in the page URL and browser history; shared URLs include those values. Personal notes and application status are excluded from URLs and directory search.

Opening a platform profile also saves your results filters and scroll position in browser storage so you can return to where you were. This return context is not included in shared profile links.

Contribution forms set a first-party cookie containing a random visitor ID. It expires 24 hours after the form connection is created or refreshed. A derived identifier remains with submitted records. The cookie supports submission limits, retries and linking a recent guest contribution to an account in the same browser.

Optional accounts

When sign-in is available, an account stores your email, sign-in identity, public name, contributions, followed discussions and reply-notification preference. Sign-in uses a session cookie, with a seven-day session that can renew as you use the site. Email stays private; your chosen public name appears on reviewed posts.

Email sign-in sends your requested code through Resend, which receives your email address and the sign-in message.

Google sign-in shares your Google account identifier, email and basic profile details with the site. Provider access and refresh tokens are not retained in the account records.

Your account provides contribution status, editing and withdrawal controls. Editing an experience or discussion returns it to review. Changing your public name applies to future posts; already reviewed posts keep their published name.

Retained records and external sites

The beta retains original submissions, revisions and moderation decisions, including declined or withdrawn content. Withdrawal hides published content from readers; it does not delete its private history. There is currently no self-service account deletion or automatic contribution-deletion schedule.

The hosted site and database run on Railway. This notice does not set a retention period for hosting logs or backups. Opening a source or application link takes you to another service with its own data handling and terms.

Contact and privacy requests

Email admin@aiworkplatforms.com about access, correction or removal of your data. Include a relevant page URL or submission receipt if available. We may need to confirm that the request concerns your account or contribution.

Contact email is forwarded through Porkbun to an administrator’s Gmail inbox. Those providers process the email address, message and any attachments you send. Contact messages are private and are not automatically published.