Security engineering

Security architecture
and verification.

How mittiPaw controls access to pet records, handles uploaded documents and evaluates release risk.

Evidence review: 18 October 2026 · Scope: retained V1 release records

Scope and assurance

This page distinguishes documented implementation from recorded release checks. The available V1 configuration review is dated 7 July 2026; it is not a live assessment of every deployed service. No independent security audit, certification or compliance attestation is claimed.

01 / Identity and authorization

Account identity and pet-level permissions

The V1 release review records authenticated access, pet ownership checks and Supabase Row Level Security (RLS). Authentication identifies an account; authorization determines whether that account may access a particular pet or resource.

Database access
RLS policies scope access to authorized rows. Selecting an active pet in the app is interface context, not an authorization grant.
Uploaded documents
The recorded storage configuration uses private buckets for pet photos, health documents and prescriptions. Storage object access is a separate control from database row access.
Privileged operations
Server credentials carry elevated authority. Account and resource authorization must be checked before privileged operations; a valid session alone is insufficient.

Evidence: V1 Security Release Summary and its referenced account-deletion/RLS review. Production policy state was not re-tested during this website review.

02 / Data lifecycle

Transport, storage and deletion

The retained V1 review records HTTPS/TLS for app traffic. This protects data in transit; it is not a claim of end-to-end encryption. Android manifest-level hardening remains subject to binary re-verification.

The account-deletion implementation is recorded as removing storage objects before application rows and the authentication account. A storage-cleanup failure aborts deletion rather than silently leaving the operation marked complete.

Backup retention windows and deletion of user-linked diagnostic logs remain verification items in the release record. No fixed retention or immediate deletion guarantee is asserted here.

Account deletion process ↗

Processing and telemetry

The dependency review recorded no third-party advertising, analytics or tracking SDKs, and no client crash-reporting SDK in the inspected dependencies. That result does not establish the absence of operating-system or hosting-platform telemetry; those settings require separate confirmation.

Document and AI processing can cross service-provider boundaries. See the Privacy Policy for data use and provider disclosures. Active processor settings must be checked against the deployed configuration before the next publication approval.

03 / Release assurance

What the evidence establishes

These are recorded V1 results, not tests newly executed as part of this website refinement.

Recorded

Android build provenance

The signed release candidate at source commit a8c0a95 was recorded as matching the downloaded EAS artifact byte-for-byte. Artifact identity does not establish security correctness.

Partial

Regression verification

The retained regression summary closes three named gates. It also lists remaining agreed gates and a final manual round as open. This is not evidence of complete regression coverage.

Not established

Static security analysis

A retained MobSF report for the signed release candidate is unavailable in the reviewed evidence. Clean-scan, zero-vulnerability and tracker-scan results are therefore not asserted.

Re-verification required

Android hardening

Backup and debug flags, cleartext restrictions and permission exclusions were not re-parsed from the binary in the retained audit. These controls must be confirmed against the release artifact.

Outstanding verification

  • Retain a static-analysis report tied to the exact release artifact and document finding dispositions.
  • Re-verify binary manifest hardening and production telemetry settings.
  • Confirm active document/AI processors, backup retention and log deletability.
  • Complete and retain the remaining regression and manual test evidence.

Source records reviewed: V1 Security Release Summary, Android Binary Audit, MobSF Summary, Security Open Items and Regression Summary. Internal evidence is summarized here; raw operational artifacts may contain confidential information.

04 / Vulnerability disclosure

Report a security issue

Email support@mittipaw.com with the affected app version, platform, reproduction steps and a description of the impact. Use an account you control and redact personal records, session tokens and credentials from supporting material.

Responsible disclosure policy ↗

Security controls reduce risk; they cannot guarantee that an application is free of vulnerabilities.