Your writing is kept in your account so it follows you to every device, with a copy in the browser you use. We don’t read it, sell it or share it, and we never train AI on it. Everything we store, and everything that leaves your device, is listed here.
Who is responsible
BUILD/POV (“we”) runs Buildblur and is responsible for the personal information described here. Contact: preetham@buildpov.com.
Your account and your writing
You sign in to use the studio, with Google or a six-digit code sent to your email. Everything you write in Buildblur (projects, scenes, characters, world notes, the whiteboard, ideas, your journal, saved versions and the authorship record) and your studio settings, writing sessions, path progress and rewards are kept in your account in our cloud database (Appwrite). Each item can be read only by your account. We don’t read your manuscript.
The browser you use keeps a copy so the studio is fast and works offline; it’s removed when you sign out. If our account service can’t be reached, you can write in the browser for now, and it’s added to your account the next time you sign in. The cookies and storage page lists exactly what is kept in your browser.
What leaves your device, and when
| When | What | Where it goes |
|---|---|---|
| You use an AI feature | The passage you asked about, the parts of your world it needs (character and world-note details, short measurements of your writing style), your instruction, and your IP address | Our AI endpoint on Vercel, then OpenRouter and the AI model provider it routes to; when that is busy, Groq or Cloudflare Workers AI instead |
| You sign in | Your email address and name; with Google, the basic profile Google shares (name, email) | Our cloud database (Appwrite); Google, if you choose it |
| You write, and while you’re signed in | Your writing and everything listed above, kept in step with the browser you use | Our cloud database (Appwrite), readable only by your account |
| You create a share link | A copy of that project | Our cloud database (Appwrite), shown to anyone with the link |
| You load any page | Your IP address, browser and device details, the page requested | Our host, Vercel |
| You view a page | A page-view count through Vercel Web Analytics: the page, the referring site, country, and device type. No cookies; visitors are counted with a hash that resets every day and can’t identify you | Vercel |
| You visit the site or use the studio, unless you’ve switched it off | Anonymous usage counts: the name of what happened (“started a story”, “exported a PDF”), a few numbers (a word count, a format), the page, the screen size, a random id for your browser, your country, and your account id if you’re signed in. Never your writing, titles or names from your story | Our cloud database (Appwrite), readable only by the Buildblur team |
| You email us | Your email address and what you write | Our email provider |
What we do with it
- AI requests are passed on to produce an answer. We don’t store the text. We count how many AI asks you’ve used this month: against your account if you’re signed in, or, if you aren’t, against a one-way hash of your IP address, so the address itself is never stored. The count is kept until the month is over. Our endpoint also holds your IP address in memory briefly to limit requests per hour, so the free service stays usable for everyone.
- Your account and your writing are kept so you can sign in and find your work on any device, until you delete the account. Each document is readable only by your account. We don’t read your manuscript.
- Share links are stored so the link works, until you ask us to take it down.
- Web requests are handled by Vercel to serve the site and keep it secure; Vercel keeps standard logs for a limited time under its own policy.
- Usage counts show us what people use and where they get stuck, so we know what to fix. They’re kept for up to 13 months. Switch them off any time in the studio under Settings → Privacy; we also respect your browser’s Do Not Track setting.
- Emails are used to answer you.
We don’t use your writing to train AI, we don’t read your manuscript, and we don’t run advertising or advertising trackers. The people who run Buildblur can see your email, when you joined and last visited, how many stories and words you have and how many AI asks you’ve used, to run the service and help you. Never the stories themselves.
Your account
Sign out from the studio at any time; signing out removes the copy of your writing from that browser, so a shared computer keeps nothing. To delete your account and your writing, use Settings → Account → Delete account; that also closes the account. Export first if you want to keep anything. To have the sign-in record itself erased, email preetham@buildpov.com from the address you signed up with. Accounts made before 26 July 2026 work the same way.
Who processes it for us
- Vercel: hosting and the AI endpoint (United States and other regions).
- OpenRouter: routes AI requests to model providers (United States).
- Groq and Cloudflare Workers AI: answer AI requests when OpenRouter's free models are busy (United States). Neither trains models on what it is sent.
- AI model providers reached through OpenRouter. Buildblur uses free models, and which provider answers can change from request to request. Some providers of free models log prompts or use them to improve their models under their own terms. Please don’t send anything you wouldn’t put in an email.
- Appwrite: accounts, your writing and settings, and share links.
- Google: only if you choose “Continue with Google” to sign in.
Some of these companies are outside your country, so your information may be processed in the United States and elsewhere, under the safeguards those companies provide.
Why we’re allowed to
We process this information to provide the features you ask for (your account and sync, AI requests, share links), because we have a legitimate interest in running a secure, working service (web logs, rate limits), and to answer you when you write to us.
Your rights
Depending on where you live (for example under India’s Digital Personal Data Protection Act, the GDPR in the EU and UK, or US state laws), you can ask to access, correct or delete personal information we hold about you, object to or restrict how we use it, withdraw consent, and nominate someone to act for you. Email preetham@buildpov.com. You can also export or delete your writing yourself from the studio at any time. You can also complain to your data protection authority.
Children
Buildblur isn’t aimed at children under 13, and we don’t knowingly collect personal information from them. If you believe a child has sent us information, email us and we’ll delete it.
Security
Each document in your account can be read only by your account. The site is served over HTTPS, service keys are kept on the server, and we keep what we hold to a minimum. See security.
Changes
If what we store or what leaves your device changes, we’ll update this page and say so in the app before it happens.
Questions about this page: preetham@buildpov.com. See also the legal centre.