Legal

Privacy Policy

This policy explains how Samuel Elgozi, operating as Reaper ("Reaper", "we", or "us"), handles personal information through reaper.io and Reaper products.

Information we handle

  • Account information. Our authentication provider gives us your account identifier, email address, name, profile picture, and authentication information when you sign in to reaper.io.
  • Access requests. We store the product requested, your message, its review status, and the time of the request.
  • Community information. We store the profile name, feature requests, issues, comments, votes, and attachments you choose to submit. Your submissions, display name, and profile picture are visible to members with the relevant product access. Private issues are visible only to their author and Reaper staff.
  • Product activity. We store product access, downloads, and update checks. These records can include your account identifier, a randomly generated installation identifier, product, version, platform, architecture, and time. The installation identifier is stored in the app's preferences and sent with update checks. We use these records to understand active installations and installed versions.
  • Monitor trials and license keys. Monitor makes an installation hash on your Mac from the Mac's hardware UUID and your macOS user ID. Monitor sends this hash, and any license key that you enter, with each access and update check. Monitor does not send the hardware UUID or the user ID. We keep the hash with your trial, so the trial cannot start again. We keep the hash with each license key activation, to limit a key to three Macs. We keep each license key with the account that has it. We keep trial records after the trial ends. When you replace a key, we delete its activations. We keep trials from earlier versions of Monitor with your account.
  • Purchases. Creem processes purchases as our Merchant of Record. We send your account email to Creem to prepare checkout. We store checkout terms, order and transaction identifiers, payment-event identifiers, prices, amounts paid, currency, discounts, taxes, and purchase dates. Refund records include amounts, reasons, dates, and status. These records, product access, and the license key a purchase creates are linked to your Reaper account. Reaper does not receive complete payment-card details.
  • Support. We store the messages, diagnostics, and attachments you send when you ask for help or request a refund.
  • Service information. Our hosting providers process normal request information, such as IP addresses and request logs, to deliver and secure the services.

Information you choose to provide

Providing personal information to Reaper is voluntary. Account and authentication information is needed to sign in to reaper.io, obtain account-restricted product access and downloads, or make a purchase. Monitor's trial and license keys do not require you to sign in inside Monitor. Community contributions and support requests are optional. Without the information needed to identify or investigate a request, we may be unable to handle it.

Inspected traffic stays local

Reaper records the network traffic you choose to inspect on the machine where Reaper is installed. Captured traffic is not sent to Reaper's servers.

Monitor inspection stays local

Reaper Monitor inspects processes and resources on the Mac where it is installed. The inspected process and resource data is not sent to Reaper's servers. Trial, license key, download, and update checks still contact Reaper services.

Reaper Usage and provider data

Reaper Usage uses provider tools and sign-ins on your Mac. Codex communicates through the local Codex app-server. Claude usage requests go through Claude Code. Grok usage requests use the credential already stored by the Grok CLI and go to Grok. Token history reads the session logs those tools write on your Mac. To price token history, Usage downloads the public model catalog from models.dev, a third-party site, at launch and once a day. That request carries no account, log, or usage data. Reaper servers do not receive provider credentials or usage readings.

Why we use information

We use personal information to authenticate accounts, issue and check trials and license keys, review access requests, fulfill purchases, provide downloads and updates, operate the community, answer support and refund requests, secure the services, understand product adoption, and comply with law. Where applicable, we process account, purchase, and access information to provide the requested service. We rely on legitimate interests to secure and improve the services, and on legal obligations to keep required records and respond to lawful requests.

Service providers

We use service providers for authentication, hosting, databases, file storage, email delivery, commerce, and website analytics. These providers process personal information as needed to provide those services and may do so in countries outside your own. Creem processes purchase information as Merchant of Record under its Privacy Policy. We do not sell personal information or use it for advertising.

Browser storage

The site uses local browser storage to keep you signed in, protect the sign-in flow, and remember where to return afterward. We do not use advertising or analytics cookies.

Website analytics

We use Seline to measure visits to our public pages and understand which pages visitors view. This includes page addresses, referral sources, country, and browser and device information. Seline processes IP addresses and browser information to estimate daily unique visitors without cookies. We do not send names, email addresses, or account identifiers to Seline. See Seline's data practices.

Retention

We keep information while it is needed to operate your account, product access, downloads, updates, and community activity. Purchase and refund records may remain after an account-deletion request to establish license rights, handle refunds or disputes, and meet legal recordkeeping obligations. We may retain other information to resolve security, legal, or support matters. We delete or anonymize information when it is no longer needed.

Your choices and rights

You may ask to access, correct, or delete your personal information. Depending on where you live, you may also have rights to object, restrict processing, receive a portable copy, or complain to a data protection authority. Contact us to make a request.

Security

We use reasonable technical and organizational measures to protect personal information. No system can guarantee complete security.

Changes and contact

We may update this policy when Reaper's products or data practices change. We will publish the new date on this page. Send privacy questions and requests to support@reaper.io.