BeaconRelay
TermsPrivacyDPARetention
Home
Legal centerTerms of ServicePrivacy PolicyData Processing AgreementData Retention Schedule
Version2026-09-30legal@beaconrelay.dev
Operational commitment

Data Retention Schedule

This schedule states what BeaconRelay deletes automatically, what remains as verifiable evidence, and how retained service records are handled.

Effective
2026-09-30
Contact
legal@beaconrelay.dev

1. Enforced payload windows

Trial7 days
Startup7 days
Growth14 days
Business30 days
Enterprise90+ daysContracted

The clock begins when BeaconRelay receives the event. Cleanup runs periodically. When an event is Delivered or Dead Letter and its deadline has passed, BeaconRelay erases the encrypted Salesforce payload and encrypted receiver response bodies. If an event is still Pending, Retrying, or Blocked, content remains temporarily because it is required to complete delivery; it becomes eligible for erasure after reaching a terminal state. An expired Dead Letter cannot be redriven.

2. What remains after payload expiry

BeaconRelay preserves non-content evidence so customers can prove and diagnose transport without retaining the original body: event ID, channel and object/operation labels, replay identity, timestamps and states, SHA-256 fingerprint, signature and signing-key ID, delivery attempts and HTTP status, failure classification, route history, incidents, signed receipts, and payload-expiry timestamp.

Encryption is not deletion

Before expiry, payload and captured response content are stored only in encrypted form. At expiry the encrypted content itself is removed; metadata and cryptographic proofs cannot reconstruct it.

3. Category schedule

CategoryCurrent ruleTrigger
Salesforce payload and receiver response content7, 14, 30, or contracted 90+ days; terminal events onlyPlan at event receipt and terminal state
OAuth access and refresh tokensUntil access revocation or Salesforce organization deletionCustomer action or authorization failure
Organization configuration, topics, destinations, events, attempts, incidents and proofsWhile the organization exists; deleted from BeaconRelay’s live database when the organization is deletedCustomer organization deletion
Account profile and legal acceptance recordWhile the account exists and as required to establish the agreementAccount closure request and legal obligations
Billing and invoice recordsAs required for subscription administration, tax, accounting, disputes, and applicable lawSubscription/account termination plus statutory period
Transactional email and delivery auditWhile needed for security, delivery diagnosis, and account administrationPurpose completion or account closure instruction
BackupsGermany-hosted disaster-recovery copies under controlled rotationBackup lifecycle and secure expiry

4. Organization deletion

Deleting a Salesforce organization stops its listener, attempts remote topic and OAuth revocation, and deletes its topics, receiver, gateway events, delivery attempts, route changes, replay cursor, monitoring events, and incidents from the live BeaconRelay database. Remote revocation can fail if Salesforce is unavailable; BeaconRelay reports that outcome.

5. Account closure and legal holds

Self-service account deletion is not currently available. An account owner may request closure, export guidance, or deletion at legal@beaconrelay.dev. Provider may retain narrowly scoped records when required by law, to resolve payment disputes, enforce the agreement, or preserve evidence under a legal hold. Restricted records will not be used for unrelated purposes.

6. Backup and deletion safeguards

OVH SAS hosts production storage and disaster-recovery backups in Germany. Backups are protected to the same security standard as production data, used only for resilience and recovery, and removed through controlled rotation. A deletion from the live service propagates as backup generations expire; backups are not restored to circumvent a completed deletion request. BeaconRelay does not represent that account, billing, or integrity metadata is deleted on the shorter payload-retention schedule.

BeaconRelay

Reliable, replayable and verifiable Salesforce events.

Product documentation