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.
| Area | What we do |
|---|---|
| Connections | All traffic uses HTTPS, and security headers limit what the site can load. |
| Account records | Database access rules keep each account's records private, and we test production weekly to confirm a signed-out visitor cannot read them. |
| Payments and plans | Records that decide payments and plan access can only be written by our servers. |
| Service notifications | Payment and background-removal notifications are verified by signature before we act on them. |
| Abuse prevention | API endpoints are rate limited, and CAPTCHA protects email and SMS sign-in and anonymous contact messages. |
| Code changes | Every code change goes through a pull request with automated tests, code scanning, secret scanning and a dependency audit. |
| Dependencies | New dependency releases are held for seven days before we adopt them, which helps avoid compromised packages. |
| Credentials | Service 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.
We follow DevSecOps practices: security checks are built into everyday development rather than left to occasional audits.
| Control | How it works |
|---|---|
| Static analysis | Semgrep runs in CI and blocks a merge when it fails. |
| Secret scanning | gitleaks scans the full git history in CI and blocks a merge when it fails. |
| Dependency audit | The audit covers the whole lockfile and blocks a merge when it fails. A malware advisory fails it even for a development dependency. |
| Production probe | Once a week we probe production as a signed-out client to confirm that database tables, restricted functions and storage reject access. |
| Content Security Policy | An 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 hardening | CI actions are pinned to commit hashes and run with read-only tokens. |
These are the main providers we rely on to run Halftone Maker. Their own security practices apply to their services.
| Provider | Used for |
|---|---|
| Vercel | Hosting, analytics and performance metrics |
| Supabase | Sign-in, database and file storage |
| Stripe | Payments and subscriptions |
| Fal | AI background removal |
| Sentry | Error and performance monitoring |
| Resend | Email delivery |
| Cloudflare | CAPTCHA on sign-in and contact forms |
| proxycheck.io | Country and VPN lookup for regional access |
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.
We will not pursue legal action over good-faith research that follows these guidelines. We do not currently run a bug bounty program.