Privacy Policy
Last updated
This policy explains how personal data is handled when you visit chunkmint.dev, create an account and use the ChunkMint.dev platform to build and test Minecraft plugins. We process personal data under the EU General Data Protection Regulation (GDPR) and applicable Polish law.
1. Who is responsible
The controller of your personal data is the operator of ChunkMint.dev identified at the end of this page (“we”, “us”). For every question about your data, write to the privacy contact below. We do not have a data protection officer; the contact address is monitored by the people who run the service.
2. What data we process
- Account data: your name, email address, a salted hash of your password (we never store the password itself), whether the address is confirmed, and, if you sign in with Google, GitHub or Discord, the identifier of that account and the profile data the provider shares with us (name, email, avatar).
- Workspace content: the prompts and chat messages you write, the project files and snapshots that you or the AI agent create, build logs, the .jar files produced by builds and the console logs of test runs.
- Test-server data: the Minecraft usernames and UUIDs you whitelist, the times a test server ran and how long. A test server console log can contain the usernames and IP addresses of players who join, because the Minecraft server writes them there.
- Billing data: your plan, the status and period of your subscription, and the customer and subscription identifiers issued by our payment provider. Card and payment details are entered on the payment provider’s pages and never reach us.
- Usage data: how many AI tokens, build minutes and test-server minutes a workspace uses, to apply the limits of its plan.
- GitHub connection data (only if you connect GitHub): your GitHub user identifier and login, an access token that we store encrypted, and the names of the repositories you export projects to.
- Technical data: IP address, browser type, request time and the pages or API calls requested. They are written to server logs and used to run, secure and rate-limit the service.
- Messages: what you send us through the contact form or by email, together with your address.
- Referral data: if you open a referral link (chunkmint.dev/r/…) we store a random visitor identifier in a cookie for 30 days and keep a record of the visit with keyed hashes of your IP address and browser details (never the raw values) and the link’s campaign tags. If you then create an account, the account is linked to the person who invited you; they see only a masked initial, dates and the reward status, never your email, name or billing details. Visit records are deleted after 90 days. Chunkmint Credits earned through referrals are recorded in a credit ledger.
- Invitations: when a workspace admin invites someone, we process the invited email address, the role offered and the name of the inviter, and send one email to that address (at most three a day per address). If the invitation is not accepted it is deleted after 7 days.
3. Why we process it and on what legal basis
Where we rely on legitimate interest you can object at any time (see section 8). We do not use your data for advertising, we do not profile you for marketing and we do not sell personal data.
| Purpose | Data | Legal basis (GDPR) |
|---|---|---|
| Create and run your account, sign you in, keep the service working | Account data, workspace content, test-server data | Performance of the contract, Art. 6(1)(b) |
| Generate, build and test plugins at your request | Workspace content | Performance of the contract, Art. 6(1)(b) |
| Take payment, manage subscriptions, apply plan limits | Billing data, usage data | Performance of the contract, Art. 6(1)(b) |
| Send service emails: address confirmation, password reset, security and billing notices | Account data | Performance of the contract, Art. 6(1)(b); our legitimate interest in account security, Art. 6(1)(f) |
| Protect the service against abuse, fraud and attacks; rate limiting; investigate incidents | Technical data, usage data | Legitimate interest in the security and integrity of the service, Art. 6(1)(f) |
| Answer your messages and support requests | Messages, account data | Legitimate interest in answering you, Art. 6(1)(f); or steps at your request before a contract, Art. 6(1)(b) |
| Keep accounting records and meet tax obligations | Billing data | Legal obligation, Art. 6(1)(c) |
| Establish, exercise or defend legal claims | Any data needed for the claim | Legitimate interest, Art. 6(1)(f) |
4. AI processing of your content
To produce plans, code and fixes, the text of your prompts, the relevant project files and build or test output are sent to the AI model providers we use. We send only what is needed to answer the request, and the provider returns the generated text to us.
We do not use your content to train our own models. The providers process what we send under their own terms as our processors. Do not put secrets such as passwords, API keys or private player data into prompts or project files: anything in a project can be sent to those providers.
AI output is generated automatically. We do not take decisions about you with legal or similarly significant effects by automated means; the only automated decisions are the plan limits, such as monthly credits, that apply to every workspace in the same way.
5. Who receives your data
We share personal data only with providers that help us run the service, and only to the extent needed:
- Infrastructure providers that host the application, the database, file storage and the servers on which test environments run.
- AI model providers (and the router through which we reach them) that generate code and text from your prompts.
- Polar, our payment provider. Polar acts as the merchant of record: it collects the payment, handles VAT and invoices, and is an independent controller of the payment data you give it, under its own privacy policy.
- An email delivery provider that sends confirmation, password-reset and notification emails on our behalf.
- PostHog (EU cloud), our product analytics provider, only if you accept analytics in the cookie banner. It receives pseudonymous usage events (pages viewed, features used, plan, internal account ID) and never your prompts, code, messages or email address. You can withdraw consent at any time under Cookie settings.
- Google, GitHub and Discord, if you choose to sign in with them, and GitHub again if you connect it to export a project. They receive the data needed to authenticate you or to write to your repository, and handle it under their own policies.
- Professional advisers (accountants, lawyers) and authorities, where the law requires it or where needed to establish or defend a claim.
6. Transfers outside the European Economic Area
Some of our providers, in particular AI model providers and GitHub, may process data in the United States or other countries outside the EEA. We rely on an adequacy decision of the European Commission where one exists (for example for providers certified under the EU–US Data Privacy Framework) or on the standard contractual clauses approved by the Commission, together with additional safeguards where needed. You can ask us for a copy of the safeguards that apply.
7. How long we keep data
- Account data: for as long as your account exists. When you ask us to delete the account we delete or anonymise it within 30 days, except for data we must keep by law.
- Projects, chat messages and snapshots: until you delete them or your account is deleted.
- Build artifacts (.jar files): 30 days after the build, then they are deleted automatically. Build logs and test-run logs: 14 days. Your source files stay in the project, so you can build again.
- Billing records: for the period required by Polish accounting and tax law, currently five years from the end of the tax year in which the transaction took place.
- Server logs and security data: for a limited time needed to run and protect the service, then deleted or aggregated.
- Messages you send us: for as long as needed to handle the matter, then for a short period to defend against possible claims.
- Where we keep backups, they are overwritten on a rolling schedule, so deleted data can remain in them for a short time.
8. Your rights
You have the right to access your data and receive a copy, to have it corrected, to have it erased, to restrict its processing, to object to processing based on legitimate interest, and to receive the data you provided in a structured, machine-readable format. Where processing is based on consent you can withdraw it at any time without affecting what was done before.
To use a right, email the privacy contact below from the address of your account. We answer within one month; if a request is complex we may extend this by up to two further months and will tell you why. We may ask you to confirm your identity first.
You can also lodge a complaint with a supervisory authority. In Poland this is the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych), ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl. You may complain to the authority of your own country of residence as well.
Providing the data in section 2 that is needed for your account and for payment is a condition of using the service; without it we cannot provide it.
9. How we protect data
Traffic between your browser and the service is encrypted with TLS. Passwords are stored only as salted hashes. GitHub access tokens are stored encrypted. Each workspace’s data is visible only to its members, builds and test servers run in isolated, resource-limited environments that are destroyed afterwards, and test environments have no access to your workspace or to other users’ data. No system is perfectly secure; if a breach puts your rights at risk we will notify you and the supervisory authority as the law requires.
10. Children
The service is not intended for anyone under 16. We do not knowingly collect data from children; if you believe a child has created an account, tell us and we will delete it.
11. Cookies and similar technologies
We use the cookies and browser storage needed to sign you in and to remember interface choices. Product analytics (PostHog) is used only if you accept it in the cookie banner, and you can change your mind at any time. See the Cookie Policy for the full list.
12. Changes to this policy
When we make a material change we will update the date above and, for registered users, tell you by email or in the product before it takes effect. Earlier versions are available on request.
Operator and contact
Chunkmint is an independent, self-funded software startup founded and operated by Daniel Paliński in Poland. Chunkmint develops AI-powered tools for Minecraft plugin creation.
Chunkmint is currently operated as an independent project and is not incorporated as a separate legal entity.
Daniel PalińskiQuestions, privacy requests and account deletion: [email protected]. Security reports: [email protected].
