Privacy and data protection
Privacy notice
This notice explains what Breeze Studio collects, why it is used, where it comes from, and the choices available to people who use the Location Site builder.
1. Who is responsible
Breeze Studio is operated by Zeno Ventures Pvt. Ltd., A-103, iThum, Sector 62, Noida, Uttar Pradesh 201301, India. Questions and privacy requests can be sent to [email protected].
2. What the public builder collects
- Restaurant search input: the restaurant name or Google Maps link entered into the builder.
- Selected location information: Google Place ID, business name, address, coordinates, listing link, hours, ratings, reviews, photographs, and other listing fields returned for the selected location.
- Generation records: a random status token, job and stage state, timestamps, cost records, checksums, audit results, and generated draft artifacts.
- Security and delivery data: IP address, browser and device information, requested pages, timestamps, and error logs used for rate limiting, security, and reliable delivery.
The current public builder does not ask for a name, email address, telephone number, payment information, or account registration.
3. Internal Studio access
Authorized Breeze operators may use the private Studio console to inspect generation stages, evidence, artifacts, costs, warnings, and publication readiness. The console uses an essential signed session cookie. Access and administrative actions should be logged.
4. Where business evidence comes from
A Location Site draft may use public listing facts from Google Places and source material discovered on an official website or official social profile. A discovered source is not automatically owner-approved or licensed for publication. Studio keeps source, retrieval time, confidence, rights, and approval states separate.
Public reviews remain attributed to their source. Breeze does not claim that third-party reviews, photographs, business facts, or social posts are owned by Breeze or by the restaurant.
5. Why information is used
- To resolve the selected restaurant and create a draft Location Site.
- To preserve source provenance and detect conflicting information.
- To run brand, content, SEO, accessibility, and technical checks.
- To prevent abuse, investigate failures, and enforce cost limits.
- To obtain owner approval before publishing or enabling indexing.
- To comply with legal, security, and provider obligations.
6. AI-assisted processing
Studio may use an AI model for bounded tasks such as proposing a structured creative direction or reviewing a screenshot. Models must receive only the evidence needed for the task. They may not invent business facts, publish a site, approve rights, or make a final release decision. Secrets, private customer exports, and authentication data must not be sent to model providers.
7. Sharing and service providers
Breeze does not sell personal data. Information may be processed by providers needed to operate a requested feature, such as hosting, database, security, email delivery, search, maps, or model providers. Each provider must be limited to its documented purpose and covered by appropriate terms and access controls.
8. Retention and raw evidence
Retention is source-aware. Owner-provided material and approved site revisions may be retained for the customer relationship. Google Place IDs may be retained as stable identifiers. Other provider content is cached, refreshed, or deleted according to the provider contract and applicable law. Credentials, authorization headers, and research session cookies must never be written into artifacts.
The production service will not launch until enforceable retention and deletion jobs exist for every data class. The local prototype is not a substitute for those controls.
9. Publication and indexing
A generated draft is not automatically public, owner-approved, or indexable. Studio distinguishes private drafts, public noindex previews, owner-approved indexable sites, and retired sites. The complete Studio inventory is not intended to be public.
10. Your choices and rights
Depending on applicable law, an individual may ask for access, correction, erasure, consent withdrawal, grievance redressal, or a copy of information associated with them. A restaurant owner may also ask us to remove a draft or correct source attribution. See Data rights and deletion.
11. Security
Studio uses access controls, secure session cookies, least-privilege credentials, rate limits, audit records, and local resource caps. Sensitive secrets are read from local configuration and are not placed in generated files. No method of storage or transmission is completely secure.
12. Children
Studio is a business service and is not directed to children. The public builder should not be used to submit personal data about a child.
13. Cookies and changes
See the Cookie notice for the current browser-storage inventory. If Studio adds owner accounts, forms, analytics, advertising, or new processors, this notice and the product controls must be updated before those features are activated.