Stamp.AI

Security at stamp

Last updated: August 13, 2026

You are trusting us with your designs, your address and your payment. This page sets out what we actually do to protect them, in enough detail to be useful rather than reassuring.

1. Our approach

We build on the principle of least privilege: every system, every service and every person gets the narrowest access that lets them do their job, and nothing more.

We would rather hold less data than defend more of it, so we collect only what the service needs and delete it when the reason for holding it ends.

2. Encryption

All traffic between your browser and Stamp AI runs over TLS 1.2 or higher. HTTP requests are redirected to HTTPS, and we send HTTP Strict Transport Security so your browser refuses to connect any other way.

Data at rest — your account, designs and order records — is encrypted with AES-256 on managed infrastructure. Backups are encrypted with the same standard.

3. Accounts and access control

Authentication is handled by a managed identity provider. Passwords are never stored in plain text; they are hashed with a slow, salted algorithm designed for the purpose.

You can sign in with Google instead of a password, in which case we never handle a password at all.

Customer database access uses row-level security to restrict records to their owner. Server operations use privileged credentials and must check ownership and authorization separately before reading or changing customer data.

Staff access to production is restricted to the few people who need it, requires multi-factor authentication, and is logged.

4. Payment security

We never see your card number. Card details are entered into fields hosted by our PCI DSS Level 1 certified payment providers and go straight to them; our servers receive only a token and the result of the transaction.

This means a compromise of Stamp AI could not expose your card details, because they were never on our systems.

3-D Secure and Strong Customer Authentication are applied where your bank or the law requires it.

5. Infrastructure

Stamp AI runs on managed cloud infrastructure with data hosted in the EU. Our providers hold ISO 27001 and SOC 2 Type II certification and are responsible for physical security, network isolation and patching at the platform layer.

Production, staging and development are fully separated, and production data is never copied into development environments.

Secrets and API keys are held in a managed secret store, never in source control, and are rotated when someone with access leaves.

6. Application hardening

The application ships a set of security headers on every response, including a Content Security Policy that restricts where scripts may load from, X-Frame-Options to prevent clickjacking, X-Content-Type-Options, and a strict Referrer-Policy.

Requests are rate limited to blunt brute-force attempts and abuse of the generation endpoints.

All input is validated against a schema at the API boundary before it reaches business logic, and database access uses parameterised queries throughout.

Dependencies are scanned automatically for known vulnerabilities, and security patches are applied on a priority basis.

7. Monitoring and logging

Errors and anomalies are captured by an application monitoring service, with personal data scrubbed before events are sent.

Authentication events, administrative actions and access to sensitive endpoints are logged and retained so that unusual activity can be investigated after the fact.

8. Backups and continuity

Databases are backed up automatically with point-in-time recovery. Backups are encrypted, held in a separate location, and restores are tested periodically — an untested backup is not a backup.

9. Our suppliers

We review the security posture of every provider that touches personal data before we adopt it, and we have a data processing agreement in place with each one.

Where a provider operates outside the EEA, transfers are covered by Standard Contractual Clauses — see our Privacy Policy.

10. If something goes wrong

We have a defined process for detecting, containing and investigating security incidents.

If a personal data breach affects your rights and freedoms, we will notify the relevant supervisory authority within 72 hours of becoming aware of it, and we will tell you directly, without undue delay, where the risk to you is high.

After any significant incident we carry out a review and publish what we changed as a result.

11. What you can do

The strongest account security depends partly on you:

  • Use a long, unique password, or sign in with Google.
  • Never reuse your Stamp AI password anywhere else.
  • Be sceptical of emails asking for your password — we will never ask for it.
  • Sign out on shared devices, and tell us at support@stamp.ai if you see activity you do not recognise.

12. Reporting a vulnerability

If you have found a security issue, please tell us at support@stamp.ai. Include enough detail to reproduce it, and give us a reasonable period to fix it before disclosing it publicly.

We will acknowledge your report within three business days and keep you informed while we work on it. We will not pursue legal action against researchers who act in good faith, stay within the scope of their own test accounts, and avoid degrading the service or accessing other people's data.