Security

Security & plan-file handling

Last updated: October 8, 2026

Your plan sets are your clients' and your own work product. This page describes, in plain terms, what we actually do to protect them. It lists only things that are true of the product today. For the full legal detail, see our Privacy Policy.

What we don't claim. ReadMyBlueprint is a small company. We do not hold a SOC 2 report, ISO 27001 certification or any other third-party security certification, and we do not run a bug bounty program. We would rather tell you that than imply otherwise.

How your plan files are handled

Who can see your plans

Other customers cannot. Access from our side is limited to the people operating ReadMyBlueprint, who can reach our hosting and database when needed to run and support the service (for example, to investigate a problem you report). We do not sell plan data or use it to build advertising profiles.

Deleting your data

Accounts and sign-in

Encryption in transit

The app and its API are served over HTTPS, and the API sends an HSTS header telling browsers to require HTTPS. It also sets standard protective headers (no framing, no MIME sniffing).

Payments

Payments are handled by Stripe using Stripe Checkout. Your card number, expiry and CVC are entered on Stripe's page and never pass through or get stored on our servers. We keep only a Stripe customer reference and your plan status. Stripe notifications to our server are verified with Stripe's signature before we act on them.

Infrastructure

These providers are listed with their roles in our Privacy Policy.

Monitoring and analytics

Report a security issue

If you think you've found a vulnerability or a problem with how your data is handled, email support@readmyblueprint.com with what you found and how to reproduce it. Please don't access other customers' data while testing. We don't offer monetary rewards, but we read every report.

Questions

Questions about how we handle your plans? Write to support@readmyblueprint.com, or read the Privacy Policy.