How your data is used

Account, contact, and check-in records help run the service and send notifications. HereSignal does not continuously track your live location by default. Data uses, retention, and deletion options are explained below.

Tracking

HereSignal does not track your live location all the time.

Who sees what

Trusted contacts only receive the information needed when a missed check-in flow reaches them.

Data use

Data is used to run your routine, explain delivery problems, and support your account.

Still to confirm

Before launch

A few store and legal details are still being prepared. We keep them visible so you know what is ready today.

App Store URL is still pending verification before public launch.
Google Play URL is still pending verification before public launch.
Legal entity name, registered address, and jurisdiction are not finalized yet.

What we collect

Minimal account identifiers and subscription state needed to operate the service.
Trusted contact configuration, enabled channels, and verification state.
Check-in, presence, reminder, and delivery records needed to run the missed check-in flow.
Device and permission state needed to explain why reminders may fail or be delayed.

What we do not collect by default

No default real-time location tracking.
No long-term raw sensor sequence retention.
No advertising profile or behavioral profiling for resale.
No automatic connection to police, rescue, or medical dispatch.

Why we process data

To run scheduled check-ins, reminders, and trusted contact notifications.
To verify contacts and prevent failed delivery caused by bad setup.
To support account, billing, and entitlement state.
To understand delivery issues and keep the service dependable.

Rights and choices

Review or update trusted contacts and enabled channels.
Pause monitoring when you do not want the missed check-in flow to run.
Delete your account to trigger cloud-side data deletion.
Clear local cache without deleting your account, settings, or pending local queues.

Retention summary

This page explains the current retention windows in clear terms.

Check-ins and presence events

Retention

Free 30 days / Pro 90 days

Used for recent history, export, and support continuity.

Activity summaries

Retention

Free 30 days / Pro 180 days

Compressed aggregate layer for recent trend logic.

Notification requests and delivery logs

Retention

30 days

Used to review delivery problems and recent notification history.

Deleted trusted contacts

Retention

30 days after soft delete

Then physically deleted.

Mail queue documents

Retention

14 days

Queue/fallback storage only, not a permanent archive.

Analytics daily aggregates

Retention

365 days

Longer-lived aggregate reporting rather than raw detail.

Dataset	Retention	Notes
Check-ins and presence events	Free 30 days / Pro 90 days	Used for recent history, export, and support continuity.
Activity summaries	Free 30 days / Pro 180 days	Compressed aggregate layer for recent trend logic.
Notification requests and delivery logs	30 days	Used to review delivery problems and recent notification history.
Deleted trusted contacts	30 days after soft delete	Then physically deleted.
Mail queue documents	14 days	Queue/fallback storage only, not a permanent archive.
Analytics daily aggregates	365 days	Longer-lived aggregate reporting rather than raw detail.

Company name, address, and jurisdiction will be added here before launch.