Privacy

What Buildiary stores, what stays private, and what you choose to share.

Updated 1 October 2026

What we store

Buildiary stores your account identity, username, profile details and photos, projects, progress entries, and uploaded images so you can keep and manage your diary. Sign-in is handled by Auth0; Buildiary does not receive your password.

We also keep recent diary changes and agent requests in a private interaction log, and record connected agents' reported product names, connection methods, and activity times. These records help you understand what changed and which agents have reached your account.

Private and public content

Projects start private. Publishing a project makes its public details, progress entries, gallery, and attached images visible to anyone, including search engines. Your next step, repository URL, and private interaction log are not included in public project pages.

Profile visibility is separate. A public profile shows your name, bio, photos, location, and links. A private profile still shows your username and any projects you have published.

Making content private removes it from public pages and discovery. It cannot recall copies someone has already saved or search engines have cached. Uploaded image addresses are direct file links: someone who already has an address may still open it while the file exists. Avoid uploading sensitive images.

Connected agents

An agent you authorize can read and change your projects and progress through the access you grant. You can turn off Agent access in your diary. Anything you send to your agent is also subject to that agent provider's own privacy practices. Buildiary does not run a language model to generate your diary entries.

Browser storage and service providers

Your browser stores sign-in information, a cache of your own diary data, and your preferred project view. Diary caches are cleared when you sign out or switch accounts. On a shared device, sign out when you finish.

Auth0 provides sign-in, Convex stores and serves diary data and images, and Vercel hosts the website. The site uses Vercel Web Analytics for page-view statistics, which can include visited addresses, referrers, device information, and approximate location. Vercel describes its analytics collection in its privacy documentation.

Feedback and retention

Feedback is sent to the developer with your message, the page address, your account when signed in, and an optional reply email. You can remove the email before sending. Feedback is not public.

Deleted projects and progress entries stay in recoverable trash, with their images and saved versions, until you permanently delete them on the website. There is no automatic trash expiry. The interaction log keeps a bounded recent history rather than every request forever.

Questions about your data

Buildiary is maintained by @tinkr. Use Feedback in the header or footer for privacy questions or requests about your account. Include a reply email if you want an answer. Do not send passwords, access tokens, or sensitive diary content in feedback.