Security

Halftone Maker is run by an independent developer. This page explains how your images and data are handled and what we do to protect them. No online service can promise perfect security, so we describe what we actually do and tell you how to reach us if you find a problem.

Your images

  • Halftone processing runs in your browser. Images you open in the app are not sent to our servers to be halftoned.
  • AI background removal is the exception. When you start it, the image is uploaded to private storage and sent to Fal for processing. Our copy is normally deleted automatically when the job finishes.
  • Images you attach to a feedback message are sent to us by email.

Your data

  • With an account, we store your profile, subscription status, usage counts and the presets you save.
  • Card details are entered on Stripe's checkout and handled by Stripe. We do not store card numbers.
  • Our Privacy Policy sets out what we collect and why.

How we protect the service

AreaWhat we do
ConnectionsAll traffic uses HTTPS, and security headers limit what the site can load.
Account recordsDatabase access rules keep each account's records private, and we test production weekly to confirm a signed-out visitor cannot read them.
Payments and plansRecords that decide payments and plan access can only be written by our servers.
Service notificationsPayment and background-removal notifications are verified by signature before we act on them.
Abuse preventionAPI endpoints are rate limited, and CAPTCHA protects email and SMS sign-in and anonymous contact messages.
Code changesEvery code change goes through a pull request with automated tests, code scanning, secret scanning and a dependency audit.
DependenciesNew dependency releases are held for seven days before we adopt them, which helps avoid compromised packages.
CredentialsService credentials are kept on the server side and are rotated when there is reason to.

We review these measures at least quarterly. Last review: October 23, 2026.

For technical reviewers

We follow DevSecOps practices: security checks are built into everyday development rather than left to occasional audits.

ControlHow it works
Static analysisSemgrep runs in CI and blocks a merge when it fails.
Secret scanninggitleaks scans the full git history in CI and blocks a merge when it fails.
Dependency auditThe audit covers the whole lockfile and blocks a merge when it fails. A malware advisory fails it even for a development dependency.
Production probeOnce a week we probe production as a signed-out client to confirm that database tables, restricted functions and storage reject access.
Content Security PolicyAn enforced policy blocks scripts from origins we have not allowed. It still permits inline scripts, so we also forbid raw HTML rendering in our code.
CI hardeningCI actions are pinned to commit hashes and run with read-only tokens.

Service providers

These are the main providers we rely on to run Halftone Maker. Their own security practices apply to their services.

ProviderUsed for
VercelHosting, analytics and performance metrics
SupabaseSign-in, database and file storage
StripePayments and subscriptions
FalAI background removal
SentryError and performance monitoring
ResendEmail delivery
CloudflareCAPTCHA on sign-in and contact forms
proxycheck.ioCountry and VPN lookup for regional access

Reporting a vulnerability

If you think you have found a security problem, email hello@halftonemaker.com with "Security" in the subject, the steps to reproduce it and the impact you expect. We aim to reply within five business days.

  • Test only with your own account, and stop as soon as you have confirmed the issue.
  • Do not access other people's data, degrade the service or run high-volume automated scans.
  • Give us reasonable time to fix the issue before sharing it publicly.

We will not pursue legal action over good-faith research that follows these guidelines. We do not currently run a bug bounty program.