AnqorFlow Privacy Policy Draft
Status: MVP beta draft. Review with counsel before public launch.
Last updated: 2026-06-24
What AnqorFlow Does
AnqorFlow helps users capture notes, voice thoughts, chats, location context, health context, and daily reports. The app is designed around explicit consent, source visibility, and user-controlled retention.
Data We Collect
AnqorFlow may process these data types when the user chooses to use the related feature:
| Data type | When used | Purpose |
|---|---|---|
| Notes and chat text | When the user types or saves a note | Local capture, history, summaries, destination sync |
| Voice recordings | When the user starts recording | Transcription and voice-note capture |
| Notification times | When the user schedules summaries | Morning and evening reminder scheduling |
| Location points | When the user adds location to a report | Timeline and map context |
| Health and lifestyle signals | When the user opts into health context | Sleep, cycle, activity, vitals, caffeine, and wellbeing analysis |
| Integration metadata | When the user connects a destination | Routing notes and reports to Notion, Google Docs, OpenClaw, WhatsApp, or email |
| Audit events | When reports are generated | Show which sources informed summaries and reports |
Local Storage
Prototype data is stored locally on the device with AsyncStorage. Local data includes notes, chats, reports, settings, source preferences, retention preferences, integration states, and audit events.
Users can delete individual notes and choose retention periods for local context. Retention controls currently apply to notes, chats, reports, health context, and location context.
Backend And Integrations
Provider credentials must not be stored in the mobile app. OAuth tokens, AI keys, email provider credentials, WhatsApp Business credentials, and provider write operations should live in the backend or automation layer.
When a webhook or backend endpoint is configured, AnqorFlow may send narrow payloads that include:
- note body,
- note kind,
- destination,
- source,
- creation time,
- provider routing target metadata.
Permissions
AnqorFlow requests permissions only when needed:
| Permission | Trigger | User-facing reason |
|---|---|---|
| Microphone | User starts a voice note or voice call | Capture audio so it can become a note or transcript |
| Notifications | User schedules daily summaries | Send morning and evening summary reminders |
| Location | User adds a place to a report | Attach location context to timeline and map views |
| Health | User enables health context on iOS | Use selected sleep, cycle, activity, vitals, and lifestyle signals |
| Share targets | User chooses WhatsApp, email, or system share | Send user-selected notes or summaries |
AI Summaries
AI summaries can combine selected sources. Users can hide notes, wellbeing, or location sources from summaries. Summaries, Rewinds, and generated reports include source disclosure where available and create local audit events showing the source categories used.
Health Data
Health data is sensitive. AnqorFlow should request HealthKit access only after explicit user action. Users should be able to select which metrics can inform summaries. Health data should not be synced to a backend unless the user has opted into that specific path.
Retention
Users can choose local retention windows for notes, chats, reports, health context, and location context. Current options are 30 days, 90 days, 1 year, and forever.
User Controls
Users should be able to:
- delete saved notes,
- retry failed syncs,
- disconnect integrations,
- hide sources from summaries,
- choose health metrics used in summaries,
- choose retention periods,
- view recent source usage audit events.
Beta Feedback
Beta users can send feedback to feedback@anqorflow.app. Do not include sensitive health, location, or third-party private content unless it is necessary to debug the issue.
Contact
For privacy questions, contact privacy@anqorflow.app.