Skip to main content
OARManager home Privacy policy

Your days are personal. Your data should be treated that way.

How OARManager collects, uses, shares, retains, and deletes account, planning, journal, wellness, integration, and diagnostic data.

Effective and last updated July 25, 2026 support@oarmanager.com

OARManager does not sell personal information, run third-party advertising, or use your activity for cross-company tracking.

1. Scope and who we are

This policy applies to the OARManager website, web application, iPhone app, Android app, and related support communications (together, the “Service”). “OARManager” means the operator of the OARManager Service. Questions and privacy requests can be sent to support@oarmanager.com.

This policy describes the Service as it exists today. Optional features only send data to the providers named below when those features are configured and you choose to use them.

2. Information we collect

The information collected depends on which parts of OARManager you use.

  • Account and profile information: email address, optional name, internal account identifiers, workspace memberships and roles, email-verification status, password hashes, passkey metadata, and security settings. OARManager does not store your plain-text password.
  • Planning and productivity content: tasks, notes, subtasks, dates, reminders, recurrence rules, tags, categories, saved views, schedules, daily priorities, gratitude, highlights, and other planner entries.
  • Journal and wellness-like content: journal text and selected photos; sleep and meal entries; symptoms or habits you choose to log; workouts, meditation, breathing, and timer sessions; day ratings; and birthdays you add. These fields are optional and are not medical records.
  • Calendar and notification information: OARManager calendar events, public calendar-feed settings, browser push subscriptions, notification preferences, and delivery history.
  • Workspace and business features: invitations, membership activity, audit events, receipt images and extracted receipt fields, reimbursements, accounting mappings and exports, and AI suggestions when those features are used.
  • Connected-service information: encrypted authorization credentials, provider account identifiers, connection status, and data needed to provide a connection you request, such as an account email, selected Google Calendar event content and sync history, or QuickBooks references.
  • Security and technical information: IP address, browser or device user agent, session timestamps, sign-in and account-security events, request metadata, crash reports, performance traces, and error details when diagnostic reporting is enabled.
  • Device-local information: theme, font, sound and feature preferences; authentication state; cached content; and task changes queued while the web app or mobile app is offline. Some of this stays on your device until you clear site/app data or uninstall.
  • Support communications: the messages and attachments you send, the account email involved, and information needed to investigate and answer your request.

3. Where information comes from

Most information comes directly from you. We also receive information automatically from your browser or device when the Service is used, from another workspace member who invites or collaborates with you, and from a connected provider when you authorize an integration.

If you submit a receipt for extraction, the receipt image and filename may be sent to the configured extraction provider. If you connect a calendar or accounting account, the provider returns the identifiers, tokens, and records needed for that feature.

4. How we use information

Where privacy law requires a legal basis, processing is generally necessary to provide the Service under our agreement with you, based on legitimate interests in security and reliability, based on your consent for optional device permissions or connected services, or required by law. You can withdraw optional permissions or disconnect integrations, although that does not affect earlier lawful processing.

  • Provide, synchronize, personalize, and maintain the Service across your devices and workspaces.
  • Authenticate accounts, operate passkeys and sessions, recover access, and protect the Service from fraud, abuse, and unauthorized access.
  • Send verification, password-reset, reminder, invitation, security, and support messages you request or that are necessary to operate your account.
  • Run optional calendar, notification, receipt-extraction, accounting, import, export, and collaboration features.
  • Troubleshoot failures, measure reliability, maintain audit trails, and improve performance and usability.
  • Comply with law, enforce the Terms of Service, and establish or defend legal claims.

5. Service providers and disclosures

We disclose information only as needed to operate a feature, follow your instructions, protect the Service, or meet legal obligations. Current code supports the following providers; a provider receives data only when the relevant service is deployed or feature is enabled:

  • Vercel for application hosting and private object storage, including receipt files when receipt storage is enabled.
  • Neon or another configured PostgreSQL host for application databases.
  • Resend for account, security, reminder, invitation, and other transactional email.
  • Sentry, when enabled, for exception, route, crash, and performance diagnostics. Diagnostic events may include exception details, route and timing data, app version, and device context. Server and browser reporting is configured to strip request bodies, headers, query strings, cookies, user identity, and IP address before sending.
  • Upstash Redis, when configured, for abuse-prevention rate limits associated with authentication or other protected endpoints.
  • Google, only when you connect Google Calendar, for OAuth account details and events from the calendars you explicitly select for import, export, or two-way sync.
  • Intuit, only when you connect QuickBooks Online, for accounting references, draft expenses, receipts, and exports you direct OARManager to send.
  • Anthropic, only when AI receipt extraction is enabled and you submit a receipt, for the receipt image, filename, and extraction request.
  • Apple, browser vendors, and push-delivery infrastructure when you enable app or browser notifications.

Workspace content is visible to other members according to their role and the workspace’s permissions. We may also disclose information in response to valid legal process, to protect people or the Service, or as part of a merger, financing, reorganization, or sale, subject to appropriate notice and safeguards.

We do not sell personal information and do not share it for targeted advertising or cross-context behavioral advertising.

6. Retention and account deletion

Account content is generally retained while your account is active so the Service can provide your history, sync, exports, and collaboration. Security events, delivery records, webhook receipts, audit trails, and backups may have different limited retention periods based on security, reliability, legal, and recovery needs.

You can start deletion in the iPhone app, Android app, or web Settings, or follow the public account-deletion instructions. Deletion ends account access and removes data tied exclusively to your account from active systems. Private receipt objects owned by a workspace being deleted are scheduled for removal. Tokens and active sessions are revoked.

Deletion is blocked when a workspace you own still has another active member. Transfer ownership to one of those active members first so one person cannot delete everyone else’s shared data. A workspace with no other active member does not create this block. Content you contributed to somebody else’s workspace may remain for that workspace but can be retained without an active link to your deleted account.

Limited security, audit, webhook, transactional, legal, or backup records may remain for a reasonable period and may be redacted or de-identified. Copies already sent to a connected provider are governed by that provider and may need to be deleted there. Disconnecting a provider or deleting OARManager does not automatically erase the provider’s own records.

7. Your choices and privacy rights

Depending on where you live, you may also complain to your local data-protection authority. We will not discriminate against you for exercising an applicable privacy right.

  • Review and change profile, security, notification, appearance, and integration settings in the Service.
  • Export task and journal data using the available backup, CSV, JSON, Markdown, HTML, or calendar tools.
  • Disconnect optional integrations and turn off device or browser notification permissions.
  • Request access, correction, deletion, restriction, portability, or an objection where those rights apply.
  • Contact support@oarmanager.com to exercise a privacy right or appeal a response. We may need to verify your identity and authority before acting.

8. Security

OARManager uses measures such as HTTPS, password hashing, encrypted integration credentials, short-lived or revocable tokens, Keychain storage in the iPhone app, Android Keystore-backed credential storage in the Android app, role-based workspace access, and restricted private-file access. No system is perfectly secure, so protect your password and devices and contact us promptly if you suspect unauthorized access.

Do not send passwords, passkeys, access tokens, private journal entries, health details, or full receipt images in an ordinary support email unless we specifically ask for a safe transfer method. Report a suspected security issue to support@oarmanager.com.

9. International processing

OARManager and its providers may process information in the United States and other countries where they operate. Those countries may have different data-protection laws. Where required, we rely on provider contractual safeguards or another lawful transfer mechanism.

10. Children

The Service is not directed to children under 13, and we do not knowingly collect personal information from a child under 13. If you believe a child has provided information without appropriate permission, contact support@oarmanager.com so it can be reviewed and deleted. Additional age or parental-consent rules may apply where you live.

11. Changes and contact

We may update this policy as the Service changes. The updated date will appear at the top, and material changes may also be announced in the Service or by email. Questions, requests, and complaints can be sent to support@oarmanager.com.

Still have a question?

Talk to OARManager support.

Do not include a password, passkey, reset link, or access token in your message.

Email support