Effective date: September 16, 2026
Capper (“Capper,” “we,” “us,” or “our”) is a software service operated by Jorge, an individual sole proprietor in Texas, United States. Capper is intended for people in the United States who are at least 18 years old.
Desktop processing, in plain language
With On this Mac selected, rewriting and dictation happen on your Mac. Capper holds audio in memory and never writes it to disk. It does not log prompts, selected text, transcripts, or responses. The activity view records only time, style, processing provider, sent byte counts, and outcome.
Local use needs no account. A 14-day trial is followed by a one-time license. Purchased licenses are checked at launch, about once a day, after a sufficiently stale reconnection, and when you choose Validate Now. These checks contain no writing or audio.
Setup downloads and optional app update checks also use the internet. Cloud processing happens only when you select it. Custom servers receive your requests; Capper cannot verify their downstream handling. Deliberately inserting text, opening links, or running a confirmed action lets the destination app handle that content.
Information Capper accesses on your Mac
Capper uses macOS Accessibility APIs to identify the focused application, window, editor, selection, and bounded surrounding text needed to complete a request you start. Capper does not require Screen Recording. Some supported canvas and Electron editors use a guarded, temporary pasteboard fallback. Capper attempts to restore existing pasteboard items and visibly reports a restoration failure.
Captured text is held only for the current panel operation. The app does not create a conversation history. Capper may display source metadata and character counts in Settings for diagnostics, but not the captured document text.
Local and custom model requests
On this Mac identifies embedded text processing plus local speech. External local servers and custom servers have separate labels. Capper cannot certify a separate process as its own embedded processing.
The Bionic/LM Studio and Ollama presets use loopback addresses on your Mac. Capper does not send those model requests to Capper Cloud. If you choose a non-loopback Custom server, your instruction and captured context are sent to the server you selected. You are responsible for that server and its privacy and security practices.
Capper Cloud requests
Cloud is closed to new subscriptions. The disclosures below continue to apply to existing subscribers, whose service and account controls are retained.
Cloud processing happens only when selected. Mixed processing identifies which part uses Cloud. Where Cloud speech is selected and available, audio passes through Capper Cloud to its speech provider; it is not local processing.
Cloud text processing sends your instruction and bounded captured text through Capper's Vercel-hosted proxy to OpenRouter and a model provider. Before transport, the app removes the source application name, bundle identifier, and window title. Capper requires zero-data-retention routing and denies provider endpoints that may collect request content. Capper and its Cloud database do not log or store prompt, document, or response text.
Do not submit regulated, highly sensitive, or confidential information you are not authorized to share. Capper is not designed for protected health information, payment-card data, government identifiers, or consequential decisions involving health, law, employment, housing, credit, education, insurance, or safety.
Purchases, licenses, and usage
Polar is the merchant of record and processes checkout information, payment details, taxes, receipts, subscriptions, and license activations under its own policies. Capper does not receive complete payment-card numbers. Capper receives identifiers and status information needed to provide the purchased product, including Polar customer, order, product, subscription, benefit, license, and meter identifiers.
The Cloud service stores a keyed hash—not the raw license key—linked to the relevant Polar identifiers, license tier, status, and expiration. Short-lived entitlement cache records are encrypted by Capper before they are sent to Upstash. Usage receipts contain a request ID, friendly model alias, reserved credits, bounded token counts when available, optional app version, credit-window data, and processing timestamps. They do not contain the prompt or response.
Website, security, and support information
Vercel processes ordinary hosting information such as IP address, request time, requested URL, device/browser information, and security logs. Vercel Analytics provides aggregate, cookie-free traffic measurement and is disabled on Capper's purchase-confirmation page. Capper does not use advertising pixels or sell browsing activity. Website analytics removes query strings and fragments from measured page URLs. When enabled, aggregate button-click events include only a fixed action name and a recognized campaign source, never free-form text or purchase identifiers. Campaign sources are not stored in browser cookies or local storage. An optional post-purchase source question opens an email draft; it sends nothing until you send that email yourself.
To prevent abuse, Capper briefly processes the requester's IP address in server memory and sends only a domain-separated HMAC pseudonym to Upstash for the rate-limiting window. If you contact support, we use your email address, message, attachments, and related correspondence to answer and protect the service.
Why we use information
We use information to provide and secure Capper; authenticate licenses; meter Cloud credits; process purchases and subscriptions; prevent fraud, abuse, and service disruption; diagnose failures; communicate with users; comply with law; and establish or defend legal claims. We do not use Cloud prompt or response content for advertising or model training.
Service providers and disclosures
Capper uses Apple platform services, Vercel for hosting and analytics, Neon for Postgres, Upstash for caching and rate limits, GitHub for releases, Polar for commerce and licensing, OpenRouter for AI routing, and OpenRouter's selected zero-retention model provider. These providers process information to perform services for Capper or under their own terms where you interact with them directly. We may also disclose information when reasonably necessary to comply with law, protect rights and safety, investigate abuse, or complete a business reorganization subject to appropriate protections.
Capper does not sell personal information, share it for cross-context behavioral advertising, or use it for targeted advertising. We do not knowingly disclose personal information to third parties for their own direct marketing.
Retention
The desktop activity view records only timestamp, mode ID, provider, outbound payload byte count, and an enumerated outcome. It retains at most 1,000 entries across two files; Clear covers both. Separate empty-output diagnostics contain bounded model, settings, and cause metadata, not writing or audio. Purchased licenses use cached validation and existing grace behavior; licensing is not guaranteed to work permanently offline.
- Capper does not retain Cloud prompt or response content.
- Pseudonymous Upstash rate-limit identifiers expire after the short rate-limit window.
- Finalized usage receipts are retained for up to 90 days.
- Expired credit-window records are retained for up to 180 days.
- Inactive license records are deleted after 90 days when no retained usage receipt requires them. Active license records are kept while needed to provide and secure the license.
- Webhook delivery identifiers are retained for up to 365 days to prevent duplicate processing and replay.
- Support correspondence is ordinarily retained for up to 24 months unless a longer period is needed for security, disputes, or law.
Polar, Vercel, OpenRouter, and other providers maintain their own records under their respective policies and legal obligations.
Your privacy choices and rights
Depending on applicable law, you may request access to, correction of, or deletion of personal information associated with you. You may also ask for a portable copy, object to or restrict certain processing, or appeal a denied request where those rights apply. Email privacy@getcapper.app with the subject “Privacy Request” or “Privacy Appeal.” We will verify requests in a way proportionate to the information involved. An authorized agent may submit a request where permitted by law, subject to proof of authority and identity verification.
Capper does not sell or share personal information for behavioral advertising, so there is currently no sale/share opt-out to apply. We treat a legally recognized Global Privacy Control signal as an opt-out where applicable. Because browsers do not provide a consistent Do Not Track standard and Capper does not perform cross-site advertising tracking, other Do Not Track signals do not change the site's behavior.
Security
We use measures designed for the nature of the information, including encrypted transport, keyed credential hashing, restricted production credentials, signed and notarized app releases, signed updates, request size limits, rate limits, and access controls. No system is completely secure, and we cannot guarantee absolute security.
Children and geographic scope
Capper is not directed to children and is not offered to anyone under 18. We do not knowingly collect personal information from children. If you believe a child has provided information, contact us so we can investigate and delete it as appropriate. Capper is offered only in the United States and is not directed to people outside the United States.
Changes and contact
We may update this policy as Capper changes. We will post the revised policy with a new effective date and provide additional notice when required by law. Questions and privacy requests may be sent to privacy@getcapper.app.