Privacy Policy
Table of Contents
Last updated: 25.10.2026 — Effective date: 25.10.2026
1. Introduction
Welcome to kōdlo (“Platform”, “we”, “us”, or “our”). kōdlo is an agent-native sales workspace built for high-ticket B2B deals, combining a multi-tenant CRM with an always-on AI agent. This Privacy Policy explains what personal data we collect, why we collect it, how we use it, who we share it with, and what rights you have. By accessing or using kōdlo (our website at kodlo.ai and the application at app.kodlo.ai, together with related integrations), you agree to the practices described in this Policy.
Our core commitments:
- We do not sell or “share” your personal data (including within the meaning of the CCPA/CPRA), and we do not use it for cross-context behavioural advertising.
- We do not share it with anyone other than the sub-processors listed in Section 6.
- We do not use your Client Workspace Data, prompts, or AI-generated content to train our or any third party’s AI models.
- Your core workspace data is hosted in the European Union. The kōdlo application, our databases, and the vector stores that hold your Knowledge Hub and long-term-memory data run on EU-based infrastructure (Hetzner, Germany/Finland). Only specific processing operations — managed AI inference, web search, and object storage — involve non-EU sub-processors, each governed by appropriate transfer safeguards (Section 7).
Each commitment is explained below.
2. Who We Are
kōdlo is operated by REINODE SOFTWARE SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ, NIP 1133173579 (“Company”).
Contact e-mail: info@kodlo.ai
Registered address: ul. GROCHOWSKA nr. 42 lok. 31, 04-282 Warsaw, Poland.
For GDPR purposes, Reinode Software acts as the Data Controller for account and billing data submitted by users directly. Where users upload third-party contact data or process CRM histories, the Client acts as the Data Controller, and kōdlo acts solely as the Data Processor.
As Reinode Software is established within the EU (Poland), we are not required to appoint an Article 27 EU representative.
Business customers acting as Data Controllers may enter into our Data Processing Agreement (DPA), which sets out our Article 28 GDPR processor obligations, the current sub-processor list, and the Standard Contractual Clauses we rely on.
3. Data We Collect
3.1 Account & Identity Data
When you register for kōdlo via Google SSO (OAuth/PKCE) or email/password, we collect:
- Full name and work e-mail address.
- Password (secured using Argon2 hashing; we never store plain text).
- Billing information, only when you subscribe to a paid plan (handled by our merchant of record, Paddle). The Free plan does not require any payment details.
- Registration security data: when an account is created, and when a workspace activates the Free plan, we record technical details of the registration: the IP address, browser identification (user-agent), browser language, and the domain part of the e-mail address. We use this only to detect fraudulent or abusive sign-ups (for example, many registrations from one network address, or repeated free allowances), on the basis of our legitimate interest (Article 6(1)(f) GDPR). See Section 8 for how long we keep it.
- Bot protection: our sign-up and Free-plan activation forms use Cloudflare Turnstile to check that a human, not an automated script, is submitting them. Turnstile processes your IP address and technical information about your browser and device for this check. We use it on the basis of our legitimate interest in protecting the Platform against automated abuse (Article 6(1)(f) GDPR).
- Activity data: we record when each user last signed in or used the Platform (to the nearest hour). We use it to operate the Platform and, for workspaces on the Free plan, to identify inactive workspaces that are deleted after 90 days without a sign-in (Section 8).
3.2 Client Workspace Data (User-Submitted)
Data you import or generate inside kōdlo (also referred to as “User Data” in our Terms of Use), including:
- Prospect records, campaigns, timeline events, and file attachments.
- Knowledge Hub documents you upload (PDF, DOCX, XLSX, CSV, TXT, MD, PPTX) and the text extracted from them.
- Custom event taxonomies and personal tone-of-voice settings.
- AI-generated deep-research briefs and outreach drafts.
- Meeting data (notetaker): if a user sends the kōdlo notetaker to an online meeting, we process the meeting link, participants’ names as shown in the meeting, the transcript with speaker names, and AI-generated meeting notes. The meeting is recorded and transcribed by our meeting-recording provider. kōdlo does not store the audio or video of the meeting. See Section 3.6.
Important: You are responsible for ensuring you have a lawful basis to process any third-party personal data you import (e.g., via CSV or LinkedIn export).
3.3 Integration & OAuth Data
If you connect third-party channels (e.g., Google SSO, Telegram, Google Chat), we collect the OAuth tokens and metadata needed to route the AI agent’s responses to your authorized devices.
Where you use Google Sign-In or Google Chat, we access only the Google user data needed to deliver those features (your basic Google profile and the messages you exchange with the agent in Google Chat). Our use of this data is described in Section 5 (Google API Services — Limited Use).
3.4 AI Interaction Data
Your prompts, chat sessions, and the AI agent’s tool calls are logged to provide session memory and workspace continuity. Where you enable Long-Term Memory, chat content and artifacts are also converted into numeric vector embeddings stored in your workspace’s private vector collection to support recall across sessions. Meeting notes created by the notetaker are also added to the workspace’s long-term memory. Meeting transcripts are not.
Personal memory-profile opt-out: You can disable your personal Long-Term Memory profile in your settings. Doing so stops the building of your personal memory profile and its use in the agent’s responses. Please note, however, that chat content is still converted into vector embeddings within your workspace’s shared memory collection, where it remains searchable to workspace members through the agent.
3.5 Website Visitor Data
When you visit our public website (kodlo.ai), we and our analytics providers — Google Analytics (Google LLC) and Microsoft Clarity (Microsoft Corporation) — collect standard technical information such as your IP address, browser and device type, pages viewed, and referring URLs, and, via Microsoft Clarity, aggregated (masked) session-replay and interaction data, using cookies and similar technologies (see the Cookies section). These analytics cookies are set only after you consent via the website’s cookie banner. We use this data solely for analytics purposes — to operate, secure, and improve the site. Both providers are US-based; transfers are safeguarded by Standard Contractual Clauses and, where applicable, the EU-US Data Privacy Framework. These analytics run on our website only — the application (app.kodlo.ai) uses strictly-necessary cookies and no analytics.
3.6 Meetings Recorded with the Notetaker
The notetaker joins an online meeting only when a user of a kōdlo workspace sends it. Meetings may include participants who are not kōdlo users. The customer who sends the notetaker decides to record the meeting; kōdlo processes the meeting data on the customer’s behalf. The customer is responsible for informing participants and, where applicable law requires it, obtaining their consent.
When the notetaker joins a meeting, it posts a message in the meeting chat addressed to all participants and pins it. The message says that the meeting is being recorded, that the recording is processed by a third-party provider, and that anyone who objects can say so or ask the organiser to remove the notetaker. The user sees the same text before sending the notetaker.
AI-generated meeting notes are visible to all members of the workspace. The full transcript is visible only to the user who sent the notetaker.
If you took part in a meeting recorded with the notetaker and want to exercise your data protection rights, please contact the organisation that invited you. You can also write to info@kodlo.ai and we will pass your request on.
3.7 External AI Apps (MCP Connector)
If your workspace owner enables External AI apps, members can connect kōdlo to third-party AI clients such as Claude through our MCP server (api.kodlo.ai/mcp). In that case we process:
- Connection data: the name of the connected app, its approved redirect address, the access level you chose (full or read-only), and hashes of access tokens and API keys. We never store tokens or keys in plain text.
- Audit trail: for every change made through the connector, the key or app used, the tool called, and the names of the changed fields. We do not log the field values.
- Usage data: when each key or connected app was last used and the IP address of that request.
- Background run data: inputs and results of lead discovery, deep research, lookup and enrichment runs started from the connector.
The connector acts with your role’s permissions and only inside your workspace. When a tool returns data, that data becomes part of your conversation in the external AI app and is processed by that app’s provider (for Claude, Anthropic) under the terms of your own account with them. That provider is not a kōdlo sub-processor, and kōdlo does not control what it stores. Details: Privacy & data for the Claude connector.
4. Personal Data of Third Parties & AI Research Profiling
A core function of kōdlo is researching prospects. When you or the AI agent build a prospect record or a research brief, the Platform may compile personal data about identifiable third parties, including: name, job title and employer, professional-network activity, publicly reported news and events, and AI-inferred “signals” or contact-readiness assessments. To do this, the agent may use our web-search sub-processor (Exa) to query publicly available web sources and to discover company and person entities — including public person profiles with professional details such as work and education history — as a default capability of the research agent.
For this third-party data, the Client is the Data Controller and is responsible for: having a lawful basis to process it (typically legitimate interest under Article 6(1)(f) GDPR), providing any notice required under Article 14 GDPR, and honouring data-subject requests, including the right to object. kōdlo processes this data solely as a Data Processor on the Client’s instructions.
Automated decision-making & AI transparency: Contact-readiness scores and “next-best-action” suggestions are decision-support outputs intended to be reviewed by a human user. They are not solely automated decisions producing legal or similarly significant effects within the meaning of Article 22 GDPR. kōdlo is an AI-powered system: when you interact with the agent you are interacting with artificial intelligence, and research summaries, drafted messages, and analyses are AI-generated content that you are responsible for reviewing before use. We maintain these transparency practices in line with the transparency obligations under Article 50 of the EU AI Act.
5. Artificial Intelligence and Strict Data Isolation
We understand that your sales strategies are highly confidential. kōdlo operates on a Zero Training Policy:
- No Model Training: kōdlo does not use your Client Workspace Data, prompts, or generated artifacts to train, retrain, or improve any AI models. Our managed AI providers are contractually bound to the same standard: Google (Gemini API) does not use prompts or responses from its paid API to train or improve its models and processes them as a data processor under its Data Processing Addendum; Mistral (used for document OCR) is an EU provider that processes data within the EU and does not use paid-API content for model training. Where optional providers (OpenAI, Anthropic) are enabled, their business/developer-API terms likewise exclude your content from model training by default.
- Architectural Isolation: Every database query is automatically scoped to your specific workspace. Cross-tenant access is restricted at the repository layer, returning a “not found” response to prevent information leakage. Knowledge Hub and Long-Term Memory vector collections are provisioned per workspace.
- Encrypted Secrets: Where you supply your own provider API keys (LLM, Google/Gemini, Mistral, Exa), they are encrypted at rest using Fernet symmetric encryption.
Google API Services — Limited Use
kōdlo’s use of information received from Google APIs (including via Google Sign-In and Google Chat) adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically: (a) we use Google user data only to provide and improve user-facing features of the Platform; (b) we do not use it for advertising; (c) we do not allow humans to read it except with your affirmative consent, for security purposes such as investigating abuse, or where required by law; and (d) we do not transfer it to others except as necessary to provide the Platform, to comply with applicable law, or as part of a merger or acquisition.
6. How We Share Your Data (Sub-processors)
We act as a conduit, using trusted sub-processors to operate the Platform securely. We disclose the categories of personal data below to these service providers solely for the business purposes described, and never for their own independent commercial use. Customers who have entered into our DPA can request the current, dated list of sub-processors and how we notify changes at info@kodlo.ai. Our current sub-processors are:
| Sub-processor | Role | Data | Purpose | Hosting / Region | Transfer mechanism |
| Hetzner Online GmbH | Infrastructure / hosting | All workspace data, databases, vector stores, backups | Application hosting; PostgreSQL; Qdrant (Knowledge Hub & Long-Term Memory vectors); Redis | EU (Germany / Finland) | None — processed within the EU (Art. 28 GDPR DPA) |
| Google (Gemini API) | Managed AI (LLM) & embeddings | Prompts, chat content, document text, meeting transcripts | AI reasoning and agent responses; Knowledge Hub & Long-Term Memory embeddings; generating meeting notes from transcripts | US (Google global infrastructure) | SCCs / EU-US DPF; paid-tier no-training |
| Mistral AI | OCR | Knowledge Hub document content | Optical character recognition of uploaded documents | EU (France) | None — processed within the EU; DPA |
| Recall.ai | Meeting recording & transcription | Meeting audio and video, participants’ names, transcript, meeting link, notetaker name | Recording and transcribing online meetings — only when the notetaker is used | EU (Frankfurt, Germany) | None — processed within the EU |
| Google Cloud Storage | Object storage | File attachments, OCR’d documents, AI artifacts | Secure storage (signed, expiring URLs) | EU / US | SCCs / EU-US DPF |
| Google (Sign-In, Chat) | Authentication & integrations | Identity, messages | SSO, agent channel | EU / US | SCCs / EU-US DPF |
| Exa | Web search & entity discovery | Search queries derived from prompts; URLs of pages retrieved | Real-time web search, company/person entity discovery, and page-content retrieval for market intelligence | US | SCCs |
| Paddle | Merchant of Record | Billing & contact data | Checkout, tax, invoicing | EU / US | SCCs / EU-US DPF |
| Cloudflare, Inc. | Bot protection (Turnstile) | IP address, browser and device signals on the sign-up and Free-plan activation forms | Telling humans from automated sign-ups | Global (US company) | SCCs / EU-US DPF |
| Gmail SMTP (Google) | Email delivery | Email address, message content | Transactional email (verification, invites, billing) | EU / US | SCCs / EU-US DPF |
| Telegram | Optional integration | Messages routed to/from the agent | Agent channel — only if you connect it | International | Governed by Telegram’s terms |
| OpenAI / Anthropic | Optional / on-demand AI (LLM) | Prompts, chat content | Alternative AI reasoning — used only when explicitly enabled by operator configuration or under Custom plan BYOK; not part of the default managed stack | US | SCCs / EU-US DPF |
Anthropic listed above refers only to kōdlo’s optional use of its API inside the Platform. When you connect kōdlo to Claude yourself (see Section 3.7), Anthropic processes tool results as your provider, not ours.
Optional and on-demand AI providers: By default, managed AI processing runs on Google Gemini (reasoning and embeddings) and Mistral (OCR). OpenAI and Anthropic are optional large-language-model providers that are not used in the default managed configuration. Your prompts are sent to OpenAI or Anthropic only if the operator switches the platform’s default provider, or if you (as a Custom plan customer) configure them under Bring-Your-Own-Key. Mistral is also available as an optional chat provider in addition to its managed OCR role.
Own-fetch first: When the agent needs the content of a specific web page, it first attempts to retrieve it directly from kōdlo’s own EU-based infrastructure (no sub-processor involved); Exa’s content-retrieval API is used only as a fallback.
Bring-Your-Own-Key (BYOK): kōdlo offers Custom plan customers the ability to supply their own API keys for the LLM provider (Google Gemini, OpenAI, Anthropic, or Mistral), web search (Exa), and OCR/embeddings (Mistral / Google). When using BYOK, data processing for those AI operations is governed entirely by your direct agreements with the relevant providers.
7. International Data Transfers
kōdlo is hosted in the European Union. The Platform, its databases, and the vector stores holding your Knowledge Hub and Long-Term Memory data run on EU-based infrastructure (Hetzner, Germany/Finland), and document OCR is performed within the EU (Mistral, France). These operations involve no transfer of personal data outside the EEA.
Certain processing operations rely on US-based sub-processors — notably managed AI inference (Google Gemini), object storage (Google Cloud Storage), web search (Exa), email delivery, billing (Paddle), bot protection on our sign-up forms (Cloudflare Turnstile), Google Sign-In/Chat, and — on our public website only — website analytics (Google Analytics, Microsoft Clarity). Where data is transferred to countries outside the EEA, we rely on the European Commission’s Standard Contractual Clauses (SCCs) as our primary safeguard, supplemented by appropriate technical and organisational measures.
Where our US-based sub-processors (such as Google and Paddle) are certified under the EU-US Data Privacy Framework (DPF), we additionally rely on that Framework for the relevant transfers. The DPF’s adequacy decision was upheld by the General Court of the European Union on 3 September 2025; because its long-term status remains subject to further appeal, we maintain SCCs as an independent fallback so that transfers remain lawful regardless of the Framework’s status.
8. Data Retention & Workspace Lifecycle
You control the lifespan of your data:
- Active Subscriptions: Data is retained for the duration of your active workspace.
- Free workspaces: A workspace on the Free plan is kept while it is in use. If nobody signs in to it for 90 days, it is permanently deleted after e-mail warnings to its owner. If its owner closes it, it is permanently deleted 7 days after closure. In both cases the whole workspace is deleted — its data, its users and the account record — and the e-mail addresses become free to register again. Nothing is kept for 2 years, unlike a paid workspace; only the free-allowance record below and the registration security data are kept.
- Free-allowance record: when a workspace activates the Free plan or starts a free trial, we record the e-mail address (including a normalised form, so alias variants of one mailbox count as the same address), its domain, the date and the workspace it was used for. We keep this record indefinitely, on the basis of our legitimate interest in preventing repeated free allowances (Article 6(1)(f) GDPR). It contains no workspace content and is kept even if the account or workspace is deleted. You can request its erasure via info@kodlo.ai; the address then becomes eligible for a free allowance again.
- Workspace closure and grace period: Owners can close their workspace at any time from the application. Access continues until the end of the paid period. After that, the workspace enters a grace period of 30 days: your data is kept intact but inaccessible, and you receive pre-deletion warnings. During the grace period you can restore the workspace by starting a new subscription; restoration takes effect once payment is confirmed.
- Deletion of workspace data at the end of the grace period: When the grace period ends, the workspace’s data is permanently deleted. This includes contacts, campaigns, timeline events and their attachments, tickets, chat sessions and messages, meeting transcripts and notes, AI-generated artifacts, uploaded files, Knowledge Hub content, AI-memory profiles, and the per-workspace Knowledge Hub and Long-Term Memory vector collections. Deletion is irreversible: after it, we cannot restore your data and no export is possible. Please request your export at least 7 days before the grace period ends (Section 10).
- Account record retained for 2 years: After deletion we keep a limited account record for 2 years: the workspace record and its lifecycle dates, the owner’s account details (so the owner can sign in and reopen a workspace), the e-mail addresses of the workspace’s other users (all their other profile details are erased at deletion), billing identifiers and usage records, and our record that the workspace has used a free trial. We keep it on the basis of our legitimate interest (Article 6(1)(f) GDPR) in preventing fraud and abuse, in particular repeated free-trial registrations, and in the establishment, exercise or defence of legal claims. During this period, the e-mail addresses in the account record remain reserved and cannot be used to register a new workspace. You can start a new subscription on the same account and receive a new, empty workspace. You can ask us to erase the account record earlier via info@kodlo.ai (Section 10).
- Final deletion of the account record: When the 2 years have passed, or earlier on a verified deletion request, the account record is permanently deleted as part of our periodic data-cleanup operations, and the e-mail addresses in it are no longer reserved.
- Backups and logs: Deleted data may remain in encrypted backups for up to 30 days and in operational logs for up to 90 days, after which both are purged. Backups are used only for disaster recovery.
- Billing & tax records: retained for 5 years as required by Polish tax and accounting law, even after workspace deletion and after the account record has been deleted.
- Registration security data: the registration details described in Section 3.1 are kept for 2 years, even if the account or workspace is deleted, so that abuse across several registrations remains visible.
- Billing provider notifications: we keep the full content of our billing provider’s event notifications for 90 days. After that we keep only the event identifier, type and timestamp, so that no billing event is processed twice.
- Sales enquiries: if you contact us about an Enterprise or custom plan, we keep your enquiry (name, business e-mail, company and message) for up to 2 years.
- Meeting recordings: kōdlo does not store meeting audio or video. After each meeting we instruct our provider to delete the recording. Transcripts and notes are kept as workspace data and deleted with it.
- External AI apps (MCP): connection records and key hashes are kept until you disconnect the app or revoke the key, then deleted within 90 days. The audit trail is kept for 90 days. Last use and IP address data is kept for 90 days. Background run inputs and results are deleted 30 days after the run finishes. Retry records (
client_request_id) are deleted after 7 days.
9. Legal Bases for Processing
- Contract Performance (Article 6(1)(b) GDPR): Providing the kōdlo workspace, CRM tools, and AI generation.
- Legitimate Interest (Article 6(1)(f) GDPR): Maintaining platform security, verifying webhook signatures via HMAC, enforcing rate limits, collecting and keeping registration security data and the free-allowance record to prevent fraud and abuse of free allowances, checking sign-ups for automated abuse (bot protection), deleting inactive Free workspaces, keeping the account record after a workspace is deleted for fraud prevention and for legal claims, and handling sales enquiries (Sections 3 and 8). You may object to processing based on legitimate interests at any time (Section 10).
- Legal Obligation (Article 6(1)(c) GDPR): Retaining billing records as required by tax authorities.
- Consent (Article 6(1)(a) GDPR and the ePrivacy rules): Setting analytics cookies on our public website — collected via the website’s cookie banner and withdrawable at any time (Section 12) — and optional marketing communications, which you can opt out of at any time (Section 10).
- Connection, audit and usage data for External AI apps: our legitimate interest in securing accounts and investigating misuse (Article 6(1)(f) GDPR), and performance of the contract (Article 6(1)(b) GDPR).
10. Your Rights (EEA)
Under the GDPR, you have the right to access, rectify, erase (“right to be forgotten”), restrict, or export your personal data, and to object to certain processing. You may also withdraw consent for marketing communications at any time. To exercise these rights, contact info@kodlo.ai. We will respond within one month, as required by the GDPR. You also have the right to lodge a complaint with the Polish supervisory authority (UODO) or your local data protection authority.
11. California Privacy Rights (CCPA / CPRA)
If you are a California resident, the California Consumer Privacy Act, as amended by the CPRA, provides you with additional rights. This section supplements the rest of this Policy.
- Categories of personal information we collect: identifiers (name, email), professional/employment information, commercial information (subscription/billing records), internet/network activity (usage and technical data, including registration IP address and browser details), audio and electronic information (meeting transcripts and notes created with the notetaker), and the content you submit to the Platform. We collect these for the business purposes described in Sections 3–5.
- Disclosure to service providers: In the preceding 12 months, we have disclosed the categories above to the service providers/contractors listed in Section 6, each for the limited business purposes stated, under contracts that prohibit them from retaining, using, or disclosing the information for any other purpose.
- No sale / no sharing: We do not sell your personal information and do not “share” it for cross-context behavioural advertising, as those terms are defined under the CCPA/CPRA. Because we do not sell or share personal information, we do not offer a “Do Not Sell or Share My Personal Information” mechanism; we nonetheless honour browser-based opt-out preference signals (such as Global Privacy Control) consistent with our practices.
- Your rights: to know/access, delete, and correct your personal information; to opt out of sale/sharing (not applicable, as we do neither); to limit the use of sensitive personal information (we do not use sensitive personal information for purposes requiring such a limit); and to be free from discrimination for exercising these rights.
- Automated decision-making technology (ADMT): The Platform’s contact-readiness scores and suggestions are decision-support outputs subject to human review and are not used to make legal or similarly significant decisions about California consumers without human involvement.
To exercise these rights, contact info@kodlo.ai. We will verify your request and respond within the timeframes required by law (acknowledging within 10 business days and substantively responding within 45 calendar days, extendable by a further 45 days where reasonably necessary). You may use an authorized agent to submit a request on your behalf.
12. Cookies
We use cookies and similar technologies on the application (app.kodlo.ai) and on our public website (kodlo.ai). Cookies are small files stored on your device. The two properties differ: the application uses only strictly-necessary cookies (no analytics, no advertising), so no cookie banner is shown there; the public website additionally uses analytics cookies, which are set only after you consent via the website’s cookie banner. Strictly-necessary cookies do not require consent.
Cookies on the application (app.kodlo.ai):
| Cookie | Provider | Category | Purpose | Duration |
| access_token | kōdlo | Strictly necessary | Keeps you signed in — HttpOnly JWT, not readable by JavaScript | ~15 minutes |
| refresh_token | kōdlo | Strictly necessary | Renews your session without re-login — HttpOnly | Up to 30 days |
| oauth_state | kōdlo | Strictly necessary | Protects the Google sign-in flow (CSRF / PKCE state) | 5 minutes |
Cookies on our public website (kodlo.ai):
| Cookie | Provider | Category | Purpose | Duration |
| Consent preference | kōdlo (consent manager) | Strictly necessary | Stores your cookie choices | 6–12 months |
| _ga, ga* | Google Analytics (Google LLC) | Analytics (consent required) | Measures and improves website usage | up to 13 months |
| _clck, _clsk, CLID | Microsoft Clarity (Microsoft Corp.) | Analytics & session replay (consent required) | Understands how visitors use the site (aggregate metrics + masked session replay) | up to 1 year |
| MUID, ANONCHK, SM | Microsoft | Analytics (consent required) | Distinguishes visitors / measurement | up to 13 months |
The website cookie table is representative; the current, auto-updated list is available in the website’s cookie preference centre. You can withdraw or change your consent at any time through the website cookie banner, and you can block or delete cookies through your browser settings. Disabling strictly-necessary cookies may prevent the application from working properly. We keep these tables up to date as our cookies change.
13. Data Breach Notification
In the event of a personal data breach, we will notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it. Where the breach is likely to result in a high risk to your rights and freedoms, we will also inform affected users without undue delay.
14. Children
The Platform is intended for business and professional users aged 18 and over and is not directed to minors. We do not knowingly collect personal data from children. If we learn that we have collected such data, we will delete it.
15. Security Measures
- Hosting: Core data is hosted on ISO/IEC 27001-certified EU infrastructure (Hetzner).
- Encryption: Sensitive secrets are encrypted at rest (Fernet); transport is secured via TLS.
- Authentication: Short-lived JWT access tokens + refresh-token rotation; tokens are stored as HttpOnly cookies (XSS-resistant).
- Isolation: Strict per-workspace tenant scoping at the repository layer.
- Rate Limiting: Per-endpoint rate limiting to prevent abuse.
16. Changes to This Policy
We may update this Policy periodically. We will update the “Last updated” date above, and where changes are material we will provide additional notice. Continued use of the Platform after the effective date constitutes acceptance of the revised Privacy Policy.
Change history
25.10.2026: Added Section 3.7 (External AI Apps, MCP connector). Clarified in Section 6 that Anthropic acts as the user’s own provider when kōdlo is connected to Claude. Added retention periods for External AI apps data (Section 8) and their legal bases (Section 9).
17. Contact
kōdlo is operated by REINODE SOFTWARE SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ. Contact e-mail: info@kodlo.ai
Registered address: ul. GROCHOWSKA nr. 42 lok. 31, 04-282 Warsaw, Poland.