Draft for legal review. This is a generic template, not advice from a lawyer.
Privacy policy
Last updated 4 November 2026. Replace this draft before you take real customers.
What we store
When you create a ShipSafe account we store your name, email, a password hash or magic-link token, the time you signed up, and your plan. If you connect billing we store a Stripe customer id and subscription status. We do not store full card numbers for your ShipSafe subscription. Stripe does.
Flow credentials you provide — test email, test password, and the public Stripe test card number if you use a checkout flow — are encrypted with AES-256-GCM before they are written down. Screenshots are images of pages on a domain you verified.
The free page scan stores the email, the URL, and a short summary of the public HTML. It is limited to one scan per email. The scan does not submit forms.
Who else sees it
Email alerts go out through the provider configured with RESEND_API_KEY, or stay in a local mailbox when that key is absent. If ActiveCampaign environment variables are set, new signups are added to the list you name. If they are not set, nothing is sent. Stripe receives billing details when you use test-mode Checkout. An optional LLM key is used only to phrase a fix prompt, and only the failure description is sent.
Your choices
You can turn failure emails off, delete flows, and cancel a subscription from the billing page. To remove an account, write to the operator of this deployment. Do not point ShipSafe at a domain you do not control, and do not store real customer passwords.