Privacy Policy
Last updated: November 2026
Who we are
MockCard (www.mockcard.io) is a payment-testing service operated by Arixeva Labs ("we", "us"). This policy explains what we collect when you use the website, the API, the SDKs and GitHub Action, monitors and the Webhook Health Check, why, and the choices you have. Questions: support@mockcard.io.
The short version
- All card numbers MockCard generates are fictitious. We never ask for, process or store real card data.
- API keys and sign-in sessions are stored only as one-way hashes. Webhook secrets you give us are encrypted and never shown again.
- The free Webhook Health Check does not save the URL you test or your handler's responses.
- Monitors only contact domains you have proved you control.
- Analytics cookies (Google Analytics) and blog comments (Disqus) load only after you agree.
- We don't sell personal data and we don't run ads.
Information we collect
Account data: your email address when you verify it, your plan, billing interval, subscription status and monthly usage count. For API keys we store a one-way hash, a short prefix (so you can tell keys apart), the name and scope you give them, and when they were created and last used. Never the full key.
Team members (Agency): the email addresses the account owner invites, and when they joined. Invited people sign in with their own email.
Projects: the name and gateway format you choose, the project's probe secret, and, if you provide one, your payment gateway's test-mode webhook signing secret. Both secrets are encrypted at rest and never returned in full.
Runs: for each chaos run, the scenarios, the planned test events, the status codes and timings your handler returned, the outcome checks your test suite reports (names, pass or fail, and any message you include), the score, and, if supplied, the commit and branch name. For push runs, the target URL.
Monitors: the URL you monitor, its environment and schedule, the domain-verification token, alert settings, an encrypted copy of any Slack webhook URL you add, and the results of each scheduled check.
Client reports (Agency): the brand name and link you set. A shared report link shows that project's results and monitor status to anyone who has it, until it expires.
Usage and request data: when you call the API we log the plan, IP address, request source, brand, scenario, gateway, amount, currency, response status, timing and the last four digits of the fictitious card returned. If you supply a webhook_url (Pro and Agency), we log that URL and the delivery outcome so you can check delivery status.
Anonymous usage: if you use MockCard without an account we store your IP address with a usage counter to enforce the free limit.
Resilience audits (Pro and Agency): the webhook URL you audit, the probe results, score and findings are saved to your account so you can review audit history.
Support messages: what you send through the contact form (name, email, message) is delivered to our support inbox by email.
Payments: subscriptions are processed by Dodo Payments, our merchant of record. We receive your subscription status and customer reference, never your card details.
Webhook Health Check
When you run the free health check, MockCard sends a small, fixed set of clearly labelled test webhook requests (currently five) to the URL you enter and measures how it responds. We do not save the URL or the responses, in our database or in our server logs; we record only that a check ran (time, IP address, gateway and how many probes passed). Results are shown in your browser, and the share link you can create encodes only the score and pass/fail flags; it contains no URL and no response data. To prevent abuse, the check is rate-limited per IP address, each probe is a single request, and only publicly reachable URLs are accepted. Private-network and internal addresses are refused. Only test URLs you own or are authorised to test.
How we use information
- To provide the service: generate test data, deliver webhooks, plan and score runs, run your monitors, send the alerts and weekly summaries you set up, enforce plan limits and show delivery status.
- To keep it secure: verify domain ownership before monitoring, detect abuse and rate-limit automated misuse.
- To communicate with you: verification codes, monitor alerts, replies to support requests and essential service notices.
- To improve MockCard: understand, in aggregate, which pages and features developers use. Besides the consent-based analytics described below, our servers report a few product milestones (for example a subscription started, a project or monitor was created, the first CI run) to Google Analytics under a random-looking account number, with no email address or other contact details.
We rely on performance of a contract (providing the service you asked for), our legitimate interests (security, abuse prevention, aggregate product analytics, including the server-side milestones, which you can object to by emailing us) and, for analytics cookies and embedded comments, your consent.
Service providers
We share data only with providers that help us run MockCard, under contracts that restrict their use of it to providing their service to us:
- Hosting and content delivery provider: runs the website, API and scheduled monitors, and provides cookieless aggregate web analytics.
- Managed database provider: stores account, project, run and log data.
- Transactional email provider: sends verification codes, monitor alerts, weekly summaries and support replies.
- Dodo Payments: subscription billing, as merchant of record. You deal with them directly at checkout.
- Google (Google Analytics): browser analytics only with your consent; pseudonymous server-side product milestones as described above.
- Disqus: only with your consent or on request.
When you add a Slack webhook to a monitor, alerts are sent to the Slack workspace you chose. That workspace is yours, not ours. Ask us for the current list of the providers above and we'll send it.
These providers may process data outside your country. Where required, transfers rely on appropriate safeguards such as standard contractual clauses.
Retention
Account data, team members, projects and monitors are kept while your account is active and deleted on request. Deleting a project deletes its runs and monitors. Run results and API request logs are retained for up to 12 months for your history, support and abuse prevention. Anonymous IP usage counters and audit history are kept until you ask us to delete them or they are no longer needed. Sign-in sessions expire after 30 days. Shared client-report links stop working after 90 days. Webhook Health Check URLs and responses are not stored.
Your rights
Depending on where you live (for example under the GDPR, UK GDPR, India's DPDP Act or US state privacy laws) you can ask to access, correct, export or delete your personal data, object to or restrict processing, and withdraw consent at any time. Email support@mockcard.io from the address on your account. We respond within 30 days. You can also complain to your local data protection authority.
Security
Traffic is encrypted with TLS. API keys and session tokens are random and stored only as SHA-256 hashes, and keys can be revoked at any time. Gateway signing secrets, probe secrets and Slack webhook URLs are encrypted with AES-256-GCM. Webhooks and production probes are signed with HMAC-SHA256. Monitors run only against domains you have verified via DNS or a well-known file, and outgoing requests never go to private or internal addresses. Generated test data is fictitious and must never be used for real transactions.
Children
MockCard is a developer tool and is not directed at children under 16. We do not knowingly collect their data.
Changes
We'll update the date above when this policy changes and, for material changes, notify account holders by email.