Privacy policy

Our Privacy Principles

The core principles that guide how we handle your data

Data Encryption

All your data is encrypted both in transit and at rest using industry-standard encryption protocols.

Minimal Collection

We only collect data that’s essential for the emergency communication service to function properly.

No Selling

We never sell, rent, or share your personal data with third parties for marketing purposes.

Secure Storage

Your data is stored on secure servers with regular backups and strict access controls.

1. Information We Collect

Account Information

We collect minimal information required to provide the emergency communication service: your email address (for authentication and service notifications), display name (optional), and phone number (optional, for SMS alerts). We follow a data minimization principle, collecting only what is essential for service operation.

Emergency Contact Information

You provide emergency contact details (names, emails, phone numbers) for individuals who should be notified in emergency situations. You are responsible for obtaining consent from these contacts before adding them to the system. Contact names, emails and phone numbers are stored as account data so the server can send the alert; they are not client-side encrypted. The confidential emergency package is encrypted on the server when you save it, over TLS, once recipients with a registered key are selected.

Location Data

Location data is collected ONLY when you explicitly enable location-based safety protocols, or when you insert your position in your message with the GPS button. This includes GPS coordinates, accuracy information, and timestamps. Location data is only shared with your emergency contacts when a protocol triggers.

Usage Data & Protocol History

We collect protocol creation times, check-in confirmations, missed check-ins, and protocol completion status to provide the service functionality. This data is retained and shown in your history page. Anonymous analytics may be collected to improve service quality.

Security Events & Logs

We record security events: access to emergency pages, PIN attempts, document downloads, protocol stops and changes to contacts, with the IP address and browser (user agent) where relevant. They are kept for as long as your account exists, for security analysis and fraud prevention, and are deleted with it. Sign-in attempts are recorded by Supabase, our authentication provider.

File Metadata

When you upload files to emergency packages, we store file metadata (filename, size, upload timestamp, content type). On paid plans, documents are encrypted for each recipient contact before storage, and the PIN that unlocks them is stored only as a cryptographic hash. We do not offer PIN recovery. Files linked to completed protocols are deleted after 30 days.

2. How We Use Your Information

Primary Purpose: Emergency Communication Service

Your data is used to provide the core emergency communication functionality: sending alerts to your emergency contacts when safety protocols trigger, managing check-in schedules, location protocols (when enabled), and heartbeat monitoring. This is the fundamental purpose of the service.

Security Monitoring & Rate Limiting

We use these records, and rate limits on PIN checks, sign-in and email sending, to protect accounts from unauthorized access and brute-force attacks, and to respond quickly to potential threats.

Service Improvement & Bug Fixes

Anonymous, aggregated analytics help us understand how the service is used and identify areas for improvement. We analyze protocol completion rates, feature usage patterns, and error logs to fix bugs and enhance reliability.

Legal Compliance & Law Enforcement

We may disclose information when required by law, court order, or legal process. In exceptional cases involving imminent danger to life, we may cooperate with law enforcement. We will notify you of legal requests unless prohibited by law.

Service Communications (No Marketing)

We send essential service notifications (protocol reminders, security alerts, service updates, billing information). We do NOT send marketing emails without your explicit opt-in consent. You can manage notification preferences in your account settings.

3. Data Protection & Security

Encryption of Sensitive Data

Your confidential emergency package is encrypted for each recipient contact before it is stored: your message on every plan, and your saved links and documents on paid plans. Contact details (names, emails, phone numbers) are not encrypted this way, because the server needs them to send alerts. The key material that unlocks a contact’s emergency data is protected by that contact’s PIN, and the PIN itself is stored only as a cryptographic hash. We do not offer PIN recovery: if a PIN is lost, data already encrypted for it cannot be restored.

How the Encryption Works

The content of an emergency package is encrypted with AES-256, and its key is wrapped with each contact’s RSA public key. Each contact’s private key is itself encrypted with a key derived from that contact’s PIN, and the package is decrypted in the contact’s browser once they enter it. All data is also encrypted in transit (TLS/HTTPS) and at rest. This is not end-to-end encryption: our servers handle your content to encrypt it and to deliver alerts. End-to-end encryption is planned for a future version, and we are working on it.

PIN Security & Hashing

Your PIN is never stored in plain text. It is hashed using secure one-way cryptographic functions, making it computationally hard to reverse. Emergency contact PINs are also hashed for protection. Rate limiting prevents brute-force attacks. We do not offer PIN recovery: if a PIN is lost, data already encrypted for it cannot be restored. A contact who has lost their PIN can be issued a new PIN and a new key, which restores access to emergency packages saved from that point onward.

Access Controls & Internal Policies

We maintain strict internal access policies. Access to production systems is limited to essential personnel only. All administrative actions are logged. Database access is controlled via role-based permissions.

Secure Infrastructure

Data is stored on Supabase cloud infrastructure, with regular automated backups. All network communications use TLS/HTTPS encryption. Our providers publish their own security practices and certifications, and update them often: refer to them directly (the list is in section 4).

4. Data Sharing & Disclosure

Emergency Contacts (Only When Protocols Trigger)

Your emergency information is shared with your designated emergency contacts ONLY when a safety protocol triggers (missed check-in, location confirmation failure, heartbeat timeout). This is the core functionality you explicitly configured. Your contacts receive decrypted information using their emergency PINs.

Service Providers (Strict Minimum)

We use third-party service providers to deliver the service. Each has access only to the data its job requires:

• Supabase: database, file storage and server functions
• Vercel: hosting of the website and the web app
• Resend: delivery of emails (sign-in codes, invitations, alerts)
• Twilio: delivery of SMS alerts, on the plans that include them
• OneSignal: push notifications in the iPhone app
• Stripe: payment processing
• Mapbox: maps and place search
• Cloudflare: protection against automated sign-ups (Turnstile)
• Sentry: error monitoring
• PostHog: audience measurement, without cookies (see section 7)
• Formspree: the contact form of the website
• EmailOctopus: the newsletter, if you subscribe to it
• GitHub: code repository

Each provider publishes its own security and privacy practices and updates them often: each name above links to them, so please refer to them directly.

Legal Requirements & Law Enforcement

We may disclose information when required by valid legal process (court orders, subpoenas, search warrants) or to comply with applicable laws. In exceptional cases involving imminent danger to life or serious crimes, we may cooperate with law enforcement. We will notify you of legal requests unless prohibited by law or court order.

Business Transfers

If Aegis Mark 1 is acquired, merged, or sells assets, your information may be transferred to the new entity. We will notify you via email at least 30 days before any such transfer. You will have the right to delete your account before the transfer if you choose.

We NEVER Sell Your Data

We do NOT sell, rent, or share your personal information with third parties for marketing or advertising purposes. Your emergency communication data is not a commodity. We do NOT participate in data brokerage or advertising networks.

5. Your Rights (GDPR and CCPA)

Under GDPR (European Union) and CCPA (California) data protection laws, you have comprehensive rights regarding your personal information. These rights apply regardless of your location:

Access Your Data

Download a complete copy of your personal data via one-click export in your settings. Export includes contacts, protocols, history, and metadata in machine-readable JSON format.

Rectification (Update Data)

Update incorrect or incomplete information anytime through your account settings. You have full control over contact details, profile information, and protocol configurations.

Right to Deletion (Right to be Forgotten)

Permanently delete your account and all associated data. Deletion is immediate and irreversible. Some data may be retained if required by law (e.g., billing records).

Data Portability

Export your data in a structured, machine-readable format (JSON) for transfer to another service. Export function available in account settings.

Object to Processing

Essential processing required for service operation cannot be opted out of.

Withdraw Consent

You can control location sharing on a per-mission basis when creating safety protocols. Essential service features (authentication, security monitoring) cannot be disabled as they are required for the service to function.

Lodge a Complaint

Contact your local data protection supervisory authority if you believe your rights have been violated. In France: CNIL (Commission Nationale de l’Informatique et des Libertés).

Restrict Processing

Request limitation of processing in certain circumstances (e.g., while disputing data accuracy). Contact us to exercise this right.

To exercise any of these rights, contact us at legal@safety-checkpoint.com. We will respond within 30 days (GDPR requirement) or 45 days (CCPA requirement).

6. Data Retention

Active Data

Data associated with your active account (profile, contacts, active protocols) is retained for as long as your account remains active. You can delete your account at any time.

Protocols

Your protocols, completed ones included, stay in your history until you delete them or delete your account. Files attached to a protocol are deleted 30 days after it ends or is deleted, and unfinished drafts are deleted with their files after 7 days. When you delete a protocol, it leaves your history at once; its reminders and alert statistics are erased after 30 days, and the rest of its record when you delete your account.

Email History

Email delivery logs and history are retained for 90 days for troubleshooting and service quality purposes, then automatically deleted.

Security Logs

Security records (access to emergency pages, PIN attempts, document downloads, protocol stops, changes to contacts) are kept for as long as your account exists, for security analysis and fraud prevention, and are deleted with it. Sign-in records are kept by Supabase, our authentication provider, under its own retention rules.

Soft-Deleted Contacts

When you delete a contact, it is soft-deleted and retained for 30 days in case of accidental deletion. After 30 days, the contact is permanently and irreversibly deleted from all systems.

Deleted Accounts

Account deletion is immediate and permanent. Once you confirm deletion and verify your PIN (if you have set one), all your data (contacts, missions, files, settings) is permanently deleted from our systems. This action cannot be undone. We recommend exporting your data before proceeding.

Note: Due to standard database backup retention policies, copies of your data may persist in encrypted backups for up to 90 days before automatic expiration.

Legal Holds

If data is subject to legal holds, court orders, or ongoing investigations, retention periods may be extended as required by law. We will notify you if this applies to your data.

Billing Records

Subscription and payment records may be retained longer for tax compliance and dispute resolution purposes, as required by French and EU financial regulations.

7. Cookies & Tracking Technologies

Essential Cookies

We use essential cookies for session management, authentication, and security. These cookies are necessary for the service to function and cannot be disabled without breaking core functionality.

Analytics

We use PostHog, hosted in the European Union, to count page views and a few product events, such as a sign-up being started. It runs without cookies and stores nothing on your device: each page load gets a new random identifier, so we cannot follow you from one visit to the next. We do not record sessions and we do not capture what you type. Analytics sends nothing from the pages your emergency contacts open (the emergency page, the protocol status page, the invitation and the consent withdrawal page), nor from the iPhone app, and a browser that sends Do Not Track or Global Privacy Control is not counted. PostHog receives the address of the page, without its parameters, and the site you came from; as with any web request, its servers also see your IP address, from which an approximate location is derived.

No Third-Party Advertising Cookies

We do NOT use third-party advertising cookies or tracking pixels for marketing purposes. We do NOT participate in ad networks or retargeting campaigns.

8. International Data Transfers

Data Storage Locations

Your data is stored on Supabase infrastructure in Paris, France (European Union).

Transfers Outside the EU

Some of the service providers listed in section 4 process data outside the EU, mainly in the United States. Each of them publishes where it processes data, and updates it over time: refer to their documentation directly.

When data is transferred to the United States or other non-EU countries, our service providers use Standard Contractual Clauses (SCCs) or rely on adequacy decisions approved by the European Commission to protect your data as the GDPR requires.

Global Protection Standards

Wherever a provider processes your data, we apply the same security and encryption standards.

9. Children’s Privacy (Age Restriction: 16+)

Age Requirement

Safety Checkpoint is intended for users aged 16 years or older. We do not knowingly collect personal information from individuals under 16 years of age.

Parental Notification

If we become aware that we have collected personal information from a user under 16, we will take steps to delete that information immediately. Parents or guardians can contact us to request deletion of a minor’s data.

How to Report

If you believe a user under 16 has created an account, please contact us immediately at legal@safety-checkpoint.com.

10. Changes to This Privacy Policy

Notification of Changes

We may update this Privacy Policy from time to time to reflect changes in our practices, legal requirements, or service features. We will notify you via email at least 30 days before any material changes take effect.

Continued Use Constitutes Acceptance

Continued use of Safety Checkpoint after receiving notice of Privacy Policy changes constitutes your acceptance of the updated policy. If you disagree with changes, you may delete your account before the changes take effect.

Material Changes May Require Explicit Consent

For significant changes that materially affect your rights or how we process sensitive data, we may require explicit consent before the changes apply to you.

11. Contact Us

If you have any questions about this Privacy Policy, our data practices, or wish to exercise your rights, please contact us:

Email: legal@safety-checkpoint.com