Portfolio Brief home

Privacy Notice

Effective date:

Who operates Portfolio Brief

Portfolio Brief is operated by Sizhe Chen, an individual responsible for the personal data described in this notice. Contact sizhechenlove@gmail.com for privacy questions or requests about your information.

What we collect and why

Waitlist. When you register interest, we record your email address, selected country, acknowledgement and first registration time. Where applicable, we also record your plan interest, where you joined from on the site and the price shown. We process this information based on our legitimate interests in maintaining the waitlist, recognizing repeat registrations and assessing early product and pricing demand. We link your registration to an internal record so we can recognize it. This does not open a sign-in account or grant beta access. Repeating a registration does not reset its first registration time.

Website and API operation. Hosting services process connection and request information, such as IP address, request timing and response status. We process this information based on our legitimate interests in keeping the service available, preventing abuse and diagnosing faults.

Contact and rights requests. If you email us, we use your address, message and relevant context to respond, based on our legitimate interest in handling enquiries. We process privacy rights requests to comply with applicable data protection law. We keep a minimal record of how we responded where required by law or where necessary for our legitimate interest in demonstrating that response.

Registering interest does not subscribe you to marketing or trigger an automatic email. This release does not use optional analytics, advertising tags or tracking pixels. If these practices change, we will update the notice and provide any choices required before the new processing starts.

Who receives the information

Cloudflare Pages hosts the website and handles visitor requests. The website sends registrations directly to the separate API endpoint; the Pages application does not proxy those submissions. Render runs the API in Frankfurt. Supabase provides database storage and backups, with the primary database configured in Frankfurt. Gmail, our personal contact mailbox service, handles incoming and outgoing contact email.

The Render service and primary Supabase database are configured in the EEA. The operator is based outside the EEA, and Cloudflare, Render, Supabase and Gmail are global services that may involve routing, processing or access outside the EEA. Where applicable, the cloud infrastructure providers rely on their standard data transfer safeguards, such as Standard Contractual Clauses or an applicable data privacy framework. The personal Gmail mailbox is subject to its standard service terms. You can contact us for information about the safeguards that apply to a transfer.

How long we keep information

We keep waitlist data for up to 90 calendar days from the first registration. We keep ordinary enquiry emails for up to 30 days after closing the enquiry and a minimal record of a privacy rights request outcome for up to six months after closing the request. After removing a waitlist record, we retain its linked internal record only where an independent purpose requires it.

Render’s current plan retains platform logs for seven days. Under the current Supabase plan, daily database backups expire on a seven-day cycle. Deleting a record from the live database does not modify backups that have yet to expire. Email deletion is also subject to the mail provider’s standard recovery process.

Your choices and rights

Email sizhechenlove@gmail.com to request access, correction or deletion. Please describe what you want us to address without sending unnecessary documents. We may ask for proportionate information to verify your identity.

Where applicable, you may also have rights to restrict processing, receive a portable copy, object to processing based on legitimate interests, or complain to the competent data protection authority. We will explain what we have done in response to your request, including any applicable limits on deletion.