This policy covers the Buildryn website, waitlist, beta, application, shared projects, and deployments. It explains what information we handle, why, and how to exercise your rights.
1. Information We Collect
Information you provide or create
- Waitlist: your email address and signup time, together with technical information needed to prevent automated submissions.
- Account and identity: your email address, username, linked Google or GitHub account identifiers, profile details and picture, security settings, and linked Minecraft username and UUID. If you use a password, we protect it with salted, one-way hashing. This allows us to verify your sign-in without storing a readable copy of your password.
- Projects: conversations, uploaded files, source code, saved settings, builds, and repository history. Project content may contain personal information that you or collaborators include.
- Collaboration: invitations, accepted memberships, roles, contributions, and related notifications.
- Deployments: saved project settings, whitelisted Minecraft identities, and temporary world, runtime, and log information needed while a server is running.
- Billing: plan, credit balance and usage, transaction and invoice records, and limited payment details returned by our payment provider. The provider handles full payment credentials.
- Communications: support messages, beta feedback, survey responses, and privacy requests.
Information collected through use
We process IP address, browser and device information, session and security events, request timestamps, service diagnostics, and action or usage records needed to operate, bill, and secure Buildryn. We also use the browser storage described in our Cookie Policy. We do not deploy optional advertising or analytics trackers at this time.
Sign-in providers
Google sign-in requests email and profile access. GitHub sign-in requests read:user and user:email; we may use a temporary GitHub token to obtain a verified email address. These connections support sign-in and account linking. We do not request GitHub repository access.
2. Purposes and Legal Bases
Where applicable law requires a legal basis, we use:
- Contract: to create accounts, provide projects and collaboration, process chat requests and builds, run deployments, manage subscriptions and credits, and answer service requests.
- Legitimate interests: to secure accounts, detect misuse, diagnose faults, maintain reliable services, and use aggregated or de-identified information to improve Buildryn, balanced against users' rights.
- Consent: to send the beta updates you request by joining the waitlist, for optional promotional messages if you separately opt in, and for any other processing for which we ask consent.
- Legal obligations: to keep required tax or accounting records, respond to valid legal requests, and comply with applicable law.
We use waitlist emails for beta updates and invitations, not as a general marketing subscription. Providing information required for an account, payment, or requested project action is necessary to supply that feature; optional profile details and feedback can be left blank.
3. AI and Project Content
To process a chat request, we send the prompt and the files or project context needed for that request to an AI provider. We store conversations and project files in Buildryn so users can continue their work. We do not use customer prompts, files, or outputs to train our own AI models, and we do not opt in to provider training on customer content.
Our current AI provider may retain prompts, responses, and related metadata in abuse-monitoring logs for up to 30 days by default, and longer when legally required or reasonably necessary for safety. Buildryn configures ordinary AI responses without stored output, but retention can differ for particular API features or flagged content. Deleting a Buildryn account does not automatically erase every provider-held copy on the same day. You may ask us for the identity of recipients relevant to your information where applicable law provides that right.
Avoid submitting passwords, private keys, sensitive personal information, or content you lack permission to use. Uploaded files may be sent to the AI provider as context. We may screen requests for prohibited use and restrict flagged content while reviewing it; you may appeal an enforcement decision through the contact below.
5. Service Provider and Contact
The individual identified below provides Buildryn from Portugal. The individual providing Buildryn is your contracting service provider and the controller of the personal information described here. Use the privacy email below for questions or requests about your personal information.
- Legal name: Bruno Medeiros
- Provider address: Rua Bispo Idácio, 5400-303 Chaves, Portugal
- Tax identification number (NIF): 261200879
- Privacy email: privacy@buildryn.com
6. Collaboration and Deployments
Owners choose whom to invite and whether a member may edit or only inspect and download. Contributions made in a shared project remain there if a collaborator leaves or deletes their account. If an owner deletes their account, projects they own become unavailable to collaborators unless the project is transferred to another owner.
A deployment runs a build on a temporary Minecraft server for testing. The server runs on a temporary virtual machine. Accepted members with linked Minecraft identities may be added to its whitelist. When the deployment ends, its virtual machine, world, runtime whitelist, and server logs are deleted. Saved project settings, build history, and build artifacts remain available until the project is deleted, subject to the retention rules below.
7. Retention and Deletion
- Waitlist: until you create an account, request removal, or the beta period ends. The beta is initially planned for 30 days from its announced start date. If it is extended, remaining waitlist members will be emailed about the new end date.
- Active accounts and projects: while needed to provide access and preserve your work. We do not currently delete accounts or projects merely for inactivity.
- Deleted projects and accounts: deletion removes access and starts removal of associated data we control. We complete removal from active Buildryn systems within 30 days, subject to the exceptions below. A collaborator's contributions may remain in another person's project; an owner's projects are removed when the owner deletes their account.
- Deployments: the temporary virtual machine, world, runtime whitelist, and server logs are deleted when the deployment ends. Project settings, build history, and build artifacts follow the project's retention period.
- Other records: invoices and transaction records may be retained for legally required periods. Security, support, and dispute records may be kept only as long as reasonably needed for those purposes. Backups may remain until overwritten on their normal cycle.
A legal obligation, active dispute, security investigation, or provider retention rule may require a longer period for particular information. We will explain applicable exceptions when responding to a deletion request. We cannot promise that every provider-held copy is erased within 30 days.
8. Your Rights and Choices
Depending on where you live, you may request access, correction, deletion, restriction, portability, or an objection to certain processing. You may withdraw consent for optional communications at any time. You may also complain to the Portuguese data protection authority or another competent authority.
You can edit profile information and delete projects or your account through available account controls. Legal retention duties and other permitted exceptions may limit deletion.
9. Security and Age
We use access controls, password hashing, secure sessions, and other safeguards to protect information. Staff access to private content is limited to what is needed for support, security, legal compliance, or an incident. No online service can guarantee absolute security; please protect your sign-in methods and tell us if you suspect unauthorized access.
Buildryn is intended only for people aged 18 or older. If we learn that a minor has created an account, we will take steps to close it and handle the associated information appropriately.
10. Changes and Contact
We will update this page when our practices change and give notice of material changes, including a change in AI provider terms that affects customer information. The updated date above shows when this version was published.
For privacy requests, email privacy@buildryn.com.