Effective 2026-09-08

Privacy.

Responsible party

Pilebench is responsible for this product site at https://pilebench.pages.dev. Product privacy questions can be sent to socialreminderinfo@gmail.com. This page does not make Pilebench the controller of research files that a user creates and handles independently.

Researcher workspace data

IndexedDB can store study titles, instructions, participant-information wording, cards, researcher notes, categories, frozen editions, anonymous session codes, response groupings, timestamps, comments, inclusion reasons, manual label standards, thresholds, and candidate structures. That data remains in the current browser profile. The app reads a checkpoint or response file only when the user selects it.

Participant file data

A generated participant HTML file makes no network requests and uses no browser storage. It holds one frozen study edition in the file itself. A saved or completed response is created as a local JSON download. It is not submitted automatically. The participant and researcher control how that file is transferred.

Data intentionally not requested

Research workflows do not request direct identity, location, demographic, biometric, payment, employment, education or safeguarding records. Optional Premium checkout requests payment and receipt details through RevenueCat and Stripe. Free text and researcher-issued session codes can still contain or become personal data.

Hosting logs

A production host may process ordinary request data such as IP address, timestamp, requested path, user agent, and security events. The final hosting provider, log fields, retention, access, and incident process must be reviewed before launch and reflected here if applicable. The static application itself does not read those logs.

Storage, retention, and deletion

Users can explicitly delete projects or responses from the browser workspace. Browser settings can also clear IndexedDB. Downloaded checkpoints and response files are outside the app and must be managed by their holder. Researchers are responsible for an approved access, backup, retention, withdrawal, and deletion process for their study.

Security

Strict schemas, content fingerprints, response digests, output escaping, formula neutralization, a restrictive content security policy, declared billing dependencies separated from research data, and release checks reduce some risks. They do not replace endpoint security, device encryption, safe transfer, least-privilege access, backups, or organizational review.

Jurisdiction and rights

The approved legal jurisdiction for this release is Ontario, Canada. Applicable privacy rights and the correct controller contact depend on the final seller, host, user, and research context. Contact the responsible researcher for rights concerning a research response they control.