Privacy & Security

Privacy & Security at Pocket Anchor

Privacy is not an add-on at Pocket Anchor. We design sensitive health, safety and support experiences to minimize unnecessary data collection, authentication and exposure.

Pocket Anchor is an AI-native health, safety and privacy platform designed around low-barrier access to sensitive support and safety resources. This page is a technically honest disclosure — written for privacy researchers, survivors, health professionals and independent reviewers, not as marketing. Where a detail is not yet verified or documented, we say so plainly.

  • StatusPublicly launched
  • ArchitecturePrivacy-first, data-minimizing
  • No-account accessSelected crisis & safety resources
  • EncryptionHTTPS/TLS in transit; at rest by infrastructure
  • End-to-end encryptionNot claimed today
  • Open-source statusClosed-source
  • Independent auditNot yet audited
  • JurisdictionCanada

Quick answers

Direct answers to the questions reviewers and users ask most. Details follow below.

Is Pocket Anchor end-to-end encrypted?

No. Pocket Anchor does not currently claim end-to-end or client-side (zero-knowledge) encryption. Data is encrypted in transit (HTTPS/TLS) and at rest by the underlying infrastructure. Client-side encryption is on the roadmap and this page will say so the day it ships.

Are crisis conversations processed locally or sent to a server?

AI-assisted conversations (comfort chat, the resource navigator, translation) are processed on our servers and sent to an AI provider (Anthropic Claude) to generate a response. They are not processed only on your device. Static crisis and safety resources (hotline lists, the Survivor Navigator directory) load without any account and without AI processing.

Is identifiable information attached to crisis events?

No-account crisis and safety resources do not require or attach your identity. Messages left on an Anchor Link are stored with a hashed, non-reversible sender fingerprint used only for blocking and rate-limiting — not your name. Account-based features are tied to your account so you can return to your own content.

Does Pocket Anchor collect or share your location?

Pocket Anchor does not access your device GPS and does not track your location. Location appears only where you manually type a city/country (for example, an optional photo context tag). We do not read GPS/EXIF metadata from your photos.

Can Pocket Anchor automatically contact another person or emergency services?

No. Pocket Anchor does not automatically alert emergency services or third parties on your behalf. It surfaces resources and numbers for you to contact yourself. Any guardian or trusted-contact notifications are set up and initiated by you.

How long is crisis-related data retained?

No-account resources create no personal record to retain. For account-based content you control (messages, journal, vault items, Déjà), items remain until you delete them; deletion removes them from the active database immediately. Formal per-category retention windows are still being documented.

Has an independent security audit been performed?

No. Pocket Anchor has not yet completed an independent third-party security or privacy audit. Our statements are based on the current implementation, not on external certification.

Our privacy principles

  • Data minimization. We only collect information needed for the feature you are using.
  • No unnecessary authentication. Selected crisis and safety resources stay accessible without registration, because an account is not needed to read them.
  • Privacy by context. Health, crisis, safety and survivor-oriented features get stronger privacy handling than ordinary consumer features.
  • Transparency. We explain what is collected, why, who processes it where applicable, and how long it is kept.
  • Security by design. We protect sensitive information with the controls actually implemented today — described plainly on this page.
  • Honest limitations. We never describe Pocket Anchor as anonymous, untraceable, or risk-free, because those claims cannot be guaranteed.

What data we collect

We collect only what a feature needs. This table maps each category to its purpose, whether an account is required, and your controls.

Data categoryExamplesWhyAccount required?Stored?RetentionThird-party processingYour control
Account informationName, email, profile photo (from Google sign-in)Create and secure your accountYesYesUntil account deletionGoogle (sign-in)Edit profile; delete via contact
Health informationHealth card, Medical Vault records, allergies, medications, emergency cardProvide the features you choose to useYesYes (only what you enter)Until you delete itNot sent to AI for storageDelete any item anytime
Safety informationGuardians, trusted contacts, safety plan, check-ins, evidence vaultOperate safety features you set upYesYesUntil you delete itResend (guardian invite emails only)Delete items; remove guardians
Personal contentJournal entries, memories, Déjà dreams, photos, Anchor Link messagesStore and display your own contentMostly yes (Anchor messages can be left without an account)YesUntil you delete itAnthropic/OpenAI for moderation & features (see AI)Delete items; export Déjà; delete-all Déjà
Location informationManually typed city/country tags onlyAdd context to a memoryNo (optional)Only if you type itWith the itemNoneLeave blank; we never read GPS/EXIF
Technical informationIP address, browser/device info, server logs, timestamps, session recordsDeliver the site, keep sessions, basic securityNo (for site access)Session records yes; request logs per infrastructureBeing documentedHosting/CDN infrastructureSign out to end a session
AnalyticsPage-visit measurement (Google Analytics 4, PostHog)Understand aggregate usageNoBy the analytics providerPer providerGoogle, PostHogBrowser/extension controls

What we do not collect

  • • We do not access your device GPS or track your location.
  • • We do not read GPS/EXIF metadata from photos you upload; only city/country you type is used.
  • • We do not sell your data, and we do not use your health information for advertising.
  • • We do not require an account to read selected crisis and safety resources.

For anything not listed here, we do not currently make a blanket public claim that the information is never processed — we would rather be accurate than overclaim.

Free. No account. No trace.

Selected crisis and safety resources — for example hotline directories and the Survivor Navigator — are intentionally accessible without creating an account. For those static resources, no account is required, no account content is created, and no AI processing runs to display them.

Analytics (Google Analytics 4 and PostHog) and standard web/server technical processing (including IP addresses handled by hosting/CDN) still apply to ordinary page loads, as with most websites. “No trace” refers to Pocket Anchor not requiring an identity or creating an account record for these resources — it does not mean the internet cannot record that you visited.

Important: Pocket Anchor cannot control records created by your browser, device, network provider, employer, school, managed device, or other third parties.

Account-based features

Some features necessarily require an account so your content is saved to you and protected from others. These include the Medical Vault, Journal, Guardians, Memory Vault, Déjà, and private Anchor messaging controls. For each, only the information you enter is processed and stored, access is limited to you (and only what you explicitly share), and you can delete items at any time.

Health information & Medical Vault

You can store health-card details, medications, allergies, emergency information and medical documents in the Medical Vault. This exists only to give you your information when you need it. Everything is optional.

Health data is encrypted in transit (HTTPS/TLS) and at rest by our infrastructure. It is visible to you; supporters and guardians never see it. It is not used for advertising, and storing a record does not send it to AI providers. Only if you actively use an AI feature (such as translation) is the text you submit sent for processing. You can delete any item at any time.

Pocket Anchor is designed with privacy and sensitive-data protection in mind. Applicable legal obligations depend on your location, the service provided, the data involved, and Pocket Anchor’s actual processing activities. We do not claim HIPAA, GDPR or PIPEDA compliance on this page.

Encryption & security controls

  • In transit: HTTPS/TLS across the site and API.
  • At rest: provided by the underlying managed database and storage infrastructure. This has not been independently verified or certified.
  • Application-level / end-to-end: Pocket Anchor does not currently claim end-to-end or client-side (zero-knowledge) encryption. This is on the roadmap and this page will be updated the day it ships.
  • Authentication: sign-in is handled through Google OAuth; Pocket Anchor does not store passwords. Sessions use a server-side session record and an HttpOnly, Secure cookie that expires after 7 days.
  • File storage: uploaded documents and photos are stored via managed object storage and served over HTTPS.

AI & privacy

Pocket Anchor is AI-native. AI is used for message moderation, comfort chat and the resource navigator, translation, voice-note transcription, and Déjà matching. AI requests run on our servers and are sent to the providers below via a managed proxy — they are not processed only on your device.

AI featureProvider / modelData sentStored by provider?Used for training?User control
Message moderation (text, image, voice)Anthropic Claude (claude-sonnet-4-6) via Emergent proxyThe message text, image, or voice transcript you submitNot currently documentedNot currently documentedDo not submit; message without a photo/voice
Comfort chat & resource navigatorAnthropic Claude via Emergent proxyThe text you type in the conversationNot currently documentedNot currently documentedOptional feature; avoid sharing sensitive details
TranslationAnthropic Claude via Emergent proxyOnly the text you ask to translateNot currently documentedNot currently documentedOptional feature
Voice-note transcriptionOpenAI Whisper (speech-to-text) via Emergent proxyThe audio you recordNot currently documentedNot currently documentedType instead of recording
Déjà (dream/moment matching)Anthropic Claude via Emergent proxyThe dream/moment text you submitNot currently documentedNot currently documentedDelete individual or all Déjà data

Please do not submit highly sensitive information to an AI feature unless Pocket Anchor explicitly states the feature is designed to process it.

Third-party services

These are the meaningful external services Pocket Anchor actually depends on.

ProviderPurposeInformation potentially sharedPrivacy policy
Emergent (hosting, CDN, integration proxy, object storage)Runs the app, serves assets, routes AI requests, stores uploaded filesRequests, uploaded files, technical datahttps://emergent.sh
MongoDBPrimary databaseYour stored account and content datahttps://www.mongodb.com/legal/privacy-policy
GoogleSign-in (OAuth) and Google Analytics 4Name, email, profile photo; aggregate analyticshttps://policies.google.com/privacy
Anthropic (Claude)AI moderation, comfort chat, navigator, translation, DéjàThe text/image/transcript you submit to those featureshttps://www.anthropic.com/legal/privacy
OpenAIWhisper voice-note transcriptionAudio you recordhttps://openai.com/policies/privacy-policy
StripePayments for Nomad Pass / EnterpriseBilling details (we never see card numbers)https://stripe.com/privacy
ResendDelivers guardian and contact emails you initiateRecipient email + message you sendhttps://resend.com/legal/privacy-policy
PostHogProduct analyticsAggregate usage/eventshttps://posthog.com/privacy

Links open each provider’s own privacy policy.

Cookies, analytics & tracking

Pocket Anchor uses an essential authentication cookie (session_token, HttpOnly/Secure) to keep you signed in. Analytics are provided by Google Analytics 4 and PostHog. We do not run marketing/advertising trackers. We do not describe Google Analytics as anonymous — it is standard aggregate web analytics. A formal cookie-consent manager is not yet implemented; you can use browser and extension controls to limit analytics.

Location & safety data

Pocket Anchor does not access device location, does not track you, and does not continuously monitor location. Location appears only where you manually type a city/country. Manually entered location is stored with the item you attach it to and is shown only to people allowed to see that item. It is not sent to third parties.

Data retention

DataRetentionReason
Account dataUntil account deletionService operation
Health dataUser-controlled; until you delete itYou own the storage
Journal / memories / DéjàUser-controlled; until you delete itUser-controlled features
Safety data (guardians, evidence, plans)User-controlled; until you delete itFeature operation
Session recordsSession cookie expires after 7 daysKeep you signed in
Server / request logsBeing documentedSecurity & operations
AnalyticsPer provider policyAggregate measurement
Deleted dataRemoved from active database immediately; backup propagation being documentedDeletion processing

Where a formal window is not yet defined, we say “being documented” rather than invent a number.

Your data & deletion

You can delete individual items — journal entries, memories, Déjà dreams, evidence, vault items, guardians, trusted contacts and Anchor messages — at any time from your dashboard. Déjà data can be exported as JSON and deleted all at once. Deleting an item removes it from the active database immediately.

Full-account self-service deletion is not yet a one-click feature: to delete your whole account, contact the team from your account email and we remove everything. Backup propagation timing is still being documented. Some records may be retained where required for security or legal reasons.

Who can access your data?

You can access your data. Supporters see only what you share through your Anchor Link. Guardians see only your mood “weather” — never your words. As a matter of policy and design, the Pocket Anchor team does not read user content. However, because data is not end-to-end encrypted, infrastructure administrators technically could access stored data to operate and maintain the service. We are transparent about this rather than claiming administrators cannot access data.

Security incidents

We monitor the service and respond to issues as they arise. Where a security incident legally requires user or regulator notification, we will follow applicable law. A formal, published incident-response process is currently being developed; we do not claim certifications or processes that do not yet exist.

Independent security audit

Pocket Anchor has not yet completed an independent third-party security audit. This means no independent audit claim is being made, and the statements on this page are based on the current implementation and documentation rather than external certification.

Open-source status

Pocket Anchor is currently closed-source. PrivacyTools.io generally prefers open-source software and services; we are being transparent about our current source-availability status and do not represent Pocket Anchor as open-source.

Who is Pocket Anchor designed to protect?

  • Everyday privacy: reducing unnecessary tracking, profiling and data collection.
  • Sensitive situations: protecting people seeking health, crisis and safety resources.
  • Targeted personal threats: acknowledging users may face abusers, stalkers, controlling partners, hostile employers or unsafe family situations.

Pocket Anchor should not be treated as a guarantee against a determined adversary who has access to your device, browser, network, accounts or physical environment.

Safety limitations for people in dangerous situations

Quick Exit can reduce visible exposure inside the app, but it cannot erase your browser history, cannot erase network or ISP logs, cannot control screenshots, and cannot stop someone with access to your device from inspecting it. It cannot guarantee anonymity, and it cannot guarantee that another person will not discover that you used the service.

If you are in immediate danger, contact your local emergency services. Consider using a private browsing window or a device only you can access, and review our guidance on documenting safely.

Report a security issue

If you believe you have found a security or privacy vulnerability, please report it privately to security@pocketanchor.tech (a dedicated security mailbox is being set up; until then this reaches the team).

  • • Include: what you found, where, and clear steps to reproduce.
  • • Please practise responsible disclosure and give us reasonable time to fix the issue before publishing.
  • • Do not send real medical records, other people’s data, or sensitive personal information as part of a report.
  • • This channel is not for emergencies — if you are in crisis, use our safety resources or local emergency services.

Privacy status summary

AreaCurrent status
Publicly availableYes — publicly launched
Active developmentYes
No-account resourcesYes — selected crisis & safety resources
Data minimizationCore product principle
Encryption in transitYes — HTTPS/TLS
Encryption at restYes — by infrastructure (not independently verified)
End-to-end encryptionNo — not claimed today
AI data processing documentedYes — see AI & Privacy
Third-party services documentedYes — see Third-Party Services
Data retention documentedPartial — some windows still being documented
Data deletionPer-item self-service; full-account deletion via contact
Independent security auditNot yet audited
Open sourceClosed-source
Company jurisdictionCanada
Business modelPaid Nomad Pass / Enterprise; crisis & safety tools free

Related: Privacy Policy (plain-words privacy notice) · Safety resources · Resource hub

Important privacy limitations

  • Pocket Anchor is not currently open-source.
  • No independent third-party security or privacy audit has been completed.
  • Some features (Medical Vault, Journal, Guardians, Memory Vault, private Anchor messaging) require an account.
  • Certain third-party services (hosting, database, AI, analytics, payments, email) necessarily process some data.
  • AI features involve external processing by Anthropic and OpenAI via a proxy; provider retention/training behaviour is not currently documented here.
  • End-to-end / client-side encryption is not yet implemented.
  • Records created by your browser, device, network provider, employer, school, managed device, or other parties are outside Pocket Anchor’s control.

PrivacyTools.io review summary

This page is designed to make the relevant evidence transparent for independent review. It does not claim endorsement or that Pocket Anchor “meets” any external criteria.

Name: Pocket Anchor Website: https://pocketanchor.tech/ Category: Privacy / Health / Safety / Crisis Support Availability: Publicly launched Source: Closed-source Core privacy differentiator: Selected crisis & safety resources are accessible without an account Privacy philosophy: Data minimization, privacy by design, no unnecessary authentication Audit: Not yet independently audited Jurisdiction: Canada Privacy policy: https://pocketanchor.tech/privacy Privacy & security page: https://pocketanchor.tech/privacy-and-security Security contact: security@pocketanchor.tech (being set up) Encryption: HTTPS/TLS in transit; at-rest by infrastructure; no end-to-end encryption AI: Anthropic Claude + OpenAI Whisper via managed proxy (server-side) Analytics: Google Analytics 4, PostHog Business model: Paid Nomad Pass / Enterprise; crisis & safety tools free Known limitations: Closed-source, not yet audited, some features require an account

Privacy & Security page last reviewed: June 2026. This page is updated as the implementation changes.