Who we are
Your Demos ("ydemos", "we") turns an agency's brief into a working, white-labelled demo. This policy explains how we handle personal data for agency users of our platform, for people who view demos that agencies share, and for visitors to this website.
Controller and processor roles
- We are the controller for agency account administration, billing, security, support and service-operation records.
- The agency is the controller and we are its processor for client viewer analytics and CX-Pen feedback collected on that agency's shared demos, and for personal data contained in briefs the agency submits. Our Data Processing Agreement covers this processing.
If you viewed a demo an agency shared with you and have a privacy question, contact that agency first. We'll help them answer it.
What we collect
| Category | Examples | Source |
|---|---|---|
| Agency account data | Name, business email, agency name, role, sign-in events | You |
| Billing data | Billing contact, payment records, receipts, refund decisions (card details are handled by our payment provider) | You, payment provider |
| Briefs and attachments | Project name, app description, roles, features, references, uploaded files | You |
| Generated artefacts | Blueprints, brand assets, app source, fictional seed data, file bundles | Our service |
| Client viewer analytics (consent only) | When a demo was opened, session duration, screens viewed, anonymous session ID | Viewer's browser, after consent |
| CX-Pen feedback | Note text, drawing, the screen and element it's anchored to, submission time | Client viewer |
| Walkthrough state | Shared route and control state during a live walkthrough | Participants |
| Support and security records | Support messages, access logs, safety-review records | You, our systems |
We ask agencies not to submit unnecessary sensitive personal data. Demos use fictional people and records only. If real personal data is detected in a brief, it's kept out of generated content or the run is blocked for review.
Why we use it
- To provide the service: accept briefs, run builds, deliver artefacts, host and share demos, show feedback.
- To bill, process refunds and review free-first-demo eligibility.
- To keep the service safe: abuse screening, injection defence, access control, incident response.
- To support you and send service emails (run started, blocked or failed, delivery ready).
- To improve reliability and quality, using operational metrics and, only after human curation and removal of unnecessary identifying information, review outcomes.
Draft lawful bases (to be validated by counsel): performance of our contract with the agency; legitimate interests in security and service improvement; consent for optional client viewer analytics; legal obligation for tax and accounting records.
Client viewer analytics and cookies
Before any optional analytics run, people viewing a demo see two options of equal prominence: Accept analytics and Decline analytics. Until they choose, nothing is collected for analytics: no opens, durations, screen views, analytics identifiers or pixels.
- Declining never blocks access to the demo.
- The choice can be changed or withdrawn at any time. Withdrawal stops collection immediately.
- The choice expires after 180 days, and we ask again.
- Sessions are anonymous by default, measure activity only while the page is visible, and end after 30 minutes of inactivity. We never infer identity from activity.
- We use first-party analytics only. No advertising pixels, fingerprinting, cross-site identifiers, cookie walls or analytics vendors that use data for cross-context advertising.
Strictly necessary storage for sign-in, security and delivering the demo is kept separate from analytics. If our consent service is unavailable, the default is no analytics.
AI processing and training
Builds are produced by large language models running through our server-side systems, with retrieval scoped to your workspace and run. Content from one workspace is never used to fill gaps in another.
We don't train our own or third-party general-purpose models on your data by default. Any training or reuse beyond delivering your service would require separate, specific, affirmative opt-in that names the data, purpose and provider. That choice is independent of purchasing a demo. We only send data to a model provider whose terms and configuration support these restrictions. Otherwise, that data flow is blocked.
Service providers
We use subprocessors for model generation, embeddings and reranking, vector and relational storage, hosting and delivery, authentication, email, support and payments. Before launch we'll publish a versioned subprocessor register listing each provider, the service it provides, the data categories, the processing location, the transfer mechanism and how we notify changes. We name a provider only after verifying its terms and configuration.
Retention
| Data | Retention |
|---|---|
| Raw client viewer analytics events | 90 days from collection, then deleted |
| Daily aggregates without viewer identifiers | 12 months, then deleted |
| Analytics choice and minimum consent evidence | Until 30 days after the related raw events are deleted |
| Briefs, attachments, artefacts, CX-Pen feedback, workspace records | While the workspace is active. After verified workspace deletion: production copies deleted within 30 days, backups expire within 35 days |
| Billing and tax records | As required by law |
Hosting expiry for inactive demos (link disabled after 90 + 30 days without agency activity) doesn't by itself delete briefs or artefacts. Legal holds are approved by counsel and never silently extend ordinary retention.
Your rights
Depending on where you live, you may have the right to access, correct, delete, restrict or object to processing of your personal data, to data portability, and to withdraw consent at any time. You may also complain to your data protection authority (for example, the ICO in the UK). Agency users can make requests through the contact details below. Client viewers should contact the agency that shared the demo, and we'll help that agency respond.
California notice
We collect the categories listed in section 03 for the purposes in section 04 and keep them for the periods in section 08. We don't sell personal information, and we don't share it for cross-context behavioural advertising. California residents can request access, deletion and correction, and we won't discriminate against anyone for exercising these rights.
International transfers
We launch in the United States first, then the United Kingdom and European Union. Where personal data moves across borders, we rely on transfer mechanisms appropriate to the actual deployment, which will be set out in our DPA and subprocessor register once verified.
Security
Each build runs in an isolated, run-scoped sandbox with outbound network access denied by default. Data is separated by workspace and run, role permissions are enforced on the server, and human access is limited to people who need it for support, safety or operations, with access logged. Generated file bundles contain no credentials or secrets.
Children
ydemos is a business service and isn't directed to children. We don't knowingly collect children's personal data.
Changes and contact
We'll post updates here and notify agency owners of material changes. Privacy questions and requests: privacy@ydemos.com, or use our contact form and choose "Privacy request".