Privacy Policy - Atrekes

1) Who we are

Atrekes is provided by Saifullah Ahad (“we”, “us”, “our”). Contact us at [email protected] or visit saifullah.ai.

2) What Atrekes does

Atrekes guides a person through a used-phone audit. It writes and verifies bounded app-private test data, samples battery and sensor signals, reads ordinary Android hardware and software properties, records a panel/touch check, compares evidence with a versioned model reference, and creates a locally signed measurement report. It is not device certification or purchase advice.

3) Data kept only on your phone

Atrekes stores audit reports, cryptographic signing keys, model-reference cache data, contribution retry state, and received-report replay records in private app storage. Reports can include device model/build fields, measurements, evidence classifications, a typed eight-digit TAC prefix when used, and the report’s signing metadata. Full typed IMEI values are cleared and are never stored.

Temporary storage-test blocks are position-seeded app data. They are removed after a completed, cancelled, failed, or low-battery run. If you deliberately pause, completed blocks and resume metadata remain only so that run can continue.

4) Optional numeric contribution

The “Contribute numeric measurements” switch is optional and is chosen before each audit. When enabled and a matching reference model exists, Atrekes sends one bounded sample to Firebase Firestore. It contains:

• model key and a SHA-256 hash of the Android build fingerprint;
• verified storage bytes, battery estimate/error, CPU score, RAM, display dimensions, and sensor counts;
• conflict score, non-text tamper flag codes, schema/report versions, a random report-derived hash, and server creation time.

It does not send an account, advertising ID, full IMEI, TAC, name, email, seller/shop identity, contact, location, photo, QR report, or user-written text. Samples are create-only and immutable. They are used to calculate same-model measurement distributions and improve future evidence comparisons.

Firebase and its network infrastructure may process technical request metadata, such as IP address and app/device connection information, to deliver and protect the service. Atrekes contains no Firebase Analytics, advertising, or crash-reporting SDK.

5) Backend protection and integrity processing

When Atrekes contacts Firebase, Firebase App Check uses Google Play Integrity to help protect the reference and measurement services from automated abuse. Google processes app-provided request data, app metadata such as package name, version, and signing certificate, device and app integrity attestation data, Play license status, and technical request metadata. This processing occurs automatically for backend security, is encrypted in transit, is not used by Atrekes for advertising, and is subject to Google’s fixed retention practices and applicable terms.

6) Reference downloads and offline use

Atrekes downloads public versioned model references and a bounded set of anonymous numeric samples. The most recent reference is cached locally with its version and fetch time. If the network or model reference is unavailable, the app says so and uses only local self-consistency evidence.

7) Camera, vibration, and network permissions

• CAMERA is requested only when you choose to scan a signed-verdict QR. Frames are analyzed in memory and are not saved or uploaded.
• VIBRATE supports the guided sensor test.
• INTERNET and ACCESS_NETWORK_STATE fetch/cache the reference corpus, send an optional numeric contribution, and support App Check integrity processing.

8) Nearby signed handoff

A sender can display a structured report as rotating QR frames. A nearby phone verifies the included ECDSA signature before showing values and records the report nonce to reject replay. This handoff is direct between the two phones and needs no server. Copy/paste is offered as an accessibility fallback.

9) Retention and deletion

Delete a local report in Report Archive. Clearing Atrekes storage or uninstalling removes all local reports, cache, signing keys, replay records, and paused test data. Optional cloud samples have no account or direct personal identifier and cannot reliably be linked back to a person; they are retained while the measurement corpus operates and may be deleted during corpus maintenance or service retirement. You can prevent future samples by leaving the contribution switch off.

10) Security and limits

Report signing keys are generated in Android Keystore. Cloud rules allow public reads only for curated references and bounded sample queries; samples must match an exact numeric schema and can be created once but never updated or deleted by an app client. No system is risk-free, and a modified operating system can still interfere with ordinary-app observations; Atrekes reports this limitation instead of claiming certification.

11) Children’s privacy

Atrekes is a general utility, is not directed to children under 13, and has no account, profile, public posting, chat, seller listing, or other user-generated-content service. We do not knowingly collect personal information from children.

12) Service providers and international processing

Google Firebase provides the reference and numeric corpus service, and Firebase App Check with Google Play Integrity protects those requests. Their processing may occur in countries other than yours under Google’s applicable terms and safeguards. The signed nearby-phone handoff is not routed through Firebase.

13) Changes and contact

Updates will be posted at privacy.saifullah.ai/atrekes.html with a revised effective date. For privacy questions or requests, email [email protected].

Developer: Saifullah Ahad
Location: Dhaka, Bangladesh
Website: https://saifullah.ai