Skip to main content

This policy describes how Automation Receipts handles information in the running service. It may be updated as the product changes.


Information Automation Receipts 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.

API keys

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.

What to send in receipts

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.

How information is used

Stored information is used to provide receipt pages, run history, event timelines, review notes, account access, and basic operation of the service.

Server logs

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.

Product changes

This privacy policy may be updated as Automation Receipts changes. The current policy is intentionally plain and describes what the service supports today.