Privacy Policy

This policy distinguishes uploaded files, stored reports, payment records and recovery backups. Seven-day download access is not a promise that every infrastructure copy is erased at exactly seven days.

Who to contact

Mabeya Utilities operates this tool. Contact support@cutoverauditor.com. We aim to reply within 3 business days (Monday–Friday, excluding Kenyan public holidays). This is a response target, not a resolution guarantee.

Uploaded files

We process the CSV exports you supply to generate your audit. Raw uploads are handled in a temporary workspace and removed before the result is created. They are not included in the report store or application-created backups. Reports can contain the URLs and findings derived from your uploads.

Results and access

Reports, findings, exceptions CSV and ZIP are stored in a private database. Download access ends 7 days after completion; expired results are removed from the active store by cleanup, on access or on service startup. Cleanup failures require operator attention. Database-backed results survive normal process restarts; they are not held only in memory.

Purchase records and recovery

We retain minimal purchase, checkout and order identifiers, payment state, expiry times and event receipts to deliver the purchase, prevent duplicate use and handle refunds, disputes and support. These records are separate from report expiry and are not automatically deleted after seven days. Recovery codes and browser tokens are stored only as hashes. Application-created ledger backups exclude results and recovery codes.

Hosting and backup copies

Hosting recovery snapshots can retain database copies beyond active-store deletion; their retention follows the hosting provider’s backup lifecycle. Application expiry does not guarantee immediate forensic erasure from infrastructure. We restrict use of recovery copies to incident handling and do not use them to reopen expired reports. Render’s snapshot documentation describes its backup lifecycle.

Cookies, logs and providers

An essential secure browser cookie keeps purchase access; a saved recovery code lets you replace that session. Cookie lifetime does not extend purchase or report deadlines. The application does not use advertising trackers. Application logs exclude raw uploads, recovery codes, query values and private result identifiers; hosting and payment providers may keep their own operational records. Creem handles payment details under its privacy policy. We do not store full card details.

Support and your requests

Messages you send remain in the support mailbox for handling your request and associated follow-up. Send only the necessary order reference and issue description; do not email private crawl files or recovery codes. Contact us about access, correction or deletion requests. We may need to retain limited records for delivery history, disputes or applicable obligations, and will explain relevant limits. Provider-held payment information may require a request to Creem.