Security
Last updated: June 5, 2026
1. Approach
Security and privacy are built into Moonship from the ground up. The most secure data is the data you never collect — so Moonship's analytics are cookie-free and store no personally identifiable information about your site visitors. This page explains the technical and organizational measures we use to protect your account and your data.
2. Encryption
- In transit — all traffic to Moonship, including the tracking snippet, the dashboard, and the API, is served exclusively over HTTPS (TLS 1.2+). Plain HTTP requests are redirected to HTTPS.
- At rest — your account data and analytics events are stored in a managed PostgreSQL database with encryption at rest enabled by our infrastructure provider.
- Secrets — credentials and API keys are stored as environment configuration, never committed to source control.
3. Authentication
- OAuth sign-in — authentication is handled through Google or GitHub. Moonship never sees or stores your provider password.
- Sessions — authenticated sessions use signed, HTTP-only cookies. Session state is validated on every request.
- No password database — because we don't manage passwords, there is no password store to breach.
4. Privacy by design
Moonship's analytics snippet is engineered to minimize the data it ever touches:
- No cookies, localStorage, or sessionStorage are written to the visitor's browser.
- Visitor identity is a 16-character hash derived server-side from IP and user-agent, rotated daily at midnight UTC. The hash is irreversible.
- The raw IP address is used only to derive coarse geolocation (country, region, city) and is never stored.
- No names, emails, or other personal identifiers are collected from your site visitors.
See our Privacy Policy and GDPR pages for full detail.
5. Data retention & deletion
- Retention — analytics events are retained for as long as your account is active so you can see historical trends. We do not sell or share your analytics data.
- Account deletion — deleting your account permanently removes your sites, all of their analytics events, and your team memberships from our production database. This cascade runs immediately and cannot be undone.
- On request — you can ask us to delete a specific site's data at any time by contacting [email protected].
6. Access controls
- Account isolation — every query is scoped to the authenticated user and the specific site they are authorized to view. You can only ever access data for sites you own or have been explicitly invited to.
- Role-based team access — site owners control which team members can view or manage each site.
- Least privilege — internal access to production systems is limited to the personnel who need it to operate the service.
7. Payment security
Billing is processed by Stripe, a PCI-DSS Level 1 certified payment provider. Card details are entered directly with Stripe and never pass through or get stored on Moonship's servers.
8. Infrastructure & availability
Moonship runs on managed cloud infrastructure (Heroku / Salesforce) hosted in the United States, with regular platform-level patching and isolation between customers handled at the application layer. We rely on vetted sub-processors for hosting, payments, email, geolocation, and AI insights — see the GDPR page for the current list.
The platform is designed for high availability, and TLS termination, network-level protections, and infrastructure monitoring are handled by our cloud provider.
9. Backups & recovery
Our managed database provider performs automated, encrypted backups of the production database, allowing us to restore service in the event of data loss. Backups inherit the same encryption-at-rest protections as the primary database.
10. AI insights
AI-generated insights and answers from the built-in assistant are produced using Anthropic's Claude models. We send aggregated analytics (such as pageview counts, traffic sources, and goal conversions) along with non-identifying details like the pages a pseudonymous visitor viewed. No names, emails, raw IP addresses, or other personal identifiers are sent. Your data is not used to train any models.
11. Compliance & sub-processors
Moonship is built to support GDPR and CCPA compliance — because we don't use cookies or collect personal data from your visitors, much of the regulatory burden is removed by design. We maintain a current list of the sub-processors that help us operate the service on our GDPR page. We are not currently SOC 2 or ISO 27001 certified; the practices described on this page reflect the controls we have in place today.
12. Vulnerability management
- Application dependencies are kept up to date, and we monitor for known vulnerabilities in the open-source packages we rely on.
- Security headers (including HSTS) are applied to all responses, and the application enforces HTTPS on every request.
- Reported vulnerabilities are triaged and remediated on a priority basis — see Responsible disclosure below.
13. Responsible disclosure
If you believe you've found a security vulnerability in Moonship, we want to hear from you. Please email [email protected] with details and steps to reproduce. We ask that you:
- Give us a reasonable opportunity to investigate and remediate before any public disclosure.
- Avoid privacy violations, data destruction, or service degradation while testing.
- Only test against your own account and sites.
We will acknowledge valid reports promptly and keep you updated as we work toward a fix.
14. Incident response
In the event of a security incident affecting your data, we will investigate, contain, and remediate as quickly as possible, and notify affected account holders in accordance with applicable law.