Safety Relay records
A Safety Relay is a worker-submitted safety report together with its review and closeout history. It is saved for the customer organization that owns the route.
Privacy notice
How Good Catch Relay handles information
This notice explains what we collect, why we collect it, who can see it, and how to contact us about privacy requests for the Good Catch Relay website, QR reporting forms, customer dashboards, owner tools, billing, onboarding, email notifications, and support.
Admin accounts
Customer admins sign in with Supabase Auth and access only organizations where they have membership.
Payments
Stripe handles subscription checkout, payment details, invoices, and billing portal sessions.
No ad sale
We do not sell personal information or share it for cross-context behavioral advertising.
Scope and roles
Good Catch Relay provides QR-based safety reporting for customer organizations. Workers can submit reports through a public route such as /r/[slug] without creating an account. Each saved submission becomes a Safety Relay: the worker report plus its review and closeout history. Customer admins sign in to review Relays, configure settings, manage billing, export records, and run follow-up workflows. Platform owners use separate owner routes to onboard customers and support the service.
For worker report content, the customer organization that owns the QR route determines who receives and reviews the report. Good Catch Relay processes that information to provide the service, secure the route, store evidence, send notifications, and make the report available to authorized customer admins.
Information we collect
| Category | Examples |
|---|---|
| Safety Relay and worker report information | Worker-submitted report type, description, crew or project, location note, corrected-already flag, optional submitter name, anonymous preference, timestamps, route, reporting unit, workflow status, and closeout history. |
| Photos and files | Optional report photos, normalized photo metadata, company logos, generated QR assets, evidence exports, and report packets when those features are used. |
| Admin account information | Name, email address, authentication identifiers, organization membership, assigned role, division access, notification preferences, and product activity needed to operate the account. |
| Billing information | Plan tier, billing interval, subscription status, Stripe customer and subscription identifiers, invoice and portal references, and billing contact context. Full card details are processed by Stripe. |
| Demo and onboarding information | Company name, contact name, work email, team size, reporting goal, owner notes, invite status, and onboarding activity. |
| Technical and security information | IP-derived request context, browser and device signals, route session tokens, route unlock cookies, device identifiers for abuse prevention, Turnstile verification results, logs, error events, and usage counters. |
| Communications | Emails we send or receive, notification delivery metadata, support requests, privacy requests, and related follow-up notes. |
How we use information
- Provide the public QR report form, save reports, process optional photos, and route notifications to configured recipients.
- Authenticate customer admins, enforce organization membership, roles, division access, plan limits, and owner authorization.
- Operate dashboards, settings, QR pages, analytics, exports, billing, onboarding, support, and owner-only customer provisioning.
- Send transactional email such as report notifications, demo follow-up, account invites, reminders, weekly summaries, and billing-related messages.
- Protect the service by detecting spam, duplicate submissions, invalid route sessions, suspicious report volume, and unauthorized access attempts.
- Maintain product reliability, debug errors, measure usage, improve workflows, and comply with legal, tax, accounting, security, and contractual obligations.
Worker reports, photos, and anonymity
Workers can choose whether to provide a name and may mark a report anonymous. If a report is submitted anonymously, Good Catch Relay does not attach the entered name to the saved report. Technical information may still be processed for security, spam prevention, troubleshooting, legal compliance, and service reliability.
Report descriptions and photos may contain personal information or safety-sensitive details. Customer admins and configured recipients may view, assign, close, export, and share reports according to their organization policies. Do not include unnecessary personal, medical, financial, or unrelated sensitive information in a report.
Retention
We keep information for as long as needed to provide the service, maintain safety records, support customer accounts, meet legal and accounting obligations, resolve disputes, enforce agreements, and protect the service. Retention periods can vary by customer configuration, report history, billing requirements, backup cycles, and legal obligations.
If a customer asks us to delete or export organization data, we evaluate the request against account status, safety record needs, legal obligations, billing records, security logs, and the rights of people named in the data.
Security
We use administrative, technical, and organizational safeguards designed to protect information. The app uses authenticated admin routes, server-side validation, row-level security, trusted service-role operations only in server code, secure public route checks, Turnstile verification where configured, and private storage for report photos and company logos.
No internet service can guarantee perfect security. If you believe information in Good Catch Relay has been accessed or disclosed without authorization, contact us promptly at relay@goodcatchrelay.com.
Your privacy choices and rights
Depending on where you live and how you interact with Good Catch Relay, you may have privacy rights. Customer admins should use their account settings where available. Workers and other people can contact us or the customer organization that owns the relevant QR route.
- Ask for access to personal information associated with you.
- Ask us to correct information that is inaccurate or incomplete.
- Ask us to delete information, subject to customer instructions, safety records, legal obligations, security needs, and backups.
- Ask us to export or provide a copy of information where required by applicable law.
- Object to or restrict certain processing where applicable.
- Appeal or complain through the channels available under applicable privacy law.
We may need to verify your identity and understand which customer organization, QR route, report, email address, or account your request concerns. We will not discriminate against you for exercising privacy rights available under applicable law.
Children
Good Catch Relay is a business safety reporting service and is not directed to children under 13. If you believe a child provided personal information through Good Catch Relay, contact us so we can review the request.
International access
Good Catch Relay is operated from the United States. If you access the service from another country, information may be processed in the United States and other locations where our providers operate.
Changes to this notice
We may update this notice as Good Catch Relay changes, providers change, or legal requirements evolve. The updated version will be posted on this page with a revised last updated date.
Contact
For privacy, security, or data rights requests, email relay@goodcatchrelay.com. Include the organization name, your email address, the QR route or report context if relevant, and the specific request. Avoid sending sensitive report photos by email unless we ask for them.