Privacy Policy
Last modified October 10, 2026 · Bearing Life is operated by P2 Reserve LLC.
1. Introduction
P2 Reserve LLC ("Bearing Life," "we," "us," or "our") respects your privacy and is committed to protecting it through this privacy policy ("Privacy Policy"). Bearing Life is a family preparedness and care coordination application that gives families one centralized place to organize documents, coordinate care, and manage health information so that everything is accessible during an emergency.
This Privacy Policy applies to personal information we collect when you:
- create an account and use the Bearing Life mobile or web application;
- enter information about yourself and the people you care for, including health information, documents, and contacts;
- use features such as the Vault, AI Scan, Crisis SOS, tasks and reminders, and circle invitations; and
- visit our website and landing pages.
It does not apply to information collected by us offline, or by any third party whose application or content may link to or be accessible from our app and whose data practices we do not control.
Please read this Privacy Policy carefully. If you do not agree with our practices, please do not use Bearing Life. If you have questions, contact us using the information in Section 14.
Controller. For users in the European Economic Area ("EEA"), the United Kingdom ("UK"), and Switzerland, P2 Reserve LLC is the "controller" of your personal information (called "personal data" under those laws). Our contact details, and the contact details of our EEA/UK representative where one is appointed, are in Section 14.
2. Children and Care Recipients Under 18
Bearing Life is intended for use by adults to organize and coordinate care for themselves and the people they care for. You may use Bearing Life to manage information about your dependents and care recipients of any age, including minor children, but only when you are their parent or legal guardian or are otherwise authorized to do so.
Bearing Life is not directed to children, and we do not knowingly allow anyone under 18 to create their own account. We collect information about a minor only at the direction of an authorizing adult, and only as necessary to provide care coordination. By entering a minor's information, you affirm that you are legally authorized to do so under the laws of your jurisdiction. If we learn that a person under 18 has created an account without authorization, we will delete that account. To review, update, or request deletion of a minor's information, contact us.
We do not "sell" (as that term is defined under California law) the personal information of any consumer. The only personal information we "share" under California law, meaning disclose for cross-context behavioral advertising, is marketing-website visit data, as described in Section 12. We do not knowingly sell or share the personal information of consumers under 16.
3. Personal Information We Collect, Sources, Purposes, and Retention
The personal information we collect depends on how you use Bearing Life. Almost all of it is information you choose to enter about yourself and the people you care for. The table below sets out, for each category we collect: what it includes, the source, the business or commercial purpose, and how long we keep it.
Sources. We collect personal information (a) directly from you when you register, enter information, upload documents, capture images, or use any feature; and (b) automatically from your device and our infrastructure (for example, IP address and request logs) when the app communicates with our servers.
Category
Identifiers
What it includes
Name of you and each care recipient, email address, phone number (if you choose to sign in by phone), account UUID, OAuth profile (Google/Apple), session tokens, and similar identifiers.
Source
You; OAuth provider
Purpose
Account creation, authentication, app functionality
Retention
For the life of your account; deleted on account deletion (see Section 9)
Category
Account credentials
What it includes
One-time sign-in codes sent to you by email, or by text message (SMS) if you sign in with your phone number; we do not store a password for your account.
Source
You
Purpose
Authentication, account security
Retention
Each code expires after a short time and is not kept after use
Category
Contact information
What it includes
Emergency contact names and phone numbers, including your own if you list yourself as a person's emergency contact, and provider or pharmacy phone numbers you save.
Source
You
Purpose
Care coordination, emergency response. An emergency contact's number is saved with that person's record, and every member of that care circle can see it
Retention
For the life of your account, or until you delete the record
Category
Demographic information
What it includes
Date of birth of you and care recipients.
Source
You
Purpose
Health record accuracy, age-appropriate care
Retention
For the life of your account, or until you delete the record
Category
Health information (sensitive)
What it includes
Medications (drug, dosage, prescriber, pharmacy, refill dates, schedule), supplements and vitamins (name, brand, amount, schedule, notes), immunizations, appointments, blood type, allergies, and free-text medical notes for you and your care recipients.
Source
You
Purpose
Storing and organizing care information, reminders, Bearing Score, AI crisis plan
Retention
For the life of your account, or until you delete the record
Category
Documents and files
What it includes
Files you upload to the Vault and their metadata (title, category, file name, type, issue and expiry dates, notes), including identity, medical, legal, financial, insurance, and education documents.
Source
You
Purpose
Document storage and retrieval, expiration reminders
Retention
For the life of your account, or until you delete the document
Category
Photos and images
What it includes
Profile photos of people in your circle and document images you capture for the AI Scan feature (for example, prescription bottles or insurance cards).
Source
You
Purpose
Personalization; AI Scan extraction
Retention
Profile photos: life of account. Scan images: passed through for extraction and not stored by us as separate records (see Section 8)
Category
Precise geolocation (sensitive)
What it includes
GPS latitude and longitude captured only when you trigger a Crisis SOS alert.
Source
You/device
Purpose
Capturing and displaying your emergency location so you can share it
Retention
Stored with the alert record; deleted when you delete the alert or your account
Category
Approximate location / search text
What it includes
Free-text place queries used for appointment and task location autocomplete, sent to a mapping service without any account information attached.
Source
You
Purpose
Location autocomplete
Retention
Not stored by us beyond the saved field you choose
Category
User content
What it includes
Tasks and reminders, family or circle membership and permissions, onboarding quiz answers, Bearing Score snapshots, crisis progress and alerts, and notification preferences.
Source
You
Purpose
App functionality
Retention
For the life of your account, or until you delete the content
Category
Push notification token
What it includes
A device push token that lets us deliver notifications to your device.
Source
Your device, only after you allow notifications
Purpose
Delivering task updates from your care circle and emergency alerts, and, only if you opt in, reminders about a Bearing Plus offer, which you can turn off in Settings
Retention
Removed when you sign out on that device, and in any case deleted with your account
Category
Subscription information
What it includes
Your plan status (Plus, trial, free, or locked); the timing of any subscription offer, the offer's prices and currency as the store showed them, the reminders sent, your time zone offset, and the short relationship label used in a reminder (for example "Mom"), so reminders arrive at a sensible hour and read naturally; and, if you subscribe to Bearing Plus, your purchase history: the purchase and transaction information the app store sends for your subscription, such as product, renewal, trial, and refund status. We never receive your payment card details; the App Store or Google Play processes payment, depending on where you bought your subscription.
Source
You; the App Store or Google Play, through our subscription processor (RevenueCat), when you subscribe
Purpose
Providing your Bearing Plus subscription and managing it
Retention
For the life of your account. Deleting your account also deletes your customer record at our subscription processor. The record of your purchase held by Apple or Google is not deleted when you delete your account (see Section 9).
Category
Internet and device activity
What it includes
IP address and request logs automatically collected by our backend infrastructure.
Source
Automatic
Purpose
Security, fraud prevention, debugging
Retention
Limited log-retention period set by our infrastructure provider, unless needed for security or legal reasons
Category
Crash and performance telemetry
What it includes
The generic route name of each screen opened (never its content), crash reports, errors, and network request timing, sent by versions of the app already installed. This can include identifiers for your care circle and for individual records, so it can be associated with your account. We have removed this from the app, so a version you update to sends none of it.
Source
Automatic, in already-installed versions only
Purpose
Finding and fixing crashes and performance problems
Retention
Collection ends once the update has finished rolling out; held by our monitoring provider for its own limited retention period
Category
App usage record
What it includes
For each signed-in account, the days you open the app, how many times you open it each day, and the time of the first and last open that day. It holds no content from your account.
Source
Automatic, when you are signed in
Purpose
Running and improving the service, seeing whether it is helping, and, only as aggregate counts that identify no one, planning our own advertising
Retention
For the life of your account; deleted on account deletion (see Section 9)
Category
Product analytics
What it includes
Four one-time setup milestones: your first open of the app, finishing setup, adding your first care recipient, and adding your first document. The three that happen after you sign in are tied to your account UUID; the first-open one fires before an account exists, so if you install the app and never sign in it is never tied to an account. Setup progress: during first-time setup, the name of each setup step you reach, the plan you chose, and whether saving your account, subscribing, restoring a purchase, or redeeming an offer code completed, was cancelled or failed. These record only that a step was reached, never your answers to the setup questions. Steps reached before you create an account carry only a random identifier made on your device, and are tied to your account UUID once you sign in. Each of these also carries the basic device and app information the analytics software attaches, such as device type and model, operating system and version, and app version. The events we send carry no names, document titles, file names, health information, or any other content from your account, and we turn off the provider's IP-based location lookup.
Source
Automatic, in versions of the app released from September 2026 onward (setup progress: from October 2026 onward)
Purpose
Seeing whether setup works for families, so we can improve it, and, only as aggregate counts that identify no one, planning our own advertising
Retention
Held by our analytics provider for its own retention period. It is not deleted automatically when you delete your account; contact us and we will delete it (see Section 9)
Category
Account login information (sensitive)
What it includes
Email, phone number, or OAuth identifier in combination with the one-time sign-in codes (emailed, or sent by text message if you sign in by phone) and session tokens allowing access to your account.
Source
You; OAuth provider
Purpose
Authentication
Retention
For the life of your account
Category
Biometric information
What it includes
We do not collect biometric identifiers. If you turn on the optional app lock, Face ID or Touch ID matching happens entirely on your device, handled by its operating system; the app learns only whether the unlock succeeded, and no biometric data ever reaches us. Profile and document photos are stored as images and are not used to create faceprints or other biometric templates.
Source
-
Purpose
-
Retention
Not collected
Category
Professional or employment information
What it includes
Bearing Life is a direct-to-consumer app and does not collect employment or professional records.
Source
-
Purpose
-
Retention
Not collected
Category
Tracking / advertising identifiers
What it includes
The Bearing Life app collects none: it contains no advertising SDKs and does no cross-app tracking, and we use no data brokers. Parts of our public marketing website use the Meta Pixel and Google Analytics 4, which set cookies and similar identifiers in your browser. See Section 12.
Source
Website only: your browser, through Meta and Google
Purpose
Website only: planning and measuring our own advertising
Retention
App: not collected. Website: kept by Meta and Google under their own retention periods
| Category | What it includes | Source | Purpose | Retention |
|---|---|---|---|---|
| Identifiers | Name of you and each care recipient, email address, phone number (if you choose to sign in by phone), account UUID, OAuth profile (Google/Apple), session tokens, and similar identifiers. | You; OAuth provider | Account creation, authentication, app functionality | For the life of your account; deleted on account deletion (see Section 9) |
| Account credentials | One-time sign-in codes sent to you by email, or by text message (SMS) if you sign in with your phone number; we do not store a password for your account. | You | Authentication, account security | Each code expires after a short time and is not kept after use |
| Contact information | Emergency contact names and phone numbers, including your own if you list yourself as a person's emergency contact, and provider or pharmacy phone numbers you save. | You | Care coordination, emergency response. An emergency contact's number is saved with that person's record, and every member of that care circle can see it | For the life of your account, or until you delete the record |
| Demographic information | Date of birth of you and care recipients. | You | Health record accuracy, age-appropriate care | For the life of your account, or until you delete the record |
| Health information (sensitive) | Medications (drug, dosage, prescriber, pharmacy, refill dates, schedule), supplements and vitamins (name, brand, amount, schedule, notes), immunizations, appointments, blood type, allergies, and free-text medical notes for you and your care recipients. | You | Storing and organizing care information, reminders, Bearing Score, AI crisis plan | For the life of your account, or until you delete the record |
| Documents and files | Files you upload to the Vault and their metadata (title, category, file name, type, issue and expiry dates, notes), including identity, medical, legal, financial, insurance, and education documents. | You | Document storage and retrieval, expiration reminders | For the life of your account, or until you delete the document |
| Photos and images | Profile photos of people in your circle and document images you capture for the AI Scan feature (for example, prescription bottles or insurance cards). | You | Personalization; AI Scan extraction | Profile photos: life of account. Scan images: passed through for extraction and not stored by us as separate records (see Section 8) |
| Precise geolocation (sensitive) | GPS latitude and longitude captured only when you trigger a Crisis SOS alert. | You/device | Capturing and displaying your emergency location so you can share it | Stored with the alert record; deleted when you delete the alert or your account |
| Approximate location / search text | Free-text place queries used for appointment and task location autocomplete, sent to a mapping service without any account information attached. | You | Location autocomplete | Not stored by us beyond the saved field you choose |
| User content | Tasks and reminders, family or circle membership and permissions, onboarding quiz answers, Bearing Score snapshots, crisis progress and alerts, and notification preferences. | You | App functionality | For the life of your account, or until you delete the content |
| Push notification token | A device push token that lets us deliver notifications to your device. | Your device, only after you allow notifications | Delivering task updates from your care circle and emergency alerts, and, only if you opt in, reminders about a Bearing Plus offer, which you can turn off in Settings | Removed when you sign out on that device, and in any case deleted with your account |
| Subscription information | Your plan status (Plus, trial, free, or locked); the timing of any subscription offer, the offer's prices and currency as the store showed them, the reminders sent, your time zone offset, and the short relationship label used in a reminder (for example "Mom"), so reminders arrive at a sensible hour and read naturally; and, if you subscribe to Bearing Plus, your purchase history: the purchase and transaction information the app store sends for your subscription, such as product, renewal, trial, and refund status. We never receive your payment card details; the App Store or Google Play processes payment, depending on where you bought your subscription. | You; the App Store or Google Play, through our subscription processor (RevenueCat), when you subscribe | Providing your Bearing Plus subscription and managing it | For the life of your account. Deleting your account also deletes your customer record at our subscription processor. The record of your purchase held by Apple or Google is not deleted when you delete your account (see Section 9). |
| Internet and device activity | IP address and request logs automatically collected by our backend infrastructure. | Automatic | Security, fraud prevention, debugging | Limited log-retention period set by our infrastructure provider, unless needed for security or legal reasons |
| Crash and performance telemetry | The generic route name of each screen opened (never its content), crash reports, errors, and network request timing, sent by versions of the app already installed. This can include identifiers for your care circle and for individual records, so it can be associated with your account. We have removed this from the app, so a version you update to sends none of it. | Automatic, in already-installed versions only | Finding and fixing crashes and performance problems | Collection ends once the update has finished rolling out; held by our monitoring provider for its own limited retention period |
| App usage record | For each signed-in account, the days you open the app, how many times you open it each day, and the time of the first and last open that day. It holds no content from your account. | Automatic, when you are signed in | Running and improving the service, seeing whether it is helping, and, only as aggregate counts that identify no one, planning our own advertising | For the life of your account; deleted on account deletion (see Section 9) |
| Product analytics | Four one-time setup milestones: your first open of the app, finishing setup, adding your first care recipient, and adding your first document. The three that happen after you sign in are tied to your account UUID; the first-open one fires before an account exists, so if you install the app and never sign in it is never tied to an account. Setup progress: during first-time setup, the name of each setup step you reach, the plan you chose, and whether saving your account, subscribing, restoring a purchase, or redeeming an offer code completed, was cancelled or failed. These record only that a step was reached, never your answers to the setup questions. Steps reached before you create an account carry only a random identifier made on your device, and are tied to your account UUID once you sign in. Each of these also carries the basic device and app information the analytics software attaches, such as device type and model, operating system and version, and app version. The events we send carry no names, document titles, file names, health information, or any other content from your account, and we turn off the provider's IP-based location lookup. | Automatic, in versions of the app released from September 2026 onward (setup progress: from October 2026 onward) | Seeing whether setup works for families, so we can improve it, and, only as aggregate counts that identify no one, planning our own advertising | Held by our analytics provider for its own retention period. It is not deleted automatically when you delete your account; contact us and we will delete it (see Section 9) |
| Account login information (sensitive) | Email, phone number, or OAuth identifier in combination with the one-time sign-in codes (emailed, or sent by text message if you sign in by phone) and session tokens allowing access to your account. | You; OAuth provider | Authentication | For the life of your account |
| Biometric information | We do not collect biometric identifiers. If you turn on the optional app lock, Face ID or Touch ID matching happens entirely on your device, handled by its operating system; the app learns only whether the unlock succeeded, and no biometric data ever reaches us. Profile and document photos are stored as images and are not used to create faceprints or other biometric templates. | - | - | Not collected |
| Professional or employment information | Bearing Life is a direct-to-consumer app and does not collect employment or professional records. | - | - | Not collected |
| Tracking / advertising identifiers | The Bearing Life app collects none: it contains no advertising SDKs and does no cross-app tracking, and we use no data brokers. Parts of our public marketing website use the Meta Pixel and Google Analytics 4, which set cookies and similar identifiers in your browser. See Section 12. | Website only: your browser, through Meta and Google | Website only: planning and measuring our own advertising | App: not collected. Website: kept by Meta and Google under their own retention periods |
How storage works. When the app runs in its local-only configuration, your information stays on your device and nothing leaves it except calls to the AI and mapping features described below. When the app is connected to our cloud backend, your information is stored and synchronized through that backend so it is available across your devices and to the people you invite to your circle.
Where AI data goes. When you use an AI feature, the relevant information (and, for AI Scan, the document image) is transmitted from the app through our backend to our AI provider (Anthropic) to perform the feature you requested, and is not retained by Anthropic as part of an ongoing record. See Section 8.
4. Sensitive Personal Information
Some of the information we collect is "sensitive personal information" under California law and "special category data" under European and UK law. This includes your health information, precise geolocation, and your account login credentials.
We use and disclose sensitive personal information only to provide Bearing Life to you and the people in your circle, to secure your account, to prevent fraud, and as otherwise permitted by Cal. Civ. Code § 1798.121 and applicable law. We do not use it to infer characteristics about you, for advertising, or for any purpose other than providing and securing the service. Because we limit our use of sensitive personal information to these permitted purposes, we are not required to offer, and do not offer, a separate "Limit the Use of My Sensitive Personal Information" link, but you may still contact us to exercise your rights.
For users in the EEA, UK, and Switzerland, we process health and other special category data only with your explicit consent (Article 9(2)(a) GDPR), which you provide when you choose to enter health information or use a health-related feature. You may withdraw that consent at any time (see Section 6); withdrawing consent does not affect processing already carried out, and may mean we can no longer provide some features.
5. How We Use Your Personal Information and Legal Bases
We use your personal information to operate Bearing Life and provide the features you ask for. Specifically, we use it:
- To create and support your account and authenticate you.
- To let you sign in with your phone number as an alternative to email. If you choose phone sign-in, we send a one-time sign-in code to your phone by text message (SMS) through our text message provider, to confirm it is you. Phone sign-in is optional; you can also sign in with a one-time code sent to your email, or with Google or Apple.
- To save the emergency contact you list for a person in your circle, which can be you or someone else, with a phone number. That number is saved with that person's record, and every member of that care circle can see it. Listing an emergency contact is optional, and you can edit or remove it in the app at any time, from the person's profile under Emergency contact. Aside from any sign-in code you request, we do not use your phone number for marketing and do not send promotional text messages.
- To store, organize, and synchronize the documents, health information, contacts, tasks, and other content you enter.
- To generate your Bearing Score and readiness snapshots from the completeness of your health and document information.
- To power AI features, including generating a crisis readiness plan and reading documents you scan.
- To deliver circle invitations and the notifications and reminders you turn on, such as refill, appointment, expiration, and task alerts.
- To capture and display your emergency location when you trigger a Crisis SOS alert, so you can share it with responders or the people in your circle.
- To maintain the security of the app, prevent fraud and abuse, and debug and improve functionality.
- To comply with our legal obligations.
We do not sell your personal information for money or other valuable consideration. We never use anything you enter into the Bearing Life app, including your account, your records, your documents, and information about the people you care for, for advertising, marketing profiling, or cross-app tracking, and we never disclose it to advertising networks or sell it. We use aggregate, de-identified website and app metrics (like visits, installs, and feature counts) to plan and measure our own advertising. The advertising measurement on our marketing website is described in Section 12.
Legal bases (EEA / UK / Switzerland). Where European or UK law applies, we rely on the following legal bases under Article 6(1) GDPR:
| Purpose | Legal basis |
|---|---|
| Creating and operating your account; storing and syncing your content; delivering invitations, reminders, and the features you request | Performance of a contract with you (Art. 6(1)(b)) |
| Processing health and other special category data; using precise location for Crisis SOS | Your explicit consent (Art. 6(1)(a) + Art. 9(2)(a)); you may withdraw it at any time |
| Securing the app, preventing fraud and abuse, debugging, and improving functionality | Our legitimate interests in running a safe, reliable service (Art. 6(1)(f)) |
| Retaining records and responding to lawful requests | Compliance with a legal obligation (Art. 6(1)(c)) |
Automated decision-making. We do not make decisions that produce legal or similarly significant effects about you based solely on automated processing. The Bearing Score and AI-generated crisis plans are informational aids to help you; they do not make decisions about you, and you remain in control.
6. Your Rights and Choices
Depending on where you live, including U.S. states such as California, Colorado, Connecticut, Texas, Virginia, Oregon, Montana, and others, and the EEA, UK, and Switzerland, you may have some or all of the following rights regarding your personal information:
- Right to know / access what personal information we have collected about you, the sources, the purposes, and the categories of third parties to whom it is disclosed.
- Right to a portable copy of your information in a usable format.
- Right to correct inaccuracies in your information.
- Right to delete the personal information we have collected from you, subject to limited exceptions.
- Right to restrict or object to certain processing, and to limit the use and disclosure of sensitive information.
- Right to withdraw consent at any time where we rely on consent (such as for health data and precise location), without affecting prior processing.
- Right to opt out of the sale or sharing of personal information and of profiling for decisions with legal or significant effects. We never sell your information and we never profile you for decisions with legal or significant effects. The only information we "share" (meaning disclose for cross-context behavioral advertising) is marketing-website visit data, as described in Section 12; nothing from inside the app is shared for advertising. We honor Global Privacy Control automatically, and you can also opt out using the "Do Not Sell or Share My Personal Information" link in the footer of the website pages that use these tools, or by emailing us at the address in Section 14.
- Right to non-discrimination for exercising any of these rights.
- Right to appeal a decision we make about your request (see below).
- Right to lodge a complaint with your local data protection authority (EEA/UK/Switzerland) or attorney general (U.S.).
How to exercise your rights. Because most of your information is stored in your account, you can review, edit, and delete much of it directly within Bearing Life, including people, documents, health records, tasks, and circle members. In addition:
- Deleting your account. You can permanently delete your account and all data in the care groups you own directly in the app: go to Settings → Account → Delete account. We ask you to confirm your sign-in before the deletion runs.
- Requesting a portable copy. To receive a copy of your account and the care groups you own in a machine-readable format, contact us at info@trybearinglife.com and we will deliver it within the response times described under "Timing" below.
For any other request, including correction or an appeal, contact us at info@trybearinglife.com. We will verify your identity before fulfilling a request, by confirming control of the account email, or of the phone number on the account where the account has no email address, and, where necessary, additional information matching what we hold.
Authorized agents. You may use an authorized agent to submit a request on your behalf. We may require the agent to provide proof of your written authorization and may ask you to verify your own identity directly.
Timing. We respond within the timeframes required by applicable law, generally 45 days under U.S. state laws (extendable by another 45 days with notice) and one month under the GDPR/UK GDPR (extendable by two further months for complex requests). We may decline a request where the law allows, such as where we must retain information for security or legal reasons, and we will explain why.
Appeals. If we decline your request and you live in a state or country that provides an appeal right, you may appeal by replying to our decision or emailing info@trybearinglife.com with the subject "Appeal." We will respond within the time required by law (for example, 45–60 days under applicable U.S. state laws). If we deny your appeal, you may contact your state attorney general or, in the EEA/UK/Switzerland, your supervisory authority.
California "Shine the Light." California Civil Code § 1798.83 permits California residents to request information about disclosures of personal information to third parties for their direct marketing purposes. We do not disclose personal information to third parties for their direct marketing purposes.
7. Who We Share Your Information With
We do not sell your personal information, and we never share anything from inside the app for advertising. The marketing-website visit data described in Section 12, which goes to Meta and Google, is the only information we share for advertising. Otherwise, we disclose your personal information only to the service providers and processors needed to run the app, and only to the extent each provider requires to perform its function. We treat these providers as our data processors. We enter into data processing agreements with them where available, and for transfers of personal information out of the European Economic Area or the United Kingdom we rely on appropriate safeguards such as the Standard Contractual Clauses. We are putting data processing agreements in place with our processors. The services that receive data are listed below; the Meta Pixel and Google Analytics are not among them because they receive marketing-website data only (Section 12).
Service
Supabase (our backend service provider)
What is sent
Substantially all data you enter, for authentication, sync, and storage.
Purpose
App functionality, authentication, data synchronization, and storage. Acts as our processor, not an independent third party.
Service
Anthropic (Claude API)
What is sent
For Crisis plans: name, blood type, allergies, medications, insurance document titles, appointments, and emergency contact. For AI Scan: the document image you capture. Sent from the app through our backend to Anthropic.
Purpose
To generate your crisis readiness plan and to read scanned documents. Under our terms with Anthropic, this data is not used to train AI models. See Section 8 for retention.
Service
Resend (email delivery, via our backend)
What is sent
Your account email address and the one-time sign-in code, every time you sign in or create an account by email, which is the primary way you sign in because Bearing Life uses no passwords; the invitee email address, invite code, and care-focus label for circle invitations; and, when an emergency alert cannot reach a circle member's device, that member's email address and the alert message (first names only, never health information).
Purpose
To email your one-time sign-in code so you can sign in and create an account, to send circle-invitation emails on your behalf, and to deliver an emergency alert by email when a circle member cannot be reached by push.
Service
Text message provider (one-time sign-in codes, via our backend)
What is sent
Your phone number and the one-time sign-in code, and only when you choose to sign in by text. Never any health information, and never the content of your account.
Purpose
To deliver your one-time sign-in code by text message (SMS). This provider never receives health information, and we do not use it for marketing. Acts as our processor.
Service
Apple (Sign in with Apple)
What is sent
An identity token when you choose Sign in with Apple, and a token sent back to Apple when you delete an account you created with Apple, to revoke the sign-in grant.
Purpose
To authenticate you when you sign in with Apple, and to revoke that sign-in grant when you delete your account. No health information is sent.
Service
Google (Sign in with Google)
What is sent
An identity token when you choose Sign in with Google.
Purpose
To authenticate you when you sign in with Google. No health information is sent.
Service
Expo (push notification delivery)
What is sent
The device push token and the notification content, which is first names, a relationship label such as "Mom", and IDs only, never health information.
Purpose
To deliver task updates from your care circle and emergency alerts to your device, and, only if you opt in, reminders about a Bearing Plus offer, which you can turn off in Settings. Acts as our processor, not for tracking.
Service
RevenueCat (subscription management)
What is sent
When you subscribe to Bearing Plus, the App Store or Google Play sends purchase and transaction information for your subscription (product, renewal, trial, and refund status) to RevenueCat, along with the app user id, which is your account UUID, and the basic device and app information its software needs to work, such as platform and app version. RevenueCat never receives your payment card details or any health information.
Purpose
To manage your Bearing Plus subscription, keep your entitlement in sync across your devices, and notify our backend of subscription changes. Acts as our processor, not for tracking.
Service
PostHog, Inc. (US Cloud region, Virginia, USA)
What is sent
The setup milestones and setup progress described in Section 3 and your account UUID, plus the basic device and app information its software attaches. Never names, document titles, file names, or health information. Its IP-based location lookup is turned off. Your subscription events also reach it from RevenueCat, joined to the same account UUID. From the check-in on our website, it also receives which screens were reached and which store buttons were tapped, never your answers or anything you type, with no cookies and no link to your account (Section 12).
Purpose
Product analytics: seeing whether setup works for families so we can improve it. Acts as our processor, not an independent third party. Never used for advertising at an individual level, and never sold. Only aggregate counts, which identify no one, help plan our own advertising.
Service
OpenStreetMap Nominatim
What is sent
The free-text location query only, sent without any account information attached.
Purpose
Location autocomplete for appointments and tasks.
Service
Your device's map application
What is sent
A link containing GPS coordinates, opened only if you tap it within a crisis alert.
Purpose
To display an emergency location in your map application. No data is sent through an API or key.
Service
Datadog, Inc. (US1 region, USA), from versions of the app already installed
What is sent
The generic route name of each screen opened (never its content), crash reports, errors, and network request timing. This record can include identifiers for your care circle and for individual records, so it can be associated with your account. We have removed this service from the app, so a version you update to sends none of it.
Purpose
Crash reporting and performance monitoring, so we could find and fix problems and keep the app reliable. Acts as our processor, not an independent third party. This entry ends once the update has finished rolling out.
| Service | What is sent | Purpose |
|---|---|---|
| Supabase (our backend service provider) | Substantially all data you enter, for authentication, sync, and storage. | App functionality, authentication, data synchronization, and storage. Acts as our processor, not an independent third party. |
| Anthropic (Claude API) | For Crisis plans: name, blood type, allergies, medications, insurance document titles, appointments, and emergency contact. For AI Scan: the document image you capture. Sent from the app through our backend to Anthropic. | To generate your crisis readiness plan and to read scanned documents. Under our terms with Anthropic, this data is not used to train AI models. See Section 8 for retention. |
| Resend (email delivery, via our backend) | Your account email address and the one-time sign-in code, every time you sign in or create an account by email, which is the primary way you sign in because Bearing Life uses no passwords; the invitee email address, invite code, and care-focus label for circle invitations; and, when an emergency alert cannot reach a circle member's device, that member's email address and the alert message (first names only, never health information). | To email your one-time sign-in code so you can sign in and create an account, to send circle-invitation emails on your behalf, and to deliver an emergency alert by email when a circle member cannot be reached by push. |
| Text message provider (one-time sign-in codes, via our backend) | Your phone number and the one-time sign-in code, and only when you choose to sign in by text. Never any health information, and never the content of your account. | To deliver your one-time sign-in code by text message (SMS). This provider never receives health information, and we do not use it for marketing. Acts as our processor. |
| Apple (Sign in with Apple) | An identity token when you choose Sign in with Apple, and a token sent back to Apple when you delete an account you created with Apple, to revoke the sign-in grant. | To authenticate you when you sign in with Apple, and to revoke that sign-in grant when you delete your account. No health information is sent. |
| Google (Sign in with Google) | An identity token when you choose Sign in with Google. | To authenticate you when you sign in with Google. No health information is sent. |
| Expo (push notification delivery) | The device push token and the notification content, which is first names, a relationship label such as "Mom", and IDs only, never health information. | To deliver task updates from your care circle and emergency alerts to your device, and, only if you opt in, reminders about a Bearing Plus offer, which you can turn off in Settings. Acts as our processor, not for tracking. |
| RevenueCat (subscription management) | When you subscribe to Bearing Plus, the App Store or Google Play sends purchase and transaction information for your subscription (product, renewal, trial, and refund status) to RevenueCat, along with the app user id, which is your account UUID, and the basic device and app information its software needs to work, such as platform and app version. RevenueCat never receives your payment card details or any health information. | To manage your Bearing Plus subscription, keep your entitlement in sync across your devices, and notify our backend of subscription changes. Acts as our processor, not for tracking. |
| PostHog, Inc. (US Cloud region, Virginia, USA) | The setup milestones and setup progress described in Section 3 and your account UUID, plus the basic device and app information its software attaches. Never names, document titles, file names, or health information. Its IP-based location lookup is turned off. Your subscription events also reach it from RevenueCat, joined to the same account UUID. From the check-in on our website, it also receives which screens were reached and which store buttons were tapped, never your answers or anything you type, with no cookies and no link to your account (Section 12). | Product analytics: seeing whether setup works for families so we can improve it. Acts as our processor, not an independent third party. Never used for advertising at an individual level, and never sold. Only aggregate counts, which identify no one, help plan our own advertising. |
| OpenStreetMap Nominatim | The free-text location query only, sent without any account information attached. | Location autocomplete for appointments and tasks. |
| Your device's map application | A link containing GPS coordinates, opened only if you tap it within a crisis alert. | To display an emergency location in your map application. No data is sent through an API or key. |
| Datadog, Inc. (US1 region, USA), from versions of the app already installed | The generic route name of each screen opened (never its content), crash reports, errors, and network request timing. This record can include identifiers for your care circle and for individual records, so it can be associated with your account. We have removed this service from the app, so a version you update to sends none of it. | Crash reporting and performance monitoring, so we could find and fix problems and keep the app reliable. Acts as our processor, not an independent third party. This entry ends once the update has finished rolling out. |
We may also disclose personal information when required to comply with the law, to enforce our terms, or to protect the rights, property, or safety of Bearing Life, our users, or others. Because some of this information includes health data and other sensitive data, we treat our AI, backend, email, and text message providers as processors and pursue appropriate data protection terms with them.
8. How We Use Artificial Intelligence
Two features use AI, and both run only when you choose to use them. The Crisis plan feature sends relevant emergency information, such as your name, blood type, allergies, medications, insurance document titles, appointments, and emergency contact, to our AI provider to generate a readiness plan. The AI Scan feature sends an image of a document you capture so the AI can read it and help fill in your records. Both AI features are gated by a separate AI consent setting that is off by default and lives in the app's Settings. We enforce it on our servers, so if it is off, nothing is sent to the AI provider even if you trigger a feature. You can withdraw consent at any time by turning that setting off in Settings, which is as easy to find as turning it on.
This information is transmitted from the app through our backend to our AI provider (Anthropic) over an encrypted connection; the app does not send it to any AI provider directly, and we do not embed AI provider keys in the app. Under our terms with Anthropic, your inputs and outputs are not used to train AI models. Anthropic may retain inputs and outputs for a limited period for trust, safety, and abuse-monitoring purposes as described in its commercial terms, after which they are deleted, unless a zero-retention arrangement applies to our account. We do not permit our AI provider to use your information for any purpose other than processing your request, and we do not store the scanned image as a separate record once it has been read.
AI Scan and the AI Crisis plan are optional. You can always enter information manually instead, and when AI is unavailable the app falls back to manual entry or an on-device generator so nothing breaks.
9. How Long We Keep Your Information
We keep your personal information for as long as your account is active and as needed to provide Bearing Life, and afterward only as required to meet legal, security, or recordkeeping obligations. Category-level retention is described in the table in Section 3. When you delete content in the app, or delete your account, we delete the associated information from our active systems, recognizing that removal from routine backups may take additional time. The exceptions are as follows. First, if you subscribed to Bearing Plus, the record of that purchase held by the app store (Apple or Google) stays under that store's own policies and is not deleted when you delete your account; the customer record we hold at our subscription processor is deleted. Second, we keep a security audit trail, described in the next paragraph. Third, the product analytics described in Section 3 (setup milestones and setup progress) are held by our analytics provider and are not deleted automatically; email us and we will delete them. Your device push token is removed when you sign out on that device and is deleted with your account. Information sent to our AI provider is handled as described in Section 8.
The security audit trail is deliberately never deleted. It records, for each change to a protected record, which account made it, what kind of change it was, and when. That trail deliberately survives account deletion, because a security record that can be erased by the person it describes is not a security record. It holds no names, no health information, and no document contents, only account and record identifiers, which care circle the change belonged to, the kind of change, the name of the table it touched, and a timestamp.
You can delete individual records in the app at any time. To delete your entire account and associated data, use the Delete account option in the app under Settings → Account, or contact us at info@trybearinglife.com.
10. How We Protect Your Information
We have implemented reasonable measures designed to protect your personal information. These include encrypted transmission, row-level security and per-category permissions in our backend, access controls that limit what each member of your circle can see, processing of AI requests through our backend rather than directly from your device, and passwordless sign-in that uses a one-time code sent to your email or by text message to your phone, or sign-in through Google or Apple, so we do not store a password for your account. Device push token records are readable only by the account they belong to and are written only through a validated server function. You control who joins your circle and what each member is permitted to view.
You can also turn on an optional app lock that asks for Face ID, Touch ID, or your device passcode before Bearing Life opens. The biometric check happens entirely on your device, handled by its operating system. Bearing Life never sees, collects, or stores your face or fingerprint data; it only learns whether the unlock succeeded. Your app-lock preference is saved on your device, not on our servers.
No system is perfectly secure, and we cannot guarantee absolute security. The safety of your information also depends on you: keep your email account and any phone you sign in with secure, never share a sign-in code with anyone, and be thoughtful about whom you invite into your circle and the permissions you grant them.
Breach notification. If we become aware of a personal-data breach that affects you, we will notify you and the relevant authorities as required by applicable law (including, where applicable, within 72 hours of becoming aware, under the GDPR/UK GDPR).
11. Where Your Information Is Processed and International Transfers
Bearing Life is operated from the United States, and your personal information is processed and stored in the United States. If you use the app from outside the United States, including from the EEA, UK, or Switzerland, your information will be transferred to and processed in the United States, where privacy laws may differ from those in your location.
Where we transfer personal data out of the EEA, UK, or Switzerland, we rely on appropriate safeguards, principally the European Commission's Standard Contractual Clauses (and the UK International Data Transfer Addendum where applicable), together with supplementary measures such as encryption in transit. We are putting these agreements in place with our processors. You may request a copy of the safeguards we use by contacting us.
12. Cookies and Tracking
The Bearing Life application uses only the storage strictly necessary to run the app and keep you signed in. Earlier versions of the app included a crash reporting and performance monitoring service. It received the generic route name of each screen you opened (never its content), errors and crashes, and network request timing, and that record could be associated with your account. We have removed it, so the app no longer includes a crash reporting or performance monitoring service. If you have not updated yet, the version on your device may still be sending it, which is why our Google Play Data safety declaration reports crash logs and diagnostics as collected until the updated version has finished rolling out. The current version does include product analytics: the setup milestones and setup progress described in Sections 3 and 7, sent to PostHog and, once you sign in, tied to your account UUID. They carry no content from your account and never your answers to the setup questions, they are never used for advertising at an individual level (only aggregate counts, which identify no one, help plan our own advertising), and there is no in-app switch to turn them off. The app itself contains no advertising cookies, no advertising SDKs, and no cross-app tracking. We do not respond to "Do Not Track" browser signals, which have no agreed meaning; we honor Global Privacy Control instead, as described below.
We do keep one usage record of our own. For each signed-in account, we record which days you open the app, how many times you open it on those days, and the time of the first and last open each day. We use this only to run and improve the service and to see whether it is genuinely helping the families who rely on it. It is stored in our own systems, tied to your account, and it is never shared with anyone, never sold, and never used for advertising at an individual level. Only aggregate counts, which identify no one, help plan our own advertising. This first-party record is why our Google Play Data safety declaration lists app interactions as collected. It is deleted when you delete your account.
Our marketing website
Our public marketing website at trybearinglife.com is separate from the app. Parts of it use the Meta Pixel and Google Analytics 4 to plan and measure our own advertising. On those pages they record a page view on every visit, and an event when you scroll the download section into view, when you tap an App Store or Google Play badge, and when a waitlist or newsletter signup succeeds. The events we send carry only which page, which form or button, and which platform. We do not add your name, email address, or phone number to these events. Meta and Google may also record how you interact with the page, such as the buttons you tap, and what your browser sends with any request, under their own policies. They set cookies or similar identifiers in your browser. Some pages load fonts from Google Fonts, which receives your IP address when your browser fetches them. Our web host keeps ordinary server logs (such as IP address and the pages requested) to keep the site running and secure. If you join our waitlist or newsletter on the website, we keep your email address to send you those updates; email us at the address in Section 14 to be removed.
Our check-in page (trybearinglife.com/start) also uses PostHog, the same analytics service as the app, to count how many visitors reach each screen of the check-in and how many tap through to the App Store or Google Play. It records a page view, which screens were reached, and which store button was tapped, plus the basic browser and device information its software attaches (such as browser, operating system and screen size) and the link that brought you there. It never receives your answers, anything you type, or your name, email address or phone number, and its IP-based location lookup is turned off. It sets no cookies and stores nothing in your browser: to count visitors without them, PostHog uses a code made from your IP address and browser that changes every day, so it cannot recognize you on a later day. It does not record your session, and it is not linked to your app account. It is used only to see where people stop in the check-in, so we can improve it, and as aggregate counts that identify no one.
When you tap a button to get the app, the link carries a short label saying which page and which button you came from, for example the home page. The App Store and Google Play use that label to tell us which page an install came from, in totals. It does not contain your name or any information about you. We use aggregate, de-identified website and app metrics (like visits, installs, and feature counts) to plan and measure our own advertising. We never sell your personal information, and we never use anything you store in Bearing Life for advertising.
Your choices. If your browser sends a Global Privacy Control signal, the Meta Pixel never loads, Google Analytics runs with ad personalization turned off, and the check-in's PostHog analytics never loads. On the pages that use these tools, the "Do Not Sell or Share My Personal Information" link in the footer saves your choice in that browser and stops the Meta Pixel and the check-in's PostHog analytics there for good; Google Analytics keeps running there with ad personalization turned off. You can also email us at the address in Section 14. These tools are not used on our invitation page (join) or our delete-account page.
13. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. If we make material changes to how we handle your personal information, we will notify you within the app or by email to the address associated with your account. The date at the top of this policy shows when it was last revised. Your continued use of Bearing Life after a change takes effect means you accept the updated policy.
14. Contact Us
If you have questions or concerns about this Privacy Policy, or if you wish to exercise any of your privacy rights, please contact us at:
P2 Reserve LLC
Email: info@trybearinglife.com
Website: trybearinglife.com
EEA / UK residents. If you are in the EEA, UK, or Switzerland, you also have the right to lodge a complaint with your local data protection authority (in the UK, the Information Commissioner's Office). Where we are required to appoint an Article 27 representative, we will publish their contact details on this page once the appointment is made.
15. The Quiz on Our Website
If you take the quiz on our website, your answers and the person you picked are saved only in your browser, on the device you used for the quiz, so you can pick up where you left off. They are not sent to us. If you come back more than 30 days later, the page clears them, and "Start over" clears them at any time. If you choose to join the waitlist from the quiz, the email address you enter is sent to us and handled as described in Section 12. The quiz page also uses the advertising tools described in Section 12.