Information the app may store
Automation Receipts may store account details, automation names, receipt and run summaries, event timeline entries, approval or review notes, and basic server logs.
Readable receipts for workflows that do real work.
Privacy Policy
This policy describes the current early-access version of Automation Receipts. It may be updated as the product changes.
Automation Receipts may store account details, automation names, receipt and run summaries, event timeline entries, approval or review notes, and basic server logs.
API keys are stored hashed where applicable. After an API key is created, keep the full key value private and do not paste it into screenshots, chat, public docs, or shared examples.
Prefer useful summaries over raw private or customer data. Avoid sending secrets, passwords, API keys, access tokens, full private documents, or any data that is not needed to understand the workflow run.
Stored information is used to provide the receipt pages, run history, event timelines, review notes, account access, and basic operation of the service.
Basic server logs may include technical details such as request times, IP addresses, browser or client information, error details, and URLs requested. These logs help operate and troubleshoot the app.
This privacy policy may be updated as Automation Receipts changes. The current policy is intentionally plain and limited to what the simple early-access app can support.