Navigation history stays on your Mac
ReturnFast does not send captured app, window, browser, file, line, folder, or terminal context through its licensing API. Purchases, activation, and this website use online services and involve separate data.
Last updated
Data summary
| Category | Examples | Where it is used |
|---|---|---|
| Navigation context | App and window details; URLs, file paths, lines, folder paths, and titles when available | In memory on the Mac running ReturnFast |
| Local app and license state | Shortcut and launch settings, license key, cached validity, purchase email, generated device identifier | Local macOS preferences on that Mac |
| License and activation records | License key, email, plan and seat count, status, order references, device identifier and device name | ReturnFast licensing services |
| Payment data | Checkout, amount and currency, Stripe session and customer references | Stripe and ReturnFast order records |
| Website analytics | Website interaction and technical data made available to Google Analytics | This public website and Google Analytics |
Local navigation history
Depending on the active app, a navigation entry can include the app name and bundle identifier, process identifier, window title, page title and URL, editor file path and line, terminal title, Finder folder path, and capture time. ReturnFast uses these details to display the trail and restore a location.
The current version keeps up to 250 navigation entries in application memory. It does not persist that trail across quitting and relaunching ReturnFast. Navigation entries are not part of the request sent to the license-validation endpoint.
macOS permissions
Accessibility permission allows ReturnFast to inspect focused-window information and raise a window. Automation allows supported apps such as Chromium browsers, iTerm2, Terminal, and Finder to provide or select deeper context through macOS scripting. These permissions are managed by macOS in System Settings.
License and device data
Initial activation sends the entered license key, a randomly generated identifier for the Mac, and the Mac name to the ReturnFast validation endpoint. The service uses this information to check license status and enforce the purchased seat limit. A successful response includes the seat count and purchase email, which the app may cache locally.
A stored license is checked again in the background when ReturnFast starts. If the server cannot be reached, a previously cached successful activation remains usable.
Purchases and license lookup
Checkout is created with Stripe. Payment-card entry occurs in Stripe Checkout; Return Fast stores order and licensing details such as purchase email, amount, currency, Stripe session or customer references, license key, seat count, and license status.
The license lookup sends the email you enter to the Return Fast service. If a matching purchase is found, the page shows masked license details and requests delivery of the full key to that email address.
Website analytics and service providers
The public website loads Google Analytics after the page becomes interactive. Google Analytics may use cookies or browser storage under its configuration. Checkout uses Stripe, licensing records use Supabase, and transactional license email is configured through Resend when email delivery is enabled. Those providers process data needed for their respective services under their own terms and policies.
Retention and questions
This page does not state a fixed retention period for purchase, license, activation, analytics, or support records. For a privacy question or a request concerning your personal data, email hello@returnfa.st from the address associated with the purchase when applicable.
Changes to this page
Material changes should be reflected here with a new visible update date. Product behavior is also documented in How it works and the changelog.