Security & Breach Notification

1.The short version

This page describes the safeguards Ashlar Enterprises LLC (“Ashlar”, “we”, “us”) uses to protect LifeAnchor today. We may change specific measures over time as we improve them, but we will not reduce the overall level of protection described here without updating this page. It supplements our Privacy Policy and Consumer Health Data Privacy Policy.

2.How we protect your information

Encrypted connections. LifeAnchor is served only over HTTPS (TLS). We use HTTP Strict Transport Security (HSTS), so browsers refuse to connect without encryption, and strict security headers that limit what a web page is allowed to load and do.

Household separation enforced by the database. Every table holding user data has row-level security: the database itself decides which rows a signed-in person may read or change, rather than relying only on application code. Automated “probe” tests impersonate real users and try to read across households, to verify that one household cannot see another’s data. Access to health information is decided by the database per person and per category, and sensitive health categories require an explicit grant.

Additional encryption for the most sensitive items. Our database provider applies its own storage-level encryption. In addition, we separately encrypt the following categories in our application before they are stored:

• Vital Documents Vault documents (each with its own key);
• identity numbers on profiles (such as passport, driver’s licence and DoD ID numbers, and the last 4 digits of a Social Security number);
• bank routing and account numbers;
• email account credentials and access tokens;
• calendar and contacts credentials and access tokens;
• health-device connection tokens (such as Oura, Dexcom and Tidepool);
• AI provider API keys;
• health-goal notes and attachments; and
• medication label photos.

Other information is protected by the provider’s storage-level encryption and the access controls described here, but is not separately encrypted in the application.

Per-document keys and crypto-shredding. Each Vault document has its own encryption key. Deleting a document destroys its key, so any remaining encrypted copy can no longer be read.

Tamper-evident audit log. Access to health information is recorded in an append-only audit log in which each entry is cryptographically chained to the one before, so that altering or removing past entries can be detected. We keep this log for at least 6 years.

AI call logging. Every AI request is logged by a fingerprint of the prompt — not its content — so we can investigate misuse without keeping a copy of what was asked.

Controlled staff access. Ashlar staff use controlled support tools rather than direct access to your data. Bulk export of a household’s data is restricted to super-administrators, requires a written justification, and is logged.

Emergency access is limited and logged. Emergency (“break-glass”) access to a health emergency card is limited to 60 minutes and is logged.

Session limits. Sign-in sessions end after a period of inactivity and after a maximum length, so an unattended device does not stay signed in indefinitely.

Two-step verification, where enabled. Where it is switched on, adult accounts must enter a 6-digit code sent by email when signing in, unless the device has been remembered. A device you mark “remember this device” is remembered for 30 days; otherwise, for 12 hours. Child accounts, which are created and managed by a parent, are not asked for codes.

Rate limiting. We limit how often sign-up, AI and other sensitive features can be called, to slow down automated abuse.

Bot protection, where enabled. Sign-up may be protected by Cloudflare Turnstile.

No bank or store passwords. We never ask for your online-banking password, and we do not connect to or store passwords for retailer accounts. Bank information comes only from statements you import or details you enter.

Nothing we don’t need. LifeAnchor does not collect your device’s GPS location, and we do not use advertising or tracking tools. Device biometric locks (such as fingerprint or face unlock) happen on your device; LifeAnchor never receives fingerprint or face data.

3.What we don’t promise

Honesty about limits is part of security:

• LifeAnchor is not end-to-end encrypted. Our servers process your information in readable form in order to provide the service — for example, to show it to the household members you allow, to build reports, and to send requests to the AI provider you connect.
• Not every item is separately encrypted. Only the categories listed above receive application-level encryption in addition to storage-level encryption.
• Connected services are outside our control. When you connect an email account, health device or AI provider, that provider’s own security applies to the data they hold. See Service Providers & Integrations.
• No system is perfectly secure. We work to prevent, detect and respond to security incidents, but we cannot guarantee that unauthorized access will never happen.

4.Your part

Most account takeovers start outside the service. You can help a great deal:

• Use a strong, unique password for LifeAnchor that you don’t use anywhere else. A password manager makes this easy.
• Protect your email account. LifeAnchor can send sign-in links and verification codes to your email, so anyone who controls your email can get into LifeAnchor. Turn on your email provider’s own two-step verification.
• Sign out on shared devices, and close the browser when you finish.
• Use “remember this device” only on a device that is yours and that others can’t use.
• Keep household roles tight. Give administrator rights only to people who need them, review who can see which modules, and remove members who no longer belong in the household.
• Be wary of messages asking for codes. We will never ask you to tell us a verification code or your password.
• Tell us quickly if you think someone else has accessed your account.

5.If a breach happens

LifeAnchor is a direct-to-consumer service and is not a HIPAA covered entity or business associate. We follow the FTC Health Breach Notification Rule for health information, as well as the state data-breach notification laws that apply.

If we discover a breach of security involving unsecured, identifiable health information in LifeAnchor, we will:

• notify each affected person without unreasonable delay, and no later than 60 calendar days after we discover the breach;
• notify the Federal Trade Commission, as and when the Rule requires; and
• where 500 or more residents of a single state are affected, also notify prominent media outlets serving that state.

For breaches involving other personal information, we will give the notices that applicable state laws require, within the timeframes they set, including notices to state authorities where required.

Our notice will explain, as far as we know: what happened and when; what kinds of information were involved; what you can do to protect yourself; what we are doing in response; and how to contact us.

How we will contact you. We will send notice to the email address on your account and show it in the app. If we do not have working contact details for enough of the people affected, we will use other means the law allows, such as a notice on our website. For a child member, we will notify the parent or guardian who manages the household. Please keep your email address current.

6.Reporting a security problem

If you believe you have found a security vulnerability in LifeAnchor, please tell us. Email [email protected] with the subject line “Security”, and include:

• a description of the problem and why you think it is a vulnerability;
• the page, feature or address affected;
• step-by-step instructions to reproduce it, and any proof-of-concept;
• what an attacker could do with it; and
• how we can reach you for follow-up.

We aim to acknowledge your report within 5 business days, and to keep you informed as we investigate and fix it. Please give us a reasonable time to fix the issue before you share it publicly.

Good-faith research. We will not pursue legal action against you, or ask law enforcement to, for security research that is carried out in good faith and that:

• uses only accounts you own, or accounts whose owners have given you permission;
• does not access, change, copy or delete other people’s data — if you encounter someone else’s information, stop, do not keep it, and tell us;
• respects user privacy and does not degrade the service for others (no denial-of-service testing, spam or social engineering of our staff or users); and
• complies with our Acceptable Use Policy apart from the testing itself, and with applicable law.

We do not offer a monetary reward or bug bounty, but we are grateful for every report.

7.Contact us

For security questions, to report a vulnerability, or to tell us you think your account has been accessed by someone else:

Ashlar Enterprises LLC · 9905 S Pennsylvania Ave, Suite A, Oklahoma City, OK 73159 · (405) 957-9360 · [email protected]