Data Security at FieldSafetyTalk

FieldSafetyTalk (a product of PreTaskPlanner LLC) is built to hold records that matter. When a crew signs off on a safety talk, that record may later be reviewed by a safety manager, an insurer, or a regulator — sometimes years after the meeting. We design the Service with that responsibility in mind.

Your data is yours. The talks you run, the crews you build, and the records you generate belong to your account. We do not sell your jobsite data, and we do not use it to train AI models.

Isolation by default. Every record in the Service is scoped to the account that created it, and that separation is enforced at the database level rather than only in application code. Your crews, meetings, signatures, and downloads are visible only to you.

Encryption in transit and at rest. Data is encrypted in transit and at rest, hosted on managed cloud infrastructure built on AWS.

Gated documents. Print-ready PDFs are stored in private storage that is not publicly reachable. Files are served only through short-lived, single-use links generated after your permission to access them is verified — there are no public document URLs to guess or share.

Workers don’t need accounts. Crew members sign off through a temporary, unguessable link that expires when the meeting closes. They never create credentials, and the sign-in page cannot be used to browse other meetings or view anyone else’s signatures.

Tamper-evident records. Each completed meeting produces an audit record with a cryptographic hash computed over the meeting’s data and every signature. The record is frozen at completion and never regenerated, so any later alteration is detectable — including across translated versions, which carry the same document ID and hash.

Honest about what a record proves. Our audit records capture timestamps, device and network signals, and comprehension responses as evidence of attendance. We present these as evidentiary, not as verification of a signer’s identity — a distinction we state plainly on every record.

Your role and ours. You decide what worker information enters the Service; we process it on your behalf. We use a small number of established sub-processors for hosting, storage, and payments, and we work only with providers that meet recognized security standards.

Questions about data handling, retention, or deletion? Contact us at info@fieldsafetytalk.com

Infrastructure

FieldSafetyTalk is built on established cloud infrastructure providers:

• Supabase provides our authentication and database services.
• Vercel provides our application hosting.

These providers maintain their own robust security programs and industry-standard practices for the infrastructure they operate. https://supabase.com/features/soc-2-compliance https://security.vercel.com/

Encryption

• In transit: Data transmitted between your browser and the Service is protected using encryption (HTTPS/TLS).
• At rest: Data stored in our database infrastructure is encrypted at rest by our infrastructure provider.

Access controls

• Access to accounts is protected by authentication, and sensitive operations require appropriate authorization.
• We limit internal access to production data to what is necessary to operate and support the Service.

Record integrity

Audit records generated by the Service are designed to be tamper-evident using cryptographic hashing (SHA-256), so that changes to a completed record can be detected. This is intended to support the integrity of your safety-meeting records.

Worker sign-off data

Worker sign-off information (such as names, signatures, timestamps, and comprehension results) is stored as part of the records that Account Holders create. This information is handled in accordance with our Privacy Policy, and Account Holders are responsible for the lawful collection and use of the worker information they enter.

Payments

Payments are handled by Stripe, our third-party payment processor. We do not store full payment card details on our servers.

Your role in security

Security is a shared responsibility. We encourage you to:

• use a strong, unique password and keep your credentials confidential;
• limit account access to authorized personnel; and
• notify us promptly if you suspect any unauthorized access.

Reporting a security concern

If you believe you’ve found a security vulnerability or have a security concern, please contact us at security@fieldsafetytalk.com. We appreciate responsible disclosure.

FieldSafetyTalk is a product of PreTaskPlanner LLC. These pages were last updated 07.16.2026