Privacy

Usage measurement and local comparison

The application records an inference ID, UTC time, environment, model, product revision, account ID when signed in, server outcome, duration, partial-context status and provider token counts. Estimated API cost is calculated using a documented tariff. No PR identifiers, code, report text or free-text notes are stored in these records. Records older than 90 days are deleted on subsequent inference admission; account deletion also removes linked usage records.

Signed-in reviewers can explicitly submit a usefulness choice and action choice for their own completed production review. These are user reports, not independent verification. Reports and verification files opened on Compare reviews are read locally in tab memory, never uploaded or saved. Reloading clears the comparison. The guest counter stores the UTC day/month and review counts in local storage.

Who operates this product

Release Engineer is built and operated by Ozan Kenan Güngör in Ankara, Türkiye. It is an independent, self-funded project in early beta. No legal company has been incorporated or registered.

What happens when you analyze a PR

We send the submitted URL to our server, retrieve public pull-request metadata and changed-file patches from GitHub, and send a bounded selection of those contents to Anthropic’s Claude API to produce your review. Submit only public pull requests you are comfortable having processed this way.

Operational usage evidence

When a valid, configured analysis starts, the server records structured operational events in hosting logs: start, success or failure; timestamp; environment; product commit when available; duration; file counts and partial-context status on success; or a high-level error code on failure. A random analysis ID links events for one attempt and helps deduplicate exported logs. It is not a user or session identifier and is never stored in a cookie.

These application events do not contain the PR URL, repository or owner, patches, descriptions, reports, model output, emails, user identity, IP addresses, request headers or secrets. Hosting providers may separately record request metadata under their own policies. Operational events are retained according to the hosting plan; selected event records may be preserved privately to substantiate a dated aggregate analysis count. Such counts are not user counts.

Storage and providers

The application does not persist submitted PR contents or review reports. They are held in memory while processing and displayed in your browser. Optional accounts use Clerk for identity, verification, passwords, recovery and session cookies, and Neon for account IDs, daily and monthly review usage and subscription state. There are no application advertising trackers. Our hosting provider, GitHub and Anthropic may process request metadata or contents under their own policies; this application does not control their retention.

Clerk may also store its public instance configuration and security state in browser storage, including for signed-out visitors while its sign-in SDK initializes. This is separate from report or verification-note storage; those notes remain in page memory and local downloads.

Anthropic privacy policy · GitHub privacy statement · Vercel privacy policy

Checkout preview

The Pricing page offers an optional Paddle sandbox checkout. Paddle’s checkout code is loaded when you select Preview checkout, not when you open the page. Paddle then receives connection metadata and any email, address or test payment details you enter in its checkout, under its own privacy and retention policies. Use test cards only. No PR contents or review reports are passed to Paddle.

Sandbox checkout does not collect real payment or grant production Pro access. An account checkout stores only the account ID, transaction ID, subscription and customer IDs, environment, status and billing-period dates. Card and address details remain with Paddle. Browser callbacks never grant access. Paddle may retain sandbox records in the operator’s Paddle account and generate test subscription emails. The on-page completion message stays in page memory and clears on navigation or reload. See the Paddle privacy policy.

Free review allowance

When you are signed out, the homepage stores a UTC date and completed-review count in your browser’s local storage to track 10 free reviews per day in that browser. This counter contains no PR URL, code, report or identity and is not sent to our server. It resets at 00:00 UTC; clearing site storage removes it. It is a device-local allowance, not an account quota. Browser storage must be available to submit through the homepage as a guest. For signed-in users, the server stores an opaque review reservation ID, UTC date, completion status and expiry against the account ID; it does not store the PR URL or report. This enforces one daily account allowance across devices. Server admission limits separately protect availability.

Account retention and requests

Detailed usage records older than 31 days are removed when the account starts another review. Checkout association records and notification deduplication IDs older than 90 days are removed during billing event processing. Account and subscription records remain until an account deletion request is handled; provider retention and database backups follow their own policies. To request access, correction or deletion, contact founder@releaseengineer.tech from your account email. Cancel any active subscription through Manage subscription before requesting deletion; deletion alone does not cancel provider billing.

Clerk privacy policy · Neon privacy policy

MVP notice

This page describes the current beta application’s data handling. It is a brief product notice, not a custom legal assessment. We will update it if the product’s data handling changes.

Downloads and voluntary feedback

If you choose to download a report or verification record, your browser saves a file on your device. Verification notes are held in page memory; they are not sent to our server, saved in browser storage or included in operational logs. Reloading clears them. Downloads can contain public PR identifiers, report text or notes you entered. Review the file before sharing it.

If you separately email feedback, your mail provider processes that message and the founder receives the material you chose to send. Agree permission and a retention period before a pilot record is retained. Publication of feedback, quotes or identity requires separate permission. Do not send secrets, private code or sensitive vulnerability details.