Your email address
Between 0 & 8 is written by Jawed Sarwar and published by 0-8 Capital GmbH. It is a publication of ideas and research, not a subscription to transaction or investor communications. Signing up is optional. We do not import business contacts as subscribers.
Publisher and controller
0-8 Capital GmbH is responsible for the publication and for processing subscriber information.
0-8 Capital GmbH
Planegger Str. 32A
81241 München, Germany
Represented by Jawed Sarwar, Managing Director. For newsletter and privacy questions, email notes@jawedsarwar.com. You can also contact the company at jawed@0-8.capital.
Confirmation and consent
We use your email address to send a confirmation message and, once you confirm, occasional notes. You agree to receive the notes when you submit the signup form and then confirm through a link sent to your email address. We record the consent wording and version, request time and confirmation time. Unconfirmed subscriptions do not receive newsletters. We do not require your name or any information about your business.
The newsletter is based on your consent (Article 6(1)(a) GDPR). You may withdraw consent at any time without affecting processing that was lawful before withdrawal. Visiting and reading the website does not require a subscription.
Storage and delivery
The website is hosted on GitLab. The signup form sends subscriber information directly to our AWS backend, rather than storing it in the website repository. Subscriber records are held in a private, encrypted Amazon S3 bucket in Frankfurt (eu-central-1); AWS Lambda handles subscription requests and Amazon SES delivers email. AWS also handles delivery feedback and operational logs. Your receiving email provider processes the messages delivered to your mailbox.
0-8 Capital GmbH uses AWS and GitLab under their applicable data-processing terms. AWS provides a GDPR Data Processing Addendum, including Standard Contractual Clauses. GitLab provides a Data Processing Addendum and Standard Contractual Clauses.
Selecting Frankfurt for the newsletter backend does not mean all provider operations or email delivery remain exclusively in Germany. GitLab describes US hosting and international processing in its privacy statement, with reliance on applicable Data Privacy Framework arrangements and Standard Contractual Clauses where required. Email delivery and provider support may also involve processing outside the EEA. Applicable safeguards depend on the provider and processing involved; contact us for information about the safeguards relevant to your data.
The website does not store your email address in browser storage. We do not enable newsletter open or click tracking, sell subscriber lists, or share them for third-party marketing.
To limit automated requests, we temporarily store keyed identifiers derived from requesting IP addresses, rather than raw IP addresses. Rate-limit records expire after two days, subject to AWS lifecycle processing. Unconfirmed requests are removed after 30 days by a daily cleanup task.
Security, abuse prevention and respecting suppression requests serve our legitimate interests in operating the publication safely (Article 6(1)(f) GDPR). Infrastructure providers may process connection and technical data separately; keyed application records are not a claim that providers never process IP addresses.
Unsubscribing
Every email includes an unsubscribe link. After unsubscribing, the active email record is replaced with a minimal suppression record: a keyed identifier, status, reason and unsubscribe timestamps. This prevents future sending without retaining your address in that record. These identifiers are pseudonymous, not anonymous. Hard bounces and complaints are also suppressed. An email already being sent may still arrive.
If you explicitly ask to return after a voluntary unsubscribe, we can send a fresh confirmation. You remain suppressed until you confirm. During this request, we temporarily hold your email address and fresh consent details. The link expires after 24 hours, and the daily cleanup removes expired request details while preserving suppression. Another unsubscribe cancels the request. Bounce and complaint suppression cannot be overridden by this process.
Retention
Active subscription details are kept while the subscription remains active. Unsubscribing removes your address and consent details from the active record, subject to the fresh-confirmation process described above.
We keep minimal suppression and per-campaign delivery records for as long as needed to respect unsubscribe requests and prevent unwanted or duplicate messages. These records do not contain the email address itself, but their keyed identifiers remain pseudonymous personal data. There is no automatic expiry for these records. We review their continuing necessity at least annually and remove records when no longer needed, subject to any applicable legal obligations. We do not remove a suppression or duplicate-send safeguard while it is still required for ongoing sending.
Unconfirmed signup requests are removed after 30 days by daily cleanup. Fresh opt-in requests expire after 24 hours and their temporary details are removed by daily cleanup. Keyed rate-limit counters expire after two days, subject to S3 lifecycle processing.
Our newsletter’s Lambda operational logs have a 30-day retention setting. Expired logs are removed through AWS’s retention processing, which may take additional time. Failed feedback messages may contain an address and expire from the failure queue after 14 days. AWS and GitLab may separately retain service, security, account or legally required information under their own applicable terms and privacy notices.
Questions and requests
Contact notes@jawedsarwar.com to request access, correction, erasure, restriction or portability of your information, as applicable. You may object to processing based on legitimate interests and may complain to a competent data protection supervisory authority. Withdrawing newsletter consent is also possible through the unsubscribe link in every message.
Last updated: 31 August 2026.