Cirava

Privacy policy

Last updated 2 November 2026

Who we are

Cirava is an app and service run by Muhammad Arham Waseem. Questions, requests and complaints about privacy: arham.waseemch@gmail.com.

What Cirava is for

Letting people in a small circle, usually a family, see where each other are when they choose to share, check on each other, plan together, message and call. We do not sell data, we show no ads, and the app contains no analytics or advertising code.

What we collect, and why

What we do not collect

The audio or video of calls (they are encrypted between the two phones; when a direct connection is not possible our relay passes on the encrypted media without being able to read it), your phone's contact book, advertising identifiers, or your location when you are not sharing it.

Who else receives data

Not in use today: an AI assistant provider and a text-message (SMS) provider. If we turn either on, we will update this policy first and say exactly what they receive. We disclose data to authorities only when the law requires it.

How long we keep it

DataKept
Location trail1 day (your latest point until you stop sharing)
Trips60 minutes after they end
Safety check-ins and alerts72 hours after they end
Calls, automation runs30 days
Drive summaries90 days
Sign-in codes10 minutes, as a hash
Messages, plans, circles, contacts, your accountUntil you delete them or your account

Your choices and rights

In the app, under You → Privacy & data, you can see what we keep, download all of it as one file, and delete your location trail. Under your account you can delete your account; see how account deletion works. You can also write to us to access, correct or delete your data, and you may complain to your data protection authority.

Children

Cirava is not meant for children under 13 (under 16 in the European Economic Area and the United Kingdom). If we learn that such a child has an account, we delete it.

Security

Everything between the app and our server is encrypted (HTTPS). Data on your phone is encrypted with a key held by its secure hardware and is removed when you sign out. Sign-in codes and session tokens are stored only as hashes.

Changes

We change this policy only by publishing a new version here, with a new date, before the change applies.