Privacy overview

Only the data needed to move an announcement.

This notice explains how ReleaseFast handles information across company recognition, ordering, editorial review and fulfilment.

Updated 31 August 2026

Controller and contact

ReleaseFast is a trading name operated by Top of the World Reizen, Dutch Chamber of Commerce number 92357989. The controller address is Kraaipanstraat 11B, 1091 PE Amsterdam, the Netherlands. For privacy questions and rights requests, use the controller postal address above. Public email support is currently unavailable; check contact availability for its current status.

Information collected

ReleaseFast stores public company facts and source URLs, customer corrections, package and credit records, contact and billing details returned by Stripe, announcement intake content, supporting evidence references, draft versions, approval decisions, order status and supplier report details. Stripe handles payment information; ReleaseFast does not store full card details.

Approval may include a one-way hash derived from an IP address where legally appropriate. Raw IP addresses are not stored in the approval record. Bearer-token hashes are stored for verification. Encrypted recovery material is also stored where needed for reliable secure-link delivery and purchase access. Private workflow pages are marked no-store and noindex.

How information is used

Information is used to identify the company, create and review the requested release, verify claims, obtain approval, coordinate third-party distribution, provide status and report links, prevent abuse and maintain an operational audit trail. Depending on the activity, processing is necessary to perform or prepare the service contract, meet legal obligations, or pursue legitimate interests in secure fulfilment, record-keeping and abuse prevention. Consent is used where applicable law specifically requires it.

Service providers

ReleaseFast may use Firecrawl for server-side public website extraction, Stripe for hosted checkout and payment events, Brevo for transactional email, Neon for database hosting, Vercel for application hosting and anonymized, cookieless Web Analytics, and a third-party distribution supplier for upstream submission. Each provider receives only the information needed for its role.

Transactional-email requests set Brevo's per-recipient open-pixel consent field to false, which asks Brevo to anonymize open events when that account feature is enabled. Brevo may still count opens in aggregate and route links through its delivery infrastructure according to the account settings.

Safeguards and retention

Provider keys remain server-side. Submitted URLs are normalized and checked against private networks. Payment webhooks are signature-verified. Sensitive workflow links are purpose-scoped and expire. Recovery tokens are encrypted at rest; plaintext bearer tokens are not persisted.

Order-record retention is governed by fulfilment, accounting, dispute, security and applicable legal requirements.

Questions and rights

Depending on applicable law, business contacts may have rights to access, correct or delete personal information, restrict or object to processing, receive portable information, or complain to a supervisory authority. A request process must protect against unauthorized disclosure, including identity verification where appropriate.

No advertising profile.

The ReleaseFast analytics wrapper accepts only a small allowlist of operational events and does not send emails, order IDs, announcement text or raw URLs as analytics properties.