Security

• Retention. A document you upload to a free checker, and its result, are deleted automatically after 120 days. Bid documents and your company library stay until you delete them.
• Training. Your bid documents and your company library are never used to train models. Uploads to the free checkers fall under the privacy policy of 14 August 2026, which allows them to improve those checks; text you rate is kept for 120 days for the same purpose.
• Isolation. Every bid belongs to one organisation. Storage is addressed by exact key, so nothing can be listed or guessed, and every read checks your membership.
• Deletion. You can delete a document from your company library in the workspace. To delete a bid and the documents in it, ask us and we do it.
• Hosting. Sydney region, non-root containers, a separate identity per service. The website holds no secrets and reaches no private resources.
• Human review. Stipple prepares a draft. You approve it. Stipple never sends anything to a buyer.

• The analysis tools (fact-check, AI-text detection) never store the submitted document — only the verification result persists, keyed by a content hash.
• Forensic inspections store the document and its result for the retention window, then delete automatically. No document content or extracted personal data enters our searchable index.
• All traffic is HTTPS; data is encrypted at rest.

When you (or an agent) submit a link, the fetch runs behind a strict server-side guard: public http(s) hosts only, every redirect hop re-validated, DNS resolution pinned at connect time, and bodies size-capped while streaming. Internal addresses, cloud metadata endpoints, and private ranges are unreachable by construction.

• No tracking identity beyond your account email: your IP is stored only as a one-way salted hash, and production refuses to start if the salt is missing.
• Rate limiting and abuse controls run on those hashes, never raw addresses.

Details in the privacy policy.

• Hosted in Australia (Sydney region) in least-privilege, non-root containers with isolated identities per service.
• The website holds no secrets and reaches no private resources; only the API service carries credentials.
• Identifiers are strictly validated and storage access is exact-key — no enumeration, no traversal.
• Honest failure: missing dependencies degrade with a labeled note in the result, never silently.

Found something? Report it through our contact page with steps to reproduce. We read every report and fix verified issues fast — recent reporter-credited fixes ship within days and appear in the changelog.