Privacy Policy
Version 1.0.0. Effective date: 19 November 2026
1. Who we are
Ugur Kaya (“we”, “us”, or “our”) operates Makas (the “Service”). Our business address is Utrecht, the Netherlands. If you have any question or request relating to this Privacy Policy (“Policy”) or to your personal data, contact us at privacy@makas.ai.
We are the data controller only of: the account and contact data of the users of our dashboard; US launch notification requests; security, abuse-prevention and sanctions-compliance records; product analytics that you consent to; and the records of your organisation’s acceptance of our terms.
For request metadata and for the content of the requests your organisation’s application sends through the Service, we act as our customer’s processor. The customer is the controller of that data, and our Data Processing Agreement governs how we process it.
2. Information we collect
Account data. When you create an account we collect your email address, your name, a password and the legal name of the organisation you act for. We never store your password itself — only a one-way Argon2id hash of it (see Security below).
Acceptance records. When you create an account, we record which versions of the Terms of Service and the Data Processing Agreement your organisation accepted and which version of this Policy you acknowledged, when, the organisation name, your email address, and the IP address and browser user agent used. These records are our evidence of the agreement.
US launch notification. If you ask us to notify you when the US region opens, we store your email address and when you first requested the notification in our EU database. We use them to manage the list and send one email about the opening. You can withdraw your request by emailing privacy@makas.ai.
Region check. When you sign up, log in, renew a session or accept a team invitation, we look up the country of your IP address in a database stored on our own server. No IP address is sent to a third party for this lookup. We use the result to refuse access from countries on our sanctions block list (currently Russia, Belarus, Iran, North Korea, Cuba and Syria). When we refuse a request, we record the event with the country code, the IP address and the browser user agent, but not your email address; repeated refusals of the same kind from one IP address are recorded at most once every ten minutes. The country database is DB-IP’s IP to Country Lite, licensed under CC BY 4.0: IP Geolocation by DB-IP.
Request metadata. Each time your application sends a request through the Service, we record metadata about that request, including: the source IP address and user-agent of the caller, the provider and model used, input and output token counts, the computed cost, timing/latency, and the HTTP status of the call. This metadata is what powers your analytics dashboard, rate limiting, and abuse prevention. We process it as our customer’s processor, under the Data Processing Agreement.
Optional product analytics. With your browser analytics consent, PostHog receives selected page categories, signup interactions, sanitized campaign labels and device categories. Owners may separately enable account sharing for historical onboarding milestones and successful API activity on later complete UTC days. Regional pseudonymous account and member IDs connect these events. We do not send names, email addresses, form values, prompts, responses, API keys or URL query strings to PostHog. Automatic click capture, session replay and geolocation enrichment are disabled. Direct browser connections still expose a network IP address to the receiving service.
3. What we do NOT collect
Prompt plaintext and provider response bodies are not persisted during normal request routing. We route requests through and log only the metadata described above. To serve repeated requests with the same content from your organisation’s account, we may hold a successful model response in memory for up to five minutes; we never write it to disk.
4. How we use information
We use the personal data described above to:
- provide, operate, and maintain the Service, including routing your requests and computing costs;
- secure the Service, detect and prevent fraud, abuse, and unauthorized access;
- refuse access from countries on our sanctions block list (currently Russia, Belarus, Iran, North Korea, Cuba and Syria);
- keep evidence of the terms your organisation accepted;
- send the US launch notification you requested;
- bill you for paid subscriptions and manage your account; and
- comply with our legal obligations and respond to lawful requests from public authorities.
5. Legal bases (GDPR)
Where the General Data Protection Regulation (“GDPR”) applies, we process personal data on the following legal bases:
- Legitimate interests (Article 6(1)(f)) — users of our dashboard are employees or representatives of our business customers. We rely on our and our customers’ legitimate interests to create and administer your account and provide the Service to your organisation; to secure the Service and prevent abuse and fraud; to look up the country of your IP address; and to keep the acceptance records as evidence of the agreement, where those interests are not overridden by your rights and freedoms;
- Performance of a contract (Article 6(1)(b)) — where you are yourself the contracting party, for example as a sole trader;
- Legal obligation (Article 6(1)(c)) — for sanctions checks, and for records we must keep by law; and
- Consent (Article 6(1)(a)) — for optional product analytics and the US launch notification. You may withdraw consent at any time without affecting the lawfulness of processing before withdrawal.
6. Sub-processors
We share limited personal data with the following sub-processors so that they can provide services to us. We engage sub-processors only under written agreements that meet Article 28(4) GDPR, and we will update this list as our sub-processors change. See our Data Processing Agreement for the terms that govern them.
| Provider | Purpose | Location |
|---|---|---|
| Google Workspace | Transactional email delivery | Global, including outside the EEA (Google data centres) |
| PostHog | Optional consented product analytics: acquisition, account onboarding and successful API activity | European Union (configured EU Cloud project) |
| Sentry | Application error monitoring | European Union |
| New Relic | Application performance and metrics monitoring | European Union |
| Hostinger | Application and database hosting (virtual private server) | European Union (Frankfurt, Germany) |
| Cloudflare | Documentation website hosting and delivery (docs.makas.ai) | Global, including outside the EEA (Cloudflare edge network) |
Customer-designated recipients
When your organisation sends requests through the Service, we forward them to the LLM providers it chooses, using its own provider credentials and under its own agreement with each provider. These providers are our customer’s processors, not our sub-processors.
| Provider | Purpose | Location |
|---|---|---|
| OpenAI | LLM request processing under the customer's own agreement | United States (per the provider's terms) |
| Anthropic | LLM request processing under the customer's own agreement | United States (per the provider's terms) |
| Google (Generative Language API) | LLM request processing under the customer's own agreement | United States (per the provider's terms) |
7. International data transfers
We are established in the Netherlands. We host the Service and its database in the European Union (Frankfurt, Germany). Some of our service providers (Sentry, New Relic, PostHog and Google) belong to groups headquartered in the United States; where such a provider may access personal data from outside the EEA, it relies on the EU-US Data Privacy Framework or the European Commission’s Standard Contractual Clauses. When you send requests through the Service, they are forwarded to the LLM providers you choose (OpenAI, Anthropic and/or Google) under your own agreement with them; those providers may process the data in the United States under the safeguards in their own terms.
8. Data retention
Request-log metadata and aggregated analytics data are retained only for as long as your plan’s retention window, after which they are automatically deleted or aggregated beyond identifiability. Longer plans retain data longer to support historical analytics.
| Plan | Request logs | Analytics aggregates |
|---|---|---|
| Trial | 7 days | 30 days |
| Founding Customer | 30 days | 90 days |
| Starter | 14 days | 60 days |
| Growth | 30 days | 90 days |
| Scale | 90 days | 365 days |
| Enterprise | 365 days | Unlimited |
Optional PostHog events use the configured EU Cloud project’s retention policy, separately from the plan-based request-log and aggregate windows above. Browser identifiers persist locally until consent is withdrawn or browser storage is cleared. Local export records retain onboarding milestone identities until account deletion to avoid duplicate delivery; acknowledged daily records are pruned after 90 days. Withdrawing sharing prevents future export but does not erase events already received by PostHog. A batch already in flight may still arrive. You may request erasure of the account and member analytics identities through our privacy contact; we process that request in PostHog as well.
- Acceptance records are kept for the life of the account and for 13 months after its deletion. The IP address and user agent in them are cleared 13 months after acceptance.
- Region-check events (refused signups, logins, session renewals and invitation acceptances), with their country code, IP address and browser user agent, are kept for 13 months.
- Deleted accounts: 30 days after an account is deleted, its account data is anonymised. The email address is replaced, and the name and organisation name are removed.
- US launch notification requests are removed from the mailing list after the notification is sent, if the campaign is cancelled, or when you withdraw your request.
- Backups. We store encrypted database backups on operator-managed equipment. After verifying a new backup, we keep the newest copy from each of the seven most recent backup days and the four most recent backup weeks. We remove copies outside that rotation.
9. Security
We apply industry-standard technical and organizational measures to protect personal data, including: encryption in transit via TLS; password hashing with Argon2id using OWASP-recommended parameters; and automatic redaction of sensitive data (such as API keys and other secrets) from our operational logs. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
Reporting a vulnerability
If you believe you have found a security vulnerability in the Service, email security@makas.ai. Please give us reasonable time to fix it before you disclose it, and do not access other people’s data or disrupt the Service while testing. Our contact details for security reports are also published at /.well-known/security.txt.
10. Your rights
Subject to applicable law, you have the right to: access the personal data we hold about you; request its rectification if it is inaccurate; request its erasure; receive a portable copy of the data you provided to us; restrict or object to certain processing; and withdraw consent at any time where processing is based on consent (without affecting the lawfulness of processing before withdrawal). You also have the right to lodge a complaint with a supervisory authority: if you are in the European Union/EEA, this right arises under Article 77 of the GDPR — for residents of the Netherlands, the relevant authority is the Autoriteit Persoonsgegevens; if you are in the United Kingdom or another jurisdiction with its own data-protection law (such as the UK GDPR), you may lodge a complaint with the equivalent authority under that law. To exercise any of these rights, contact us at privacy@makas.ai.
11. Data-breach notification
If we become aware of a breach affecting personal data for which we are the controller, we will notify the competent supervisory authority and the individuals concerned in accordance with Articles 33 and 34 GDPR. For data we process on behalf of a customer, we notify that customer as set out in the Data Processing Agreement.
12. Cookies & similar technologies
Authentication uses browser local storage. Optional PostHog browser identifiers and sanitized attribution are stored only after you accept browser analytics. You can decline without losing access to the Service, and change your choice using Analytics preferences. Account sharing has a separate owner-only control in the same preferences panel, and does not depend on whether this browser allows analytics. Browser withdrawal clears PostHog identity storage and stops future browser capture. Sentry provides application error monitoring with personal data collection disabled and request and response bodies stripped. We do not use advertising trackers.
Successful password login sets an opaque, HttpOnly security cookie called makas_devicefor up to 90 days. It helps us recognize a previously observed browser and notify you of a login from a new device. We retain only an actor-scoped hash of this identifier and first/last-seen timestamps, deleting device-presence records after 90 days of inactivity and keeping at most 20 recent devices per account identity. The first observed device establishes a baseline. This cookie is not an authentication credential, and does not use browser fingerprinting or location inference. Security notices contain a coarse browser/operating-system label and UTC login time. This security function is separate from optional analytics consent. The cookie is strictly necessary for the security of your account, so it does not require consent (Article 11.7a(3)(b) Telecommunicatiewet).
13. Children
The Service is not directed to, and is not intended for use by, anyone under the age of 18. We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, contact us at privacy@makas.ai and we will take steps to delete it.
14. Changes
We may update this Policy from time to time to reflect changes to the Service or for legal, regulatory, or operational reasons. If we make a material change, we will notify account holders (for example, by email) before the change takes effect. This Policy is effective as of 19 November 2026.
15. Contact
Questions about this Policy, or requests relating to your personal data, may be sent to privacy@makas.ai, or by post to Utrecht, the Netherlands.