Privacy Policy
This notice explains how BeaconRelay handles personal data for its website, accounts, billing, support, and Salesforce event transport.
- Effective
- 2026-09-30
- Contact
- legal@beaconrelay.dev
1. Roles
The Provider is a controller for account, security, billing, support, and service-administration data. For personal data inside Salesforce event payloads and receiver responses, the customer determines purposes and means and is normally the controller; Provider acts as processor under the DPA. Salesforce data subjects should first contact the relevant customer.
2. Data collected
| Category | Examples | Source |
|---|---|---|
| Account | Name, work email, company, role, password hash, verification and recovery status | You |
| Salesforce connection | Org and user IDs, instance URL, encrypted OAuth client credentials, encrypted access and refresh tokens, topic configuration | You and Salesforce |
| Event transport | Encrypted payload, object/operation metadata, replay ID, hashes, signatures, destination URL, receiver responses | Salesforce and your receiver |
| Operations and security | Event states, attempts, timestamps, incidents, IP-derived rate-limit identifiers, audit actions | Service use |
| Billing | Stripe customer, subscription, invoice and payment-status identifiers; BeaconRelay does not store full card details | You and Stripe |
| Communications | Email address, transactional email content and delivery status, support messages | You and Brevo |
3. Purposes and legal bases
- Contract: create accounts, authenticate users, connect Salesforce, transport events, provide plans, billing, support, and requested communications.
- Legitimate interests: secure and diagnose the service, prevent fraud and abuse, maintain operational evidence, and improve reliability without using payload content for unrelated purposes.
- Legal obligations: accounting, tax, compliance, lawful requests, and protection of legal claims.
- Consent: where required for optional communications or non-essential technologies. BeaconRelay currently uses essential session and security cookies only.
4. Sharing and subprocessors
Data is disclosed only as needed to provide or protect the service, follow customer instructions, complete transactions, or comply with law. OVH SAS hosts compute, database, storage, and backup infrastructure in Germany. Brevo provides transactional email, Zoho Corporation B.V. provides support email in its EU region, Stripe provides subscription billing, and Salesforce provides customer-authorized source connectivity. Customer-configured webhook receivers receive event data at Customer’s direction.
5. International transfers
Primary BeaconRelay infrastructure is hosted in Germany. Stripe, Zoho, Brevo, Salesforce, or customer-selected destinations may process limited data outside the EEA. Where GDPR transfer restrictions apply, transfers rely on an applicable adequacy decision, the EU-US Data Privacy Framework, approved Standard Contractual Clauses, or another lawful safeguard identified in the relevant provider agreement.
6. Retention
Event content follows the plan-specific, technically enforced schedule described in the Data Retention Schedule. OAuth tokens remain until revocation or organization deletion. Operational integrity evidence remains while the account exists unless deleted with an organization or on documented customer instruction, subject to legal obligations. Account, billing, and email-audit records are retained only while needed for service administration, security, disputes, or applicable accounting and tax obligations. Germany-hosted backup copies are restricted to disaster recovery and removed through controlled rotation.
7. Security
Measures include encrypted payload and OAuth-token storage, TLS transport, password hashing, scoped access controls, CSRF and session protections, rate limits, destination validation, restricted signing keys, and audit records. Security is risk-based and no internet service can guarantee absolute security.
8. Rights
Depending on applicable law, individuals may request access, correction, deletion, restriction, portability, or objection, and may withdraw consent without affecting earlier processing. Contact legal@beaconrelay.dev. For payload data, identify the customer controlling the Salesforce organization. You may complain to the competent data-protection authority.
9. Automated decisions and children
BeaconRelay does not make decisions producing legal or similarly significant effects about individuals and is not directed to children. Customers must not knowingly use the service to collect children’s data without a valid legal basis and appropriate safeguards.
10. Changes and contact
Material changes will be announced through the service or account email. BeaconRelay is operated by a French individual entrepreneur whose statutory identification is supplied on applicable orders and invoices. No Data Protection Officer has been appointed. Questions and rights requests may be sent to legal@beaconrelay.dev. The competent French supervisory authority is the Commission nationale de l’informatique et des libertés (CNIL).