RAW DATA CLUB / PRIVACY
Resource request privacy notice
Updated 12 November 2026
1. Who is responsible
Raw Data Club is operated by Felipe da Rocha Vieira Mattos as an individual controller based in Ontario, Canada. For questions about personal information or to make a privacy request, contact [email protected].
2. Information collected
The resource request form collects your email address and, if you provide them, your professional role and brand/company. The request record will also contain the resource identifier and title, receipt time, a random request identifier used to prevent duplicate retries, accepted-request status, campaign source/medium/campaign labels supplied with your visit, and your marketing choice.
Every request records the marketing wording version. If you opt in to research updates, it also records the consent time. An unchecked choice has no consent timestamp. The system does not verify ownership of the email address. Please do not submit sensitive information or another person's details.
3. Purposes and choices
Email and request identifiers are used to record and administer resource requests. Optional role and company information help us understand the professional audience. Campaign source, medium and campaign labels help us understand which campaigns generate requests. Automatic validation and security checks protect the request system against abuse. These are distinct purposes. Marketing permission is requested separately and is not a condition of receiving the resource.
4. Required and optional fields
Email is required by RDC's chosen request form; professional role and company are optional. Email is not technically necessary to serve the static PDF, and no delivery email is sent. After an accepted request, the page attempts to start the PDF download and provides a download button if your browser blocks it. Personal email domains are accepted. The spam check must succeed before a request can be accepted. Declining marketing does not prevent access.
5. Optional marketing permission
The research-updates checkbox is unchecked by default. Selecting it records a separate, explicit choice. This system sends no marketing emails and does not enroll you in a mailing service. A request record alone is not proof of a current subscription. Future research campaigns may include only contacts with valid explicit opt-in after withdrawals have been reconciled. No campaign sending is authorized.
You can withdraw marketing permission by contacting [email protected]. Withdrawal does not affect access to the resource. Leaving a later request unchecked does not itself withdraw an earlier choice.
6. Hosting, storage and disclosures
Cloudflare Pages and Pages Functions deliver the website and process form requests. The application sends accepted request records to Supabase for private database storage. Browser database roles are not permitted to read or write lead records directly. Authorized account administrators and the server credential can access records; the final administrative access list is controlled separately.
Cloudflare Turnstile processes browser security signals, including IP address, user-agent and TLS fingerprint information, to distinguish people from bots. Cloudflare describes acting as a processor for website protection and as a controller when improving Turnstile's bot detection. See the Turnstile Privacy Addendum and Cloudflare Privacy Policy.
The application does not place IP addresses or spam-check tokens in lead records or send a visitor IP in its server verification call. Hosting and database providers can still process technical network information and operational logs. If you email us directly, your message is also handled by the email service used for that correspondence.
7. International processing
Resource requests from this website are stored in the Raw Data Club Supabase project in us-east-2, Ohio, United States. Cloudflare operates a global network. Provider support, operational metadata and other service processing may occur outside the primary database region, including outside Canada. Information processed abroad may be subject to lawful access under the laws of those jurisdictions.
Provider information is available in Supabase's residency and transfers explanation, its Data Processing Addendum, and Cloudflare's Data Processing Addendum. These links describe provider terms; this notice does not assert that a particular transfer mechanism has been verified for the RDC account.
8. Retention
Felipe Mattos has accepted operational responsibility for retaining resource-request records for 12 months from submission, reviewing them monthly and deleting expired records within 30 days after expiry. Deletion is manual; no scheduled automatic deletion or anonymization is implemented. Marketing consent does not extend a resource request’s retention period. Separate rules for consent evidence and withdrawal records must be approved before marketing begins. Removing an active database row does not necessarily remove it immediately from provider backups or retained operational logs.
Abuse-control storage contains keyed email digests, counters and expiry times rather than raw email addresses. These digests are pseudonymous. Buckets stop counting at their expiry, within a maximum 15-minute window, and are purged on later requests or through maintenance.
9. Privacy requests
Contact [email protected] to request access, correction, deletion or withdrawal of marketing permission. Depending on the law that applies, you may have additional rights, such as objection, restriction, portability or a complaint to a competent privacy authority. We may ask for proportionate information to verify your request and protect other people's information.
10. Cookies, security scripts and measurement
The reviewed website code does not install advertising pixels, third-party analytics SDKs or its own tracking cookies, local storage or session storage. Cloudflare may add an email-address decoding script to delivered pages; it was observed on the existing live homepage, rather than established by this staging source review. Provider security features and Turnstile can process technical signals and may use security-related browser storage or cookies according to their settings. This is not a claim that every website visit is cookie-free.
Resource metrics are disabled. The implementation supports separately enabled daily totals by resource and event for page views and download-link clicks, without visitor identifiers in those counters. Accepted request rows count submissions separately. A click does not prove a completed download, opening or reading. The browser sends resource event requests only when the server explicitly reports metrics enabled. Metrics remain disabled. Infrastructure logs and Access authentication cookies are separate from these counters. Links to LinkedIn, Instagram and external sources take you to services with their own privacy practices.
11. Security and automatic checks
Requests pass automatic field validation, a bot check, a hidden spam field, rate limits and retry checks. These can reject or delay a request. Contact the privacy email if you need help with your information or an incorrect rejection. Server credentials stay outside browser code, and database permissions restrict lead access. No technical measure guarantees absolute security.
12. Updates
We will revise this notice when the request system, providers or privacy practices change and identify the updated version. Material changes will be communicated where required. This version is dated 12 November 2026.
