This privacy policy explains how PastePrompt handles local app data, source code, payments, support, and update checks.
This page summarizes the current PastePrompt policy in plain language. It is not legal advice; if formal contract terms apply to your purchase or organization, those written terms control.
PastePrompt is designed as a local-first macOS app. Repository scanning, file selection, preview, token estimation, secret scanning, Git metadata, Git diff context, prompt templates, and context bundle generation are intended to run locally on your Mac.
The desktop app does not need to upload your source code to a PastePrompt backend to build context bundles. Source code can leave your Mac when you copy, export, paste, attach, sync, email, or otherwise share a generated bundle with another tool or service.
PastePrompt may store local app data such as:
Full source contents should not be stored in prompt history by default. Raw secret values from scanner warnings should not be stored as persistent app data by default.
Paid checkout, receipts, invoices, taxes, refunds, and customer account details may be processed by Stripe or another configured payment provider. PastePrompt may use the minimum purchase details needed to issue a license or answer payment support, such as name, email address, selected plan, billing details, payment status, and receipt identifiers.
If you contact support at roberreigada@gmail.com, your message, email address, app version, license status details you provide, and diagnostic context you choose to include may be used to answer the request. Do not send source code, credentials, private keys, or generated bundles unless support explicitly asks for sanitized details.
If update checks are configured, the app may contact a release manifest or update endpoint for version metadata such as app version, platform, CPU architecture, and selected release channel. Update checks should not require source code, selected file paths, generated bundles, prompts, or secret scanner findings.
PastePrompt does not add telemetry or analytics by default in the current V1 site/app plan. If telemetry, analytics, crash reporting, or cloud sync are introduced later, this policy should be updated before those features are enabled.
For technical privacy details, read the local-first model, secret scanning, and clipboard/export risk docs.