TradesRosterSign in

Privacy

Effective September 19, 2026. TradesRoster is operated by Kevin Spahn. Contact hello@kevinspahn.com with privacy questions.

Account and profile information

You can sign in with Google or an emailed sign-in link. Signing in provides your account identity and email address, and may also provide your name and a picture, depending on the method you use and what you have shared with that provider. You can set or replace the picture in your profile. We store linked sign-in records to authenticate you. Your account email is separate from the contact email you choose to publish. The sign-in methods offered on the sign-in page are the only ones in use.

Visibility, location, and work

Profiles start visible to signed-in members only. You can explicitly make your profile public in your settings. Public profile information, contact details you publish, credentials, projects, and work photos can be seen and indexed outside TradesRoster. Member-only profiles and work require sign-in; they are visible to other members, not just people you follow. Visibility changes cannot recall screenshots, search indexes, or external copies.

City, state, ZIP, and an approximate postal centroid support nearby search. We do not request device GPS or a street address. Distances are approximate. Media is processed for display and stored with a cloud storage provider. Photos and profile pictures are re-encoded to remove embedded metadata. Private media uses expiring download links; someone who has a link can use it until it expires.

Participation and conversations

Jobs, availability, follows, likes, endorsements, and discussions support the member network. Jobs, availability, and discussions are member features. Direct messages are available to the conversation participants. Site operators can access stored records when needed to operate the service or investigate abuse. Messages are not end-to-end encrypted. Blocking controls interactions independently of reporting; it does not erase previously delivered messages.

Notifications and service records

We store in-app notifications and your email notification preference. Notification email is sent only when you enable it and mail is configured. Necessary session cookies keep you signed in. Hosting and application logs help diagnose failures.

We record limited first-party sign-in, profile setup, publishing, media, follow, job, availability, and messaging milestones with account ID when one exists, time, environment, and release version. We also count fixed workflow error categories such as sign-in, profile, media, jobs, messaging, and notifications. These records do not include submitted text, contact details, precise location, message bodies, error messages, stack traces, page addresses, or report text. Anonymous sign-in starts contain only a random attempt identifier. We do not use advertising analytics, advertising trackers, or analytics cookies, and we do not sell member information.

For visits made while signed out, we use Umami, an analytics tool we host ourselves, to count page views. For each page view it records the page address without its query string, the page title, the referring site, the browser, operating system, device type, language, and screen size, and the country, region, and city estimated from the IP address. It uses the IP address and browser identification to compute a visit identifier that changes each month; it does not store the IP address. It sets no cookies, honors the browser's Do Not Track setting, and is not shared with advertisers. It is not loaded on pages you open while signed in, and the addresses of member-only pages are not sent to it.

Providers and disclosure

Authentication, hosting, database, media storage, and configured email providers process information needed to deliver the service. Information may also be disclosed when required by law or to address abuse, fraud, or threats. Public information and information shared with other members are available to those audiences.

Reports and retention

Reports contain your concern and a snapshot of the reported content. The site operator reviews them manually. Reports are kept while under review and for 90 days after closure, then removed by scheduled maintenance. Workflow error categories are kept for 90 days, and anonymous sign-in starts are kept for 30 days. Account-linked milestone and error records are included in account export and removed with the account. Review records may remain after the reporter or author deletes an account. Operational backups may retain older records until replaced; restoring a backup can require reapplying later account removals.

Download, change, or delete your data

Edit profile information and privacy choices in your profile. Use Account and data to export your records and media links or permanently delete your account. Deletion removes your profile, public authored content, linked sign-in accounts, and notifications. Delivered messages remain in recipients' conversations as Former member. Job status history may remain without your profile, and report records follow the retention described above. Referenced media is removed during deletion; incomplete uploads and leftover copies are handled by scheduled orphan cleanup after its 24-hour grace period. External copies are outside our control. Contact us if you cannot access your account or need assistance with a privacy request.