Privacy Policy

1. Our two roles

• Controller. For website visitors, account holders, billing, security and support we decide why and how personal data is processed, so we are the controller.
• Processor / service provider. The webhook payloads, headers and destination URLs you send through Retryx (“Customer Data”) are processed on your instructions, only to receive, store, deliver, retry, show and replay them. You decide what you send and are responsible for having a lawful basis for it. If you need data-processing terms for your own compliance, contact us.

2. What we process

Account and team

Email address, optional name, a one-way argon2id hash of your password (we never store the password), your two-factor secret (encrypted) and recovery codes (hashed) if you enable 2FA, organization membership and role, invitations, and your sessions (creation time, IP address, browser user-agent).

Configuration

Organization, project, endpoint and destination names and settings, destination URLs, custom header names and values, JSON Schemas, payload-transform rules, notification preferences, and API key metadata (we store only a hash of each key).

Customer Data

The body of each webhook you send us and its headers (credential headers such as Authorization and Cookie are not stored), plus every delivery attempt: when it ran, the HTTP status, duration, the resolved destination IP, and up to 16 KB of the response body for debugging.

Billing

Plan, subscription status, usage counts (number of events accepted), invoice references and your Stripe customer and subscription identifiers. Card details are collected and processed by Stripe; we never receive or store card numbers.

Communications

Messages you send through the contact form (name, email, company, message, IP address) and the transactional emails we send you (verification, password reset, invitations, alerts you enable).

Technical and security data

IP address and user-agent in an append-only audit log of security-relevant actions (sign-in, password reset, 2FA changes, API key and team changes, administrative actions), rate-limit counters, and server logs of requests (method and path without query strings; cookies and authorization headers are redacted).

Cookies

Inside the signed-in app we use only strictly necessary cookies and browser storage. On our public marketing pages we use Google Analytics 4 (page views, approximate location, device and browser type, referrer); it is not loaded in the app, and not for visitors who send Do Not Track or Global Privacy Control. No advertising cookies. See the Cookie Policy.

3. Why we process it

• To provide and operate the service you asked for (contract).
• To authenticate you and keep the platform secure: abuse prevention, rate limiting, fraud and incident investigation (legitimate interests).
• To bill you and keep accounting records (contract, legal obligation).
• To answer support and sales messages (legitimate interests, pre-contract steps).
• To send service and security notices (contract, legitimate interests).
• To meet legal obligations and defend legal claims.

We do not sell personal data and we do not use Customer Data for advertising or to train models.

4. Who we share it with

• Render: hosting, managed PostgreSQL and Key Value (queues). Our primary infrastructure is operated in the United States.
• Stripe: payment processing, invoicing and the customer billing portal.
• Google: website analytics on our public pages only (Google Analytics 4, which does not log or store IP addresses). Never used inside the app.
• Our email delivery provider: sends transactional email (your email address and the message content).
• The destinations you configure: we deliver your events to the URLs you set, on your instruction.
• Authorities or advisers where required by law, and a successor if the business is transferred (you would be told).

These providers process data under their own terms and security programmes. We will update this list if it changes.

5. How long we keep it

• Webhook payloads: removed automatically after the retention period of your plan (7 to 365 days; see Pricing). Event metadata and delivery history remain so you can still audit what happened.
• Attempt response bodies: removed after 14 days by default.
• Account and configuration data: while your account exists, then deleted or anonymised after closure except where we must keep it.
• Audit log and usage ledger: kept for security, accountability and billing. They are append-only by design and contain user identifiers and IP addresses; we cannot selectively erase individual entries, but we will minimise and anonymise them on a valid deletion request where the law requires.
• Sessions and one-time tokens: expire automatically and are purged shortly afterwards.
• Backups: kept by our hosting provider for its backup period, after which deleted data ages out.

6. Security

We protect data with encryption in transit, encrypted storage of secrets, strict tenant isolation, access control and audit logging. Details and limits are on the Security page. No system is perfectly secure; we will notify affected customers of a breach as required by law.

7. International transfers

If you are outside the United States, your data is transferred to and processed in the United States and wherever our providers operate. Where required we rely on appropriate safeguards such as standard contractual clauses offered by our providers.

8. Your rights

Depending on where you live (for example under the GDPR, UK GDPR or CCPA/CPRA) you may have the right to access, correct, delete or export your personal data, to object to or restrict certain processing, and to withdraw consent. Contact us through the contact form; we may need to verify your identity and will respond within the time the law requires. You can also remove projects, endpoints, destinations, API keys and team members yourself in the dashboard. If you are unhappy with our answer you may complain to your local data-protection authority.

If you are an end user of one of our customers (for example your data appears in a webhook a customer sent), please contact that customer first; we act on their instructions.

9. Children

Retryx is a business tool and is not directed to children. We do not knowingly collect personal data from anyone under 16.

10. Changes

We will post changes here with a new “last updated” date and, for material changes, notify account holders by email or in the dashboard.

11. Contact

Use the contact form and mention “privacy”.