Qivra Privacy Policy

1. Who provides Qivra

Qivra is provided by Saifullah Ahad. Contact: www.saifullah.ai@gmail.com. Portfolio: https://saifullah.ai.

2. What the app does

Qivra is an offline-first documentation and measurement aid for a fresh-concrete slump test. It guides a visible before-and-post-lift capture, lets the user confirm landmarks, records a bounded measurement range or an intentional refusal, provides a physical-ruler fallback, and creates local export files.

3. Data collection and sharing

We do not collect, receive, sell, rent, or share personal data through Qivra. The app has no account system, developer server, analytics SDK, advertising SDK, crash-reporting SDK, cloud AI, or third-party tracker. It does not request Android's internet, location, contacts, microphone, advertising-ID, or billing permission.

4. Camera and motion sensors

The optional CAMERA permission is used only while the foreground setup chamber is visible. Qivra deliberately captures two still evidence frames and no audio. Gyroscope and accelerometer readings are processed locally to describe whether the phone moved during capture. Manual ruler entry remains available if camera access is denied or unavailable.

5. Information stored locally

• Optional batch aliases, procedure labels, and profile dimensions entered by the user.
• Measurement ranges or refusal reasons, confirmed landmarks, motion summaries, frame-analysis evidence, hashes, and app-held event signatures.
• Two Qivra-managed camera frames when the camera workflow is used.
• An optional ruler photo selected through Android's system photo picker.

Record payloads are encrypted with AES-GCM using key material held by Android Keystore. Event signatures use an app-held device key. These controls help protect local records and detect changes; they do not prove that a physical scene happened as described.

6. Retention

Saved record payloads remain on the device until the user deletes an individual sheet, deletes all local Qivra data, clears app storage, or uninstalls the app. Qivra-managed camera frames become eligible for local cleanup after 24 hours. Optional ruler photos become eligible after 180 days. Android schedules cleanup work and may run it later when device conditions permit.

7. Exports

Qivra can create PDF, JSON, CSV, and .qivra files. An export is written only after the user chooses a destination through Android's system document picker. An exported file is a separate copy outside Qivra. Qivra cannot delete it from another app, device, backup, or recipient.

8. Your controls

• Deny or revoke camera permission in Android Settings.
• Use the complete physical-ruler workflow without camera permission.
• Delete one local sheet from its detail screen.
• Delete all local records and Qivra-managed media from Privacy and limitations.
• Clear app storage or uninstall Qivra through Android Settings.

9. Security and device backup

Qivra excludes its private app storage from Android cloud backup and device transfer because its encryption keys are device-bound. No security measure can eliminate every risk, especially on a compromised or unlocked device. Keep exported files only in destinations you trust.

10. Measurement boundary

11. Children's privacy

Qivra is a general construction utility and is not directed to children under 13. Because the developer does not receive app data, Qivra does not knowingly collect personal information from children.

12. International transfers

Qivra does not send app data to the developer or a developer-controlled service, so the app performs no developer-controlled international data transfer.

13. Policy changes

If this policy changes, the revised version and effective date will be published at https://privacy.saifullah.ai/qivra.html.

14. Contact

Privacy questions may be sent to Saifullah Ahad at www.saifullah.ai@gmail.com.