Rego Privacy Policy

Rego is built to be private by default. This page explains, in plain language, what data the Rego app and the regoapp.com website handle, and what never leaves your control.

Effective date: 29 August 2026. Rego and regoapp.com are operated by Peer Assembly Ltd ("we", "us").

The short version

• Your place library — places, notes, photos, tracks, collections — is stored on your devices and in your private iCloud account. We cannot read it. We have no server that holds it.
• There is no Rego account. We don't know who you are.
• We show no ads and we never sell data.
• Saving a place never publishes anything. Sharing and exporting happen only when you choose them.
• The app sends anonymous usage analytics and crash reports. Neither can ever include your places, notes, coordinates or search terms.

Your place library

Everything you save in Rego lives in the app's storage on your device. If you're signed into iCloud, your library also syncs through Apple's CloudKit to your private iCloud database so it appears on your other devices. That database belongs to your Apple account: Peer Assembly has no access to it, and Apple protects it per the Apple Privacy Policy.

Backups and exports you create are written to locations you pick, and sharing a place or collection sends data only to the people you share it with. Nothing you save in Rego is ever published as a side effect.

Location

Rego asks for location permission so it can save your current position as a place, sort your library by distance, and show your position on the map. Your location is used on the device for those features — it is not sent to us, and Rego does not track or record your movements.

Network services the app uses

Some features contact online services when you use them:

• Apple Maps — map tiles, place search, and address lookup (reverse geocoding) are provided by Apple's MapKit services.
• iCloud sync — as described above, via your own iCloud account.
• Link resolution — when you share a shortened map link into Rego, the app follows the link to read the location it points to. This lookup happens from your device, and only for links you explicitly share into Rego.
• Google Firebase — crash reporting, and the settings that let us change a feature's configuration without shipping an update. Described below.

Anonymous usage analytics

To understand which features are used and whether flows like import and migration succeed, the app sends anonymous usage signals to TelemetryDeck, a privacy-first analytics service with EU-hosted infrastructure. For these signals, identifiers are anonymized on the device before transmission, IP addresses are not stored, and timestamps are coarsened.

These signals describe that a feature was used, never what you saved: no place names, no coordinates, no notes, no photos, and no search terms are ever collected.

You can turn these signals off at any time in Settings → Share Anonymous Usage Data.

Crash reports and app configuration

The app uses Google Firebase for two things: crash reporting (Crashlytics) and remote configuration, which lets us adjust a setting or switch off a misbehaving feature without shipping an update.

A crash report describes the failure, not you: the stack trace, the device model, the iOS version, and how long the app had been running. It never contains your places, notes, photos, coordinates or search terms. Crash reports are sent even if you turn off usage analytics, because without them a crash that only happens on your device is one we cannot see or fix.

Firebase also records basic app-lifecycle events — first launch, a session starting, an app update. This is a separate, smaller system from the TelemetryDeck signals above, and the guarantees are different, so we would rather spell them out than let one paragraph cover both. Firebase assigns your installation a random identifier that is not linked to any account and tells us nothing about who you are, and Google derives an approximate country from your connection. We have configured it to collect no advertising identifier (IDFA), no vendor identifier (IDFV), and no ad personalization signals — Rego shows no ads, runs no ad campaigns, and does not track you across other apps or websites. These lifecycle events follow the same Settings → Share Anonymous Usage Data switch as the analytics above. Google processes this data as described in the Firebase privacy documentation.

Purchases

Purchases are processed by Apple through the App Store. We receive no payment details. See Apple's privacy policy for how Apple handles purchase data.

This website

regoapp.com is a static website. It sets no cookies and runs no third-party trackers. Our hosting provider may keep standard server logs (IP address, page requested, time) for security and operations.

Email

If you email us at rego@peerassembly.com or use Send Feedback in the app, we receive your email address and message (feedback emails attach the app version and device model to help with support). We use this only to respond, and we don't add you to any mailing list.

Data retention and your rights

Because your library lives with you — on your devices and in your iCloud — deleting it is in your hands: delete data in the app, or delete the app and its iCloud data from your device's iCloud settings. Support emails are kept only as long as needed to help you. If you have questions about your data, or want a support conversation deleted, contact us.

Children

Rego is not directed at children and we do not knowingly collect personal information from children.

Changes to this policy

If this policy changes, we'll update this page and its effective date. Meaningful changes will be noted in the app's release notes.

Contact

Peer Assembly Ltd · rego@peerassembly.com