Research is only as good as the data behind it — and the way that data is handled. This is where we document both: how respondent data quality is protected, and how your data moves through the platform.
A compact buyer review path for legal, security, research ops, and analytics stakeholders.
Procurement review
Each answer is evidence-reviewed and expires unless it is reviewed again. “Confirm for deployment” means the repository documents a control, but your target environment or contract still needs current operational evidence.
Plan contracts expose retention windows and organization settings support scoped retention rules. Confirm the policy, enforcement coverage, exceptions, and execution evidence for your workspace before relying on a retention commitment.
The production contract rejects local object storage and supports private Cloudflare R2 bindings with environment-specific buckets. Account, region, bucket, encryption, and lifecycle evidence remain deployment-specific and must be confirmed for the environment serving your workspace.
An authenticated account-deletion flow schedules deletion after a 30-day grace period. Procurement review should still confirm organization-wide scope, backups, object classes, legal-hold exceptions, and a deletion-verification receipt for the intended environment.
A complete environment-specific subprocessor register is not publicly verified in this build. Request the applicable vendor list, purpose, data categories, location, and contractual terms before purchase or sensitive-data use.
Internal incident evidence, redaction, review, and recovery runbooks exist. No public incident-response SLA, notification window, uptime commitment, or external security attestation is claimed here; request the current contractual posture during review.
CSV, Excel, and JSON export paths are available. PDF reporting is beta; statistical-package and presentation/share workflows retain their documented limits. Access, content scope, and deletion after export remain the customer's responsibility.
External model calls are gated by workspace settings and the public data-handling page documents provenance and human review. Exact provider, region, retention, training-use terms, and contract coverage are deployment-specific and must be confirmed before sensitive data is processed.
Staging and production declarations require separate secret-file and object-storage bindings, while local development can use local services. Configuration contracts do not prove a deployed environment; request current readiness, storage-probe, backup, and recovery evidence for the target environment.
Need deployment-specific evidence or contractual answers? Start a security review.
A status describes whether you can use a workflow and how access works. It is not a promise that a research method will produce a particular business outcome.
Start free to see the controls first-hand, or ask us anything about how your data is treated.
