Opashka Privacy Policy

1. Who provides Opashka

Opashka is provided by Saifullah Ahad ("we", "us", or "our"). This policy explains how the Android app and its queue-estimate service handle information.

2. What the app does

Opashka provides crowd-estimated wait ranges for physical queues. People can open a short queue code, discover broad nearby signals, and submit structured joined, served, or left-line events. The app has no account, public profile, comments, ratings, photos, or place and staff names.

3. Information handled by the queue service

• Approximate area: when you choose nearby discovery, create a signal, join, or mark served, the app requests Android approximate location. On the device it converts the result to a broad area cell of roughly two kilometres. The service receives that cell, a broad accuracy band, and the age of the fix. It does not receive or store the latitude and longitude returned by Android.
• Queue marker data: category, short code, broad area cell, intended closing time, time-zone offset, status, and timestamps.
• Queue event data: joined time, served or left-line outcome, elapsed wait, request identifier, and timestamps. These are structured signals; there is no free-text queue content.
• Installation pseudonym: the app creates a P-256 key pair in Android Keystore. Signed write requests include the public key and signature. The service derives a secret-scoped pseudonymous hash to limit replay and repeated influence. The private key never leaves Android Keystore.
• Technical network data: Cloudflare necessarily processes network information such as an IP address to route and protect HTTPS requests. Opashka's application database does not write IP addresses, advertising identifiers, contacts, or precise location.

Location is foreground and action-based. Opashka does not request precise location, background location, continuous tracking, or location history.

4. Optional feedback

About Developer can open a draft in your chosen email app. The draft includes the Opashka version, Android version, manufacturer, and device model so the developer can investigate a problem. You can edit or remove that information, and nothing is sent until you choose to send the email. No queue code, queue event, or location is attached. Opashka does not submit the message through an embedded form or relay.

5. Information stored on the device

Opashka stores saved queue estimates, the current open-session state, pending retry actions, and the Android Keystore signing key on your device. This supports clearly labelled saved estimates and bounded delivery retries when connectivity is interrupted. Android backup is disabled for the app.

6. How information is used

• To create and find broad-area queue signals.
• To calculate a wait interval, closing chance, confidence explanation, and potentially lighter hour.
• To detect replay, limit one installation's influence, and protect service availability.
• To prefill useful app and device context in an optional email draft that you control.

We do not use the information for advertising, profiling, credit, employment, insurance, or sale of personal information.

7. Service providers and sharing

We do not sell personal information. Information is disclosed only to processors needed to operate the selected feature:

• Cloudflare: hosts the queue API and database and processes HTTPS traffic and service-security metadata.
• Your chosen email app and provider: process an optional feedback email only if you choose to send the draft outside Opashka.

Public queue reads return combined estimates and marker details, including the short code, category, closing time, and broad area cell. They do not return individual events, installation pseudonyms, public keys, signatures, feedback, or precise coordinates.

8. Retention

• Raw queue sessions are retained for up to 30 days.
• Signed-request replay records are retained for up to 7 days.
• A queue marker is deleted after up to 90 days without activity.
• Short-lived rate-limit counters expire automatically.
• Local app data remains until you clear it in the Privacy screen, clear Android app storage, or uninstall the app.
• An optional email you send is retained only as needed to read and respond to it, subject to your email provider's and the developer mailbox provider's terms and deletion procedures.

9. Your choices and deletion controls

• Location permission: deny or revoke approximate location in Android Settings. Code-based forecast reading remains available.
• Delete reports and local data: open Opashka > Privacy > Delete my reports and local data. A signed request removes raw queue sessions associated with this installation and clears the local database and pending outbox.
• Clear or uninstall: Android Settings can clear all local app data; uninstalling removes local app data and the Keystore key.
• Privacy request: email www.saifullah.ai@gmail.com. Because there is no account and the server uses a one-way scoped pseudonym, we may need you to use the in-app signed deletion control to identify your reports.

10. Security

Queue traffic uses HTTPS. Write requests are signed, request identifiers are replay-checked, rate limits are bounded, exact coordinates are discarded before transmission, and private signing keys stay in Android Keystore. Optional feedback leaves through the security controls of your chosen email app and provider. No method of storage or transmission can be guaranteed completely secure.

11. International processing

Cloudflare and, if you send optional feedback, your chosen email provider may process information in countries other than yours. Where required, their contractual and technical safeguards apply to that processing.

12. Children's privacy

Opashka is a general utility and is not directed to children under 13. It does not provide accounts, profiles, messaging, or public user content. We do not knowingly collect personal information from children. Contact us if you believe a child sent personal information in an optional feedback email.

13. Accuracy and affiliation

Opashka provides a crowd estimate, not an appointment, ticket, exact place in line, or service promise. It is not affiliated with or endorsed by the offices, clinics, aid providers, repair services, or travel operators whose visitors may use a queue signal.

14. Changes to this policy

We may update this policy when the app, providers, or legal requirements change. The current version and effective date will remain available at https://privacy.saifullah.ai/opashka.html.

15. Contact

For questions, deletion help, or privacy requests, email www.saifullah.ai@gmail.com.