Updated
Privacy policy
How Avizo handles information when you use the app, its API and this website. No Avizo account is required.
Developer: xandrco
Information we process
The server stores an anonymous installation identifier, platform, language, notification preferences and a hash of the access token. Saved places contain your label, selected type and color, locality, street, house, block, selected services and any coordinates you provide. Reports of service problems and reminders are linked to the installation.
If you enable push, the server stores an Expo push token and delivery records. Technical server logs can include IP address, request time, requested URL and errors. Official announcements, source links, research evidence and their translations are stored separately from your saved places.
Purpose and local storage
We use this information to match official notices to saved places, show selected services and, when available and enabled, send updates and reminders. Device storage also holds preferences, saved-place information and cached notices for offline use and widgets.
The current version has no advertising analytics. The website loads no external analytics scripts. Removing an app or its local cache does not automatically delete the corresponding server installation.
Push and external services
When push delivery is enabled, Expo Push Service and Apple or Google process the push token and notification payload. A payload may contain your saved-place label, the service and time, and identifiers used to open the relevant notice. Notifications may appear on the lock screen according to your device settings.
Native builds that include Firebase Crashlytics send Google crash diagnostics: installation and session identifiers, device and app versions, stack traces and exception messages. Avizo does not add saved places, access or push tokens, or custom user identifiers to these reports. Advertising analytics is not enabled.
DOT processes public provider announcements and address research to prepare translations and matching evidence. Saved-place labels and private installation tokens are not supplied to DOT for that research. Opening an official source or emailing support uses the destination service and its privacy terms.
Retention and deletion
Saved places and installation settings remain on the server until deleted. Deleting a saved place removes its subscriptions and reminders. The authenticated installation deletion operation removes its saved places, subscriptions, reminders, push tokens and identifiable delivery records and invalidates its access token. Public directory entries and official announcements are not personal saved places and are retained separately.
Technical logs and previously created backup copies are separate from the active installation records and are not erased by that API operation. For an erasure request covering these copies, or if you can no longer access the installation, contact support. Do not send a secret access token. Reinstalling creates a new installation and does not prove ownership of an older one.
Outage details are cleaned up 30 days after completion according to the published schedule or recorded closure. Finished import diagnostics and provider documents without retained references are eligible for cleanup after 7 days. Evidence linked to retained announcements, revisions or address reviews stays available. Aggregate counters and import identities can remain to prevent duplicate imports.
Your choices and support
You can change saved places, selected services, language and notification preferences. System notification permissions are controlled on the device. To delete data for this installation, open Settings → Privacy policy → Delete my data and confirm the action. Deletion cannot be undone.
For privacy questions, correction or deletion requests, use the contact above. Share only information needed to identify the request. The date above identifies this published policy version.