This is a draft and has not been reviewed by a lawyer. It is written from what the software verifiably does, which is the half we can be accurate about. Whether it satisfies Article 28 GDPR, the DPDP Act, or any other law is a question for counsel, and neither BuildFrame Technologies Private Limited nor this page answers it. If you need a signed DPA before you can launch, write to hello@buildframe.tech and say so — do not rely on this page as executed.
This agreement supplements the Terms of Service and applies where BuildFrame Technologies Private Limited processes personal data on your behalf. Where it conflicts with the Terms, this document governs for data protection.
1. Roles
You are the controller of shopper photographs. BuildFrame Technologies Private Limited is the processor. Section 5 of the Terms already places the consent obligation on you, and this document does not move it.
For your own account data — your name, email, workspace and billing records — BuildFrame Technologies Private Limited is the controller, and this agreement does not apply to it. The Privacy Policy covers that relationship.
2. Subject matter and duration
| Subject matter | Generating a synthetic image of a garment on a person |
| Nature of processing | Automated screening, image generation, short-term storage, deletion |
| Duration | For the life of your account, and for each photograph the window in §4 |
| Data subjects | Shoppers who use try-on on your storefront |
| Categories | Facial and body photographs, generation metadata, consent records, a browser-local rate-limit identifier |
Some jurisdictions treat a facial image as biometric data with its own written-consent rules and statutory penalties — Illinois and Texas among them. Whether they apply to you is your assessment. We are telling you the category exists, not advising you on it.
3. Instructions
BuildFrame Technologies Private Limited processes shopper photographs only to provide try-on, and on your instructions. Your use of the service is the instruction; there is no separate mechanism for issuing others.
Photographs are never used to train a model — not by BuildFrame Technologies Private Limited, and not by the model providers under the terms we contract on. They are not sold and not licensed.
4. Retention and deletion
You choose the retention window per workspace: 1, 3 or 7 days. An hourly job deletes the stored bytes first and marks the record afterwards, so a row is never reported as deleted while the file still exists.
One honest exception. Photographs stored before 7 September 2026 carry no expiry date and are not reached by that job. They are deleted on request.
5. Data subject requests
Two paths, and you can use either.
- Through the API.
DELETE /api/tryon/v1/customers/:externalUserIderases a shopper from our records and returns a receipt saying what was removed. You do not need to wait for us. - Through us. Write to hello@buildframe.tech and a person will run it and confirm.
Either path removes the photograph, the result image made from it, and the identifiers tying a record to that person. It does not remove the fact that a generation happened or what it cost — that is your billing record, not the subject's personal data, and erasing it is not something a subject request entitles anyone to.
What is outside this, stated rather than omitted: results returned inline by POST /api/generate are not stored by us at all. There is nothing to erase and nothing to produce, which is a good property and a real gap in any records request you receive, because we cannot produce what was never kept.
6. Sub-processors
| Sub-processor | Purpose |
|---|---|
| OpenAI | Image generation, and the content screening that runs before it |
| Supabase | Database and the private image bucket |
| Vercel | Hosting, and the logs a server necessarily writes |
| Resend | Transactional email |
| Stripe, Razorpay | Payment for credits. Card details go to them, never to us |
| Only where a user chooses "Sign in with Google" |
Shopper photographs reach OpenAI and Supabase only. They do not reach the payment, email or sign-in processors.
BuildFrame Technologies Private Limited is established in India and several sub-processors are outside it, so personal data is transferred internationally. The transfer mechanism has not been papered, and that is a gap rather than a position: it is one of the things a reviewing lawyer should settle first.
Changes. We will give notice of a new sub-processor on this page. There is no automated notification and no formal objection window built into the product today.
7. Security
- Photographs are stored in a private bucket, never a public one. Reads are signed links that expire in ten minutes, served with caching disabled so a deleted file cannot keep being served from an edge.
- Provider API keys are encrypted at rest; the database never holds one in the clear.
- Every shopper photograph is screened before any generation model sees it, and the check fails closed — if screening cannot reach its provider, the try-on is refused rather than allowed through.
- Access to the admin surface is authenticated, and platform-wide data is restricted to the host role.
Not claimed: there is no third-party exception tracking, no formal penetration test, and no certification of any kind — no ISO 27001, no SOC 2. If your procurement needs one, we do not have it.
8. Breach notification
BuildFrame Technologies Private Limited will notify you at the address on your account without undue delay after becoming aware of a personal data breach affecting your shoppers, with what is known at the time rather than waiting for a complete picture.
No specific hour count is promised here, deliberately, because there is no automated detection that would let anyone honour one. Monitoring today is application health checks and error logging, not intrusion detection.
9. Audit
BuildFrame Technologies Private Limited will answer reasonable written questions about this processing and provide what documentation exists. There is no audit programme, no third-party report to hand over, and no on-site inspection process.
10. Deletion on termination
When your account closes, shopper photographs still inside their retention window are deleted by the ordinary job. Ask at hello@buildframe.tech for earlier deletion or for a copy first.
11. Contact
BuildFrame Technologies Private Limited, C-1208, ACE PLATINUM, ZETA 1, Greater Noida, Uttar Pradesh 201306, India. Data protection correspondence: hello@buildframe.tech — put "Data protection request" in the subject line, because that address also receives general mail.