The short version
- Less data, less riskWe do not store your sermons, your passwords (there are none) or your card details.
- Encrypted and signedHTTPS everywhere with HSTS, signed HTTP-only cookies, and keyed hashes instead of raw IPs.
- Payments by StripeCard details go straight to Stripe, a PCI DSS Level 1 certified provider.
- Report a vulnerabilityGood-faith security research is welcome, with safe harbor and a fast response.
1. Our approach
The most effective way to protect data is not to hold it. Free AI Sermon Generator is built to keep as little as possible: your requests and sermons pass through our server without being stored, your saved work lives on your own device, there are no passwords to steal, and payment details never touch our systems. What remains is protected by the measures below.
2. Data in transit
- Every page and API request is served over HTTPS (TLS). Plain HTTP requests are redirected.
- HTTP Strict Transport Security (HSTS) tells browsers to use only encrypted connections with us.
- Requests to AI providers and to Stripe are also made over encrypted connections.
3. Data we store
- Our database and configuration live outside the public web folder, so they cannot be downloaded from the website. API keys and secrets are never sent to browsers.
- IP addresses and device identifiers used for free limits are stored only as keyed hashes (HMAC-SHA-256 with a secret key), and deleted within 35 days.
- Sign-in links are random, single-use and valid for 30 minutes. We store only a SHA-256 hash of each link, never the link itself.
- Our usage log records events such as the engine and tradition used, never your text, email address or IP address.
- Data is deleted automatically on the schedule in our Privacy Policy.
4. Sign-in and sessions
- No passwords: paid subscribers sign in with a one-time email link, so there is no password to reuse, guess or leak.
- Session and device cookies are signed with HMAC-SHA-256 so they cannot be forged, and are set
HttpOnly,SecureandSameSite=Lax. - The sign-in form gives the same answer whether or not an address has an account, and is rate-limited, so it cannot be used to discover accounts or flood inboxes.
5. Payments
All payments are handled by Stripe Checkout and the Stripe billing portal, on Stripe’s own secure pages. Stripe is certified as a PCI DSS Level 1 Service Provider, the highest level of certification in the payments industry. We receive only a customer reference, your email address and the status of your plan. Messages from Stripe to our server are verified with a cryptographic signature before we act on them.
6. Application safeguards
- Our API accepts requests only from our own pages, and limits how often each device and network can call it.
- Security headers on every response prevent content-type sniffing, clickjacking and unnecessary referrer leakage, and switch off camera, microphone and location access.
- No third-party scripts run on our pages, which removes a whole class of supply-chain attacks. Our fonts and code are served from our own server.
- API responses are never cached and never indexed by search engines.
- Access to our servers uses dedicated SSH keys, not shared passwords.
7. Your part
- Keep your email account secure, with a strong password and two-step verification, since it is your key to a paid plan.
- Sign out of the studio on shared or public computers.
- Never paste confidential pastoral information, passwords or financial details into any AI tool, including ours.
- Be careful with emails that claim to come from us. We will never ask for your card number or a password by email.
8. If something goes wrong
If we learn of a security incident, we will move quickly to contain it, investigate it and fix the cause. If personal information is affected, we will notify the people concerned and the relevant authorities within the time the law requires (for example, within 72 hours to a supervisory authority under the GDPR), and tell you what happened and what you can do.
9. Responsible disclosure
We welcome reports from security researchers and users. If you believe you have found a vulnerability, please report it through our contact form and choose Security report, with a short description and how we can reach you.
Our commitments to you
- We will acknowledge your report within three business days and keep you informed as we work on it.
- We will not take legal action against research carried out in good faith under these guidelines.
- With your permission, we will thank you publicly once the issue is fixed.
Please
- do not access, change or delete other people’s data; use only accounts you own;
- do not run denial-of-service, load or spam tests, or automated scans that degrade the Service;
- do not use social engineering or phishing against us or our users;
- do not test the systems of our providers (Hostinger, Stripe or the AI companies); report issues to them directly;
- give us reasonable time to fix an issue before disclosing it publicly.
We do not currently run a paid bug bounty program. Reports about missing best-practice headers without a demonstrated impact, self-XSS, or volumetric rate-limiting are generally out of scope.