Updated 2026-08-21.
What Tekmerion collects for the V1 pilot, who can see it, where it is stored, when it is deleted — and the exact wording of what we cannot delete.
When you pay for a V1 pilot, Stripe processes your payment and returns a transaction id (kept by Polsia for accounting). After payment you fill in a 14-question scope questionnaire and submit up to 3 redacted documents.
We store: your questionnaire answers (free text and multiple choice); the file names, byte sizes, MIME types, and the raw bytes of the documents you upload; the manual-review notes written by the Tekmerion analyst; and the final PDF report generated at the end of the engagement. We do NOT store your credit-card primary account number; Stripe processes the payment and Tekmerion never sees or stores it.
Everything is stored in a single PostgreSQL database row tied to your account (a PilotEngagement row, with evidence and the final report as attached rows). The data is hosted on the Polsia platform; encryption at rest is provided by the platform database; encryption in transit is HTTPS only.
Access is limited to the Tekmerion analyst assigned to your pilot (manual review), a small Tekmerion internal operations role (administrative tasks only), and you (the customer) through /dashboard/pilot and /dashboard/pilot/report. No third party has access. No data is ever sold, resold or shared for marketing.
The V1 pilot is built around an explicit, automatic 30 calendar day retention window. The clock starts on the day the final PDF report is delivered to you (finalDeliveredAt). On day 30, a scheduled job runs nightly, marks your engagement status as "deleted", removes your questionnaire answers, the uploaded evidence files, the manual-review notes, and the PDF, and writes a PilotDeletionRecord — a small audit-trail row containing only: your user id, the engagement id, the finalDeliveredAt timestamp, the deletedAt timestamp, and the ids of the deleted evidence rows. The deletion record contains no questionnaire, document or report content.
Tekmerion controls the application data above and deletes it on the schedule we promise. We do NOT have visibility into, or the ability to delete, infrastructure-level backups of the platform database that the hosting provider may keep for their own disaster-recovery purposes. Those backups may persist beyond the 30-day deletion window.
If your threat model requires strict, verifiable deletion of all material within a fixed window (e.g. a regulatory erasure request), please contact tekmerion@polsia.app before paying so we can discuss the exact retention posture, the provider backup cadence (which we cannot unilaterally shorten), and any contractual commitments the platform provider offers you directly.
We require you to redact your documents before upload. To make compliance easier, the upload endpoint runs an automated denylist against common secret patterns: credit-card shaped numbers (13–19 contiguous digits); API key prefixes (AWS, Stripe, GitHub, OpenAI, Google); long hexadecimal strings (≥ 32 chars, sometimes used as tokens or keys); US SSN shapes (3-2-4 digits); IBAN shapes. Uploads matching any pattern are rejected with a 400 response and a clear field-level error.
Even with the denylist, the denylist is a guardrail, not a guarantee. You remain responsible for redacting your documents before upload.
Within the 30-day retention window you may download everything we hold about your pilot from /dashboard/pilot and /dashboard/pilot/report at any time. You may request an earlier deletion before the 30-day mark by emailing tekmerion@polsia.app — we will delete on demand. (See the backup caveat above for the absolute scope of any deletion.)
For any privacy question under the V1 pilot, email tekmerion@polsia.app. We will respond within one business day.
This page is the V1-pilot specific overlay. It does NOT replace or amend Tekmerion's site-wide Confidentiality & Security wording on /trust.