Privacy practices for Connect beta.

• Account and profile data, including name, email, roles, organization context, and vanity profile settings.
• Marketplace, jobs, and community content, including listings, offers, applications, posts, comments, votes, reports, and moderation state.
• Private operational data such as messages, attachments, resumes, file object metadata, audit logs, rate-limit signals, and worker/outbox records.
• Technical data from requests, health checks, errors, and abuse-prevention systems.

• Operate Connect features, including marketplace, messaging, offers, jobs, community, profiles, notifications, and admin moderation.
• Protect users and the product through authorization checks, audit logs, rate limits, reports, and abuse investigations.
• Review relevant message, attachment, report, audit, and account records when needed for support, safety, abuse, privacy, or marketplace integrity investigations.
• Support beta users, process privacy requests, debug incidents, and improve product reliability.

Public profile, listing, job, and community preview fields may be visible to other users or visitors depending on the route. Votes are private; only aggregate scores are public. Private offers, messages, resumes, attachments, reports, audit rows, and exports are restricted to the roles and participants allowed by the product.

• Email privacy@subangstrom.com from the address on your SubAngstrom account.
• Use the subject line Data export request, Deletion request, or Correction request.
• Include the profile URL or organization name if the request concerns a public profile, listing, job, or community post.
• SubAngstrom staff may verify identity before exporting or deleting data.
• During invited beta, requests are staff-operated and tracked manually until the self-serve privacy workflow is promoted.