Who is responsible
Data controller: Tigran Varazhian (structivio). Privacy contact: tigran.varazhian@struct-i-vio.com.
The concept creator named on each product page may receive the signup information to provide the updates you requested.
What we collect
- Your email address and the time/version of your consent.
- The concept and page version you joined.
- Limited campaign attribution such as UTM parameters or ad click identifiers, when present.
- The referrer hostname and landing path, not your full browsing history.
- A one-way keyed hash derived from the request IP for short-window abuse prevention; the application does not store the raw IP in the waitlist table.
Purpose and legal basis
We use the data to record interest in a specific concept, measure which acquisition messages produce consented interest, prevent duplicate/spam submissions, and send the product updates you requested. The legal basis for product-update emails is your consent. You may withdraw it at any time.
Processors and transfers
The pilot uses Vercel to serve the application and Supabase to store project and waitlist records. Their infrastructure may process routine network metadata under their own service terms and data-processing arrangements. Azure AI is used only in the local creator flow; signup emails are not sent to the model.
Retention and sharing
Waitlist records are intended to be kept only while the concept test and its update cycle are active, and no longer than 12 months after the last relevant update unless law requires otherwise. We do not sell waitlist data. Deletion and export requests are handled through the privacy contact above.
Your choices and rights
You can withdraw consent and request access, correction, deletion, restriction, or portability where applicable. You can also object to direct marketing and lodge a complaint with your local data-protection authority. Withdrawing consent does not affect processing that occurred before withdrawal.
No purchase and no automated decision
Joining a waitlist does not create an order, reservation, account, or right to receive a product. The pilot does not make legal or similarly significant automated decisions about subscribers.
This operational notice is a starting point for the pilot and should be reviewed against the final operator identity, contracts, markets, and retention process before paid acquisition.