Privacy Policy
Last updated: 29 October 2026
This policy explains what personal data Teckologs AI processes, why, for how long, who helps us, and the rights you have. It is written to match exactly what the product does; if something here is unclear, email teckologs.support@teckologs.com.
1. Who we are and our role
Teckologs AI (teckologs.ai) is operated by Teckologs sp. z o.o., ul. Złota 7 lok. 1, 00-019 Warszawa, Poland, entered in the register of entrepreneurs of the National Court Register (KRS) under no. 0001015544, kept by the District Court for the Capital City of Warsaw, XII Commercial Division of the National Court Register, NIP 5252941259, REGON 524295449, share capital PLN 5,000.00 (“we”, “us”). We play two roles under the EU General Data Protection Regulation (GDPR):
- Controller for the data we need to run our relationship with you: your account, billing, support and sales enquiries, website analytics (with consent) and security logs.
- Processor for the content our customers put into the service — their documents, the people and companies named in them, and the people they share documents with or onboard. For that data our customer is the controller and we act only on their instructions, under our Data Processing Agreement. If your data is in a customer’s document, please contact that company first; we will help them answer you.
2. What we collect
| Who | Data | Source |
|---|---|---|
| Account users | Name, email, password (stored only as a hash), company name and details you enter (address, VAT/tax number, phone), role, language, saved signature, Vault PIN (hashed) | You |
| Customers’ documents | Whatever you put in or upload: party names, addresses, cargo, amounts, contract terms, signatures, files | You / your organisation |
| People you send documents to | Name, email (or phone for WhatsApp), what they did — viewed, signed (signature image, time, IP for the audit trail), edited, reviewed | The sender, and the person themselves |
| Onboarding portal users | Name, email, files they upload, signatures, task progress | The inviting organisation, and the person |
| Visitors and enquiries | Contact-form and booking details (name, email, company, message); chats with Tessa, our AI assistant | You |
| Usage and security | Sign-in events, actions in your workspace (audit log), IP address, device and browser information, error logs | Automatically |
| Analytics (only with consent) | Pseudonymous usage events, page views, performance and errors | Automatically, after you accept analytics cookies |
| Payments | Billing contact and subscription status. Card details are collected and held by Stripe — never by us | You, via Stripe |
3. Why we use it and our legal basis
| Purpose | Legal basis (GDPR) |
|---|---|
| Providing the service: accounts, document creation, storage, signing, sharing, filing, integrations you turn on | Contract — Art. 6(1)(b) |
| Processing customers’ document content on their instructions | Our customer’s basis; we act as processor (Art. 28) |
| Security: authentication, rate limiting, abuse and fraud prevention, audit logs | Legitimate interests — Art. 6(1)(f) — keeping the service and your data safe |
| Billing, invoicing and tax records | Legal obligation — Art. 6(1)(c); contract |
| Answering support and sales enquiries, booking demos | Legitimate interests / steps before a contract — Art. 6(1)(f), (b) |
| Product analytics with cookies | Consent — Art. 6(1)(a); you can withdraw it any time in Cookie settings |
| Aggregate service metrics without cookies (e.g. AI usage and cost per organisation) | Legitimate interests — running and pricing the service |
| Service emails (account, security, signature requests, receipts) | Contract / legitimate interests. We do not send marketing email without your consent. |
4. AI features
- AI drafting, extraction, analysis, translation and our assistant Tessa use the Azure OpenAI Service run in our own Microsoft Azure subscription. Microsoft does not use prompts or outputs to train models.
- We do not use your content to train any AI model.
- AI output can be wrong. It is a draft for you to review; it is not legal, tax or customs advice, and the person who uses a document remains responsible for it.
- Tessa is an AI. Please don’t share sensitive personal data in the chat. Conversations are kept in your browser for the visit and sent to the AI only to answer you.
- We make no decisions about you based solely on automated processing that produce legal or similarly significant effects (GDPR Art. 22). Compliance checks, HS/TARIC suggestions and sanctions screening are advisory.
- AI-drafted documents are labelled as AI-assisted in the PDF’s metadata (EU AI Act transparency).
5. Who we share data with
We use carefully selected service providers (“sub-processors”) — the full, current list with what each does and where is on our Sub-processors page. Data also goes to recipients you choose to send it to:
- Tax authorities and e-invoicing networks you file with (e.g. KSeF in Poland, ANAF in Romania, SDI in Italy, the Peppol network)
- People you share documents with, request signatures from, or onboard through a portal
- Your connected TMS / ERP / webhook endpoints
- The European Commission’s VIES service, to confirm an EU VAT number you enter (only the VAT number is sent)
We do not sell personal data, share it for advertising, or let advertising networks track you. We disclose data to authorities only where the law requires it, and we would tell affected customers unless legally prohibited.
6. Where your data is stored and international transfers
Your account and document data are stored in the European Union — Microsoft Azure, Poland Central — including database backups. AI requests are processed only within Microsoft’s EU Data Zone. Some providers process data outside the EU (for example email delivery by Resend in the US). Where data leaves the European Economic Area (EEA) we rely on the European Commission’s Standard Contractual Clauses, the EU-US Data Privacy Framework where the provider is certified, or another lawful safeguard. You can ask us for a copy of the relevant safeguards.
7. How long we keep it
| Data | Kept for |
|---|---|
| Account and workspace data, documents, signatures and their history | While your account is active. Deleting a document removes it; deleting your account removes your data immediately |
| Database backups | Up to 7 days, then overwritten (so deleted data disappears from backups within 7 days) |
| Server and error logs | 30 days |
| Payment and invoice records | As long as tax and accounting law requires (Stripe and we keep invoices; typically 5–10 years) |
| Support, sales and booking enquiries | As long as needed to handle them and follow up; ask us to delete them at any time |
| Cookie-consent records | As long as needed to show what you chose |
| Analytics (with consent) | Up to 12 months in PostHog |
For documents in a customer’s workspace, the customer decides how long to keep them.
8. Your rights
Under the GDPR you can ask to access, correct, delete or port your data, restrict or object to processing, and withdraw consent at any time (without affecting earlier processing). Much of this is built in:
- Access and portability: Settings → Export data gives you a machine-readable (JSON) copy.
- Correction: edit your details in Settings.
- Deletion: Settings → Danger zone deletes your account and data immediately. Or see Data deletion.
- Analytics consent: change it any time with “Cookie settings” in the footer.
For anything else email teckologs.support@teckologs.com with “Privacy request” in the subject. We reply within one month (extendable by two months for complex requests, in which case we tell you), may need to verify your identity, and never charge for a reasonable request.
9. Cookies and similar technologies
We use strictly necessary cookies to run the site, and analytics cookies only if you accept them. Details, durations and how to change your choice: Cookie Policy.
10. Security
- Encryption in transit (TLS) and at rest (Microsoft Azure).
- Each organisation’s data is isolated at the database level (row-level security), with role-based access inside a workspace.
- Passwords and Vault PINs are stored only as salted hashes; Vault documents need the PIN again before they can be sent outside your organisation.
- Secrets are held in Azure’s managed secret stores, never in the browser.
- Rate limiting, audit logs, version history with restore, and short-lived signed sessions.
If a personal-data breach occurs we notify the competent supervisory authority within 72 hours where required, and affected customers without undue delay.
11. Children
The service is for businesses and is not intended for anyone under 18. We do not knowingly collect children’s data.
12. Changes to this policy
We will tell account holders by email or in the app at least 30 days before a material change takes effect. The date at the top shows the latest version.
13. Contact and complaints
Teckologs sp. z o.o., ul. Złota 7 lok. 1, 00-019 Warszawa, Poland, entered in the register of entrepreneurs of the National Court Register (KRS) under no. 0001015544, kept by the District Court for the Capital City of Warsaw, XII Commercial Division of the National Court Register, NIP 5252941259, REGON 524295449, share capital PLN 5,000.00 · teckologs.support@teckologs.com · support form. If you’re unhappy with our answer you can lodge a complaint with a data protection supervisory authority — our lead authority is Poland’s President of the Personal Data Protection Office (UODO, uodo.gov.pl), or the authority in the EU member state where you live or work.
Related: Privacy Policy · Terms of Service · Cookie Policy · Sub-processors · Data Processing Agreement. Translations of these documents are provided for convenience; the English version prevails.