Privacy Policy

Overview

Hark is operated by Ryan Vogel. This policy explains the information Hark processes to deliver notifications, approvals, Live Activities, on-call pages, team features and signed-in web apps through the website, API, CLI, MCP server and iOS app. Hark does not sell personal information or use it for targeted advertising.

Information we process

• Your Google or Apple account identifier, name, email address, and profile image when provided by the sign-in service. Apple may provide a private relay email address.
• Encrypted Apple refresh tokens used only to revoke Sign in with Apple authorization when you delete your account.
• Service settings you create, including titles, image URLs, destination URLs, secret webhook-token hashes, and encrypted webhook tokens.
• Webhook and agent notification content such as titles, bodies, summaries, project names, images, destinations, idempotency keys, timestamps, read state, and delivery results.
• Device information needed for delivery, including Expo and APNs push tokens, device name, platform, and last registration time.
• Agent access-token names, scopes, identifying prefixes, hashes, expiry and usage times. Plaintext agent tokens are shown once and are not stored by Hark.
• Approval and reply prompts, choices, expiry, response text or decision, requesting token identity, responding device, and response timestamps.
• Live Activity task titles, status text, optional detail and progress, expiry and update history, requesting token identity, and encrypted ActivityKit delivery tokens. Private mode replaces task content with generic text on the Lock Screen but does not remove the task content from Hark's encrypted network and account-scoped processing.
• Teams you create or join: the team name, members and their roles, invite codes (stored as hashes), the email address an invite was sent to, who invited whom, and when people joined or left. Other members of a team can see your name, email address and profile image.
• On-call information: rotation schedules, your time zone, overrides, escalation steps, pages and their content, who was notified, acknowledgements, escalations and resolutions, and your paging preferences, including whether your iPhone allows Critical Alerts.
• Web apps you add or open in Hark: the app's name, address and icon, which team it belongs to, and your sign-in approval. When you approve sign-in, Hark gives that site a short-lived signed pass with an identifier made only for that site, your team and role for team apps, and your name and email only if you choose to share them. The site receives that information under its own privacy terms, not Hark's.
• Agent clients connected through the MCP server or the CLI: the client's name, the permissions you granted, and hashed access and refresh tokens.
• Subscription status and billing identifiers when you or your team choose a paid plan. Payment-card details are collected and handled by Stripe, not stored by Hark.
• Limited technical logs used to secure, operate, and troubleshoot the service.
• Product analytics such as page and app-screen visits, feature lifecycle events, first-touch campaign labels, referring and outbound hostnames, app version, coarse outcomes, and related account, service, device, anonymous-install, or session identifiers. Hark never puts notification content, summaries, project names, prompts, replies, tokens, full URLs, IP addresses, email addresses, or user-agent strings in analytics.

How we use information

We use this information to authenticate your account, create and secure webhook endpoints, deliver notifications, show delivery activity, prevent duplicate or abusive requests, deliver requested interactions and return your response to the authorized agent, start and update Live Activities you authorize, run teams and on-call rotations, route and escalate pages, sign you in to web apps you approve, bill for paid plans, provide support, and maintain the reliability and security of Hark.

Service providers

Hark relies on Google and Apple for authentication, Expo and Apple for push delivery and app distribution, Autumn and Stripe for billing, Amazon Web Services for hosting the API and database, Cloudflare for DNS, encrypted connections and traffic protection, and Inbound for support email. These providers process information only as needed to provide their services and under their own privacy terms.

Retention and deletion

We retain account and service data while your account is active. Webhook and agent notification content — including titles, bodies, summaries, projects, and read state — persists in your inbox and is not expired on a schedule; it is removed when your account is deleted. You can permanently delete your account inside the Hark app. Deletion removes your services, devices, projects, notifications, activity, team memberships and web-app approvals from the active database; teams you own are handed to another admin or deleted. For accounts using Apple, Hark first asks Apple to revoke stored authorization grants; deletion stops and reports an error if that revocation cannot be confirmed. Limited backup copies may remain temporarily until rotated.

Security and your choices

Webhook URLs contain secret tokens and should be treated like passwords. You can rotate a webhook token or revoke a scoped agent token from the dashboard if it is exposed. Device responses require the signed-in account and a registered device identity. Hark uses access controls and encrypted network connections, but no online service can guarantee absolute security.

Children

Hark is not directed to children under 13, and we do not knowingly collect personal information from children under 13.

Contact

Questions or privacy requests can be sent to [email protected].