Legalica Privacy Policy & Data Protection
Table of Contents
- Introduction and Legal Framework
- Data Controller Information
- Categories of Personal Data Collected
- Collection Methods
- Legal Basis for Processing
- Purposes of Processing
- Role: Controller vs. Processor
- Google Cloud Infrastructure and Data Processing
- International Data Transfers
- Processing Details (Art. 28 GDPR)
- Processor Obligations
- AI Act Transparency Obligations
- Data Breach Notification
- No-Training Covenant
- Subprocessors and Infrastructure Chain
- Standard Contractual Clauses
- Cookie Types and Purposes
- Consent Management
- First-Party vs. Third-Party Cookies
- Retention Schedule
- Deletion Procedures
- User Rights
- Banner Texts and Settings Panel
PART I — PRIVACY POLICY
1. INTRODUCTION AND LEGAL FRAMEWORK
Legalica OÜ ("Legalica," "we," "us," or "our") processes personal data in accordance with this Privacy Policy and Data Governance document ("Policy").
1.1 Applicable Legal Framework
This Policy is designed with reference to the following regulations and frameworks:
| Regulation | Reference | Scope |
|---|---|---|
| GDPR | Regulation (EU) 2016/679 | All EU data subjects |
| Estonian IKS | Isikuandmete kaitse seadus | Estonian-specific requirements |
| EU AI Act | Regulation (EU) 2024/1689 | AI-related data processing |
| UK GDPR | UK Data Protection Act 2018 | UK data subjects |
| CCPA/CPRA | Cal. Civ. Code § 1798.100 et seq. | California residents |
| LGPD | Lei nº 13.709/2018 | Brazilian data subjects |
| PIPEDA | S.C. 2000, c. 5 | Canadian data subjects |
| PDPA | Act 26 of 2012 | Singapore residents |
| POPIA | Act 4 of 2013 | South African data subjects |
| APPI | Act 57 of 2003 | Japanese data subjects |
| PIPL | Order No. 84 of the President of the PRC | Chinese data subjects |
| ePrivacy Directive | Directive 2002/58/EC | Electronic communications |
| Rome I | Regulation (EC) 593/2008 | Conflict of laws |
1.2 Scope Across 324 Jurisdictions
Legalica operates across 324 jurisdictions and 187+ languages. While this Policy is designed for global compliance, the GDPR serves as the baseline standard for all processing activities. Where local laws provide stronger protections, those stronger protections apply. Users in all Supported Jurisdictions retain the rights granted by their local data protection laws, even if such rights exceed those described herein.
2. DATA CONTROLLER INFORMATION
2.1 Controller Identity
| Name | Legalica OÜ |
| Legal form | Private limited company (osaühing), Republic of Estonia |
| Registration number | ************* (Estonian Commercial Register / Äriregister — to be added upon registration) |
| VAT number | ************* (to be added upon VAT registration) |
| Address | Ahtri tn 12, 10151 Tallinn, Estonia (temporary registered address provided by a licensed e-Residency service provider) |
2.2 Data Protection Contact
| privacy@legalica.app | |
| Postal | Legalica OÜ, Attn: Data Protection, Ahtri tn 12, 10151 Tallinn, Estonia |
Legalica has assessed the appointment criteria of Art. 37 GDPR and has not formally appointed a Data Protection Officer at this stage; data-protection inquiries are handled centrally at the address above. This page will be updated if a DPO is appointed.
2.3 Lead Supervisory Authority
| Authority | Andmekaitse Inspektsioon (Data Protection Inspectorate) |
| Address | Tatari 39, 10134 Tallinn, Estonia |
| info@aki.ee | |
| Website | www.aki.ee |
Rationale for Estonian Lead Authority: Legalica's main establishment is in Estonia. Under GDPR Article 56, the supervisory authority of the main establishment serves as the lead authority for cross-border processing. Data subjects in all EU Member States may lodge complaints with the Estonian DPA or their local supervisory authority.
2.4 EU Establishment
Legalica OÜ is established in the European Union (Republic of Estonia). No representative under GDPR Art. 27 is required, as Art. 27 applies only to controllers and processors not established in the Union.
3. CATEGORIES OF PERSONAL DATA COLLECTED
3.1 Account Information: Full name, email address, professional title, organization, phone number, country of residence, IP address, device information.
3.2 Payment Information: Payments are processed by Creem (Armitage Labs OÜ, Estonia), acting as Merchant of Record. Creem collects and processes your billing address, payment method details, and transaction data as an independent data controller for the purposes of executing the purchase, invoicing, tax collection/remittance, and payment-dispute handling, under its own privacy policy. Legalica does NOT receive or store full card numbers. Legalica retains only purchase confirmations (product, amount, date, status) needed to activate and administer your subscription.
3.3 User Input Data: Queries, uploaded documents, corporate entity names, case descriptions, legal scenarios — any content voluntarily submitted to the Platform.
3.4 Usage Data: Log files, device information, IP address, approximate geolocation, session duration, activity patterns, error reports.
3.5 Google Workspace Data (if connected): File names and metadata from selected Google Drive folders, calendar event titles and dates, task lists. We do NOT access email content, contacts, or files outside selected folders.
3.6 Authentication Data: Processed by Firebase Authentication (Google LLC): email/password hashes, session identifiers, OAuth tokens for Google sign-in.
3.7 Special Categories: Legalica does not intentionally collect special category data (Art. 9 GDPR) or criminal conviction data (Art. 10 GDPR). Such data may only appear if included in User Input. Users are responsible for ensuring a lawful basis for processing such data.
4. COLLECTION METHODS
| Method | Description |
|---|---|
| Direct | Registration forms, Platform usage, support contacts, surveys |
| Automated | Server logs, cookies, analytics (consent-based), error monitoring |
| Third-party | Creem (purchase confirmation), Google (OAuth profile), corporate registries (public data) |
5. LEGAL BASIS FOR PROCESSING
| Purpose | Legal Basis (GDPR Art. 6) |
|---|---|
| Account registration and management | (b) Contractual necessity |
| Subscription administration (purchase confirmations) | (b) Contractual necessity |
| AI processing and response generation | (b) Contractual necessity |
| Authentication (Firebase) | (b) Contractual necessity |
| Security and fraud prevention | (f) Legitimate interest |
| Platform improvement (anonymized only) | (f) Legitimate interest |
| Marketing communications | (a) Consent (explicit opt-in) |
| Legal compliance (tax, accounting) | (c) Legal obligation |
| AI system validation (anonymized) | (f) Legitimate interest |
| Cookie placement (non-essential) | (a) Consent |
Legitimate Interests Assessment (LIA): Available upon request at privacy@legalica.app. We have conducted balancing tests ensuring our legitimate interests do not override your fundamental rights.
6. PURPOSES OF PROCESSING
6.1 Primary Purposes
- Platform Services: Authentication, query processing, AI response generation, document drafting, KYC/UBO tools, Google Workspace sync;
- Subscription Administration: Activation and management of paid access based on purchase confirmations from the Merchant of Record; refund handling;
- Security: Unauthorized access monitoring, fraud detection, integrity maintenance;
- Support: Inquiry response, troubleshooting, onboarding;
- Communication: Essential service notifications, marketing (with consent only);
- Legal Compliance: Tax/accounting records, legal request response, Terms enforcement;
- Platform Improvement: Anonymized usage pattern analysis only.
6.2 What We Do NOT Do
- Use your data to train any AI models (contractually prohibited across the entire AI Cascade);
- Sell your data to any third party;
- Use your data for advertising profiling;
- Share data with third parties for their marketing;
- Use advertising cookies or marketing pixels (e.g., Meta Pixel, Google Ads tags) — we do not operate any;
- Automated decision-making producing legal or similarly significant effects (GDPR Art. 22).
7. ROLE: CONTROLLER VS. PROCESSOR
7.1 Legalica as Controller: For: account management, subscription administration, usage analytics, communication, security, marketing.
7.2 Legalica as Processor (Art. 28): When processing User Input and AI Output on behalf of Workspace Owners. Legalica:
- Processes only on documented instructions;
- Ensures confidentiality obligations;
- Implements technical and organizational measures;
- Does not engage subprocessors without authorization;
- Deletes/returns data upon service termination.
7.3 Customer as Controller: Workspace Owners are Data Controllers for: User Input, AI Output, uploaded documents, corporate entity data, client Personal Data.
Workspace Owners are solely responsible for: obtaining consents, ensuring compliance, implementing policies, responding to client data subject requests.
7.4 Creem as Independent Controller (Merchant of Record): For each purchase, Creem (Armitage Labs OÜ, Estonia) is the seller of record and processes buyer payment and invoicing data as an independent data controller, not as Legalica's subprocessor. Creem's processing is governed by the Creem terms and privacy policy presented at checkout. Legalica and Creem exchange only the data necessary to activate your purchase (product, amount, status, account reference).
8. GOOGLE CLOUD INFRASTRUCTURE AND DATA PROCESSING
8.1 Infrastructure Provider as Key Subprocessor: Google LLC is Legalica's primary Infrastructure Provider and subprocessor. All Customer Data is stored, processed, and transmitted through Google Cloud Platform services. The following Google services process Customer Data:
| Google Service | Processing Activity | Data Location | Legal Basis |
|---|---|---|---|
| Cloud Firestore | Primary database — all structured data | EU (europe-west3) | Art. 28 GDPR |
| Firebase Authentication | User authentication, sessions | EU (europe-west3) | Art. 28 GDPR |
| Cloud Storage for Firebase | Document file storage | EU (europe-west3) | Art. 28 GDPR |
| Cloud Functions | Background processing, orchestration (transient compute; no Customer Data persisted) | US (us-central1) | Art. 28 GDPR + SCC |
| Cloud CDN | Content delivery (cached, encrypted) | Global edge | Art. 28 GDPR |
| Cloud Monitoring | Performance and error logging | EU (europe-west3) | Art. 28 GDPR |
| Vertex AI | AI model inference (primary) | EU (europe-west3) | Art. 28 GDPR |
8.2 Google's Role and Obligations: Google LLC processes Customer Data under the Google Cloud Data Processing Addendum (cloud.google.com/terms/data-processing-addendum), which incorporates:
- EU Standard Contractual Clauses (2021/914), Modules Two and Three;
- GDPR Article 28 processor obligations;
- EU-US Data Privacy Framework certification;
- Subprocessor governance with 30-day notice for new subprocessors.
8.3 Data Flow Architecture
User → Legalica Platform (application layer)
↓
Google Cloud Platform (infrastructure layer)
↓
├─ Cloud Firestore (database — EU)
├─ Firebase Auth (authentication — EU)
├─ Cloud Storage (files — EU)
├─ Cloud Functions (transient compute — us-central1)
└─ Vertex AI / Third-Party LLMs (AI inference)8.4 Data Location and Residency:
- Primary data location: Google Cloud europe-west3 (Frankfurt, Germany) — all persistent storage;
- Serverless compute: Cloud Functions execute transiently in us-central1 (Iowa, USA); no Customer Data is persisted there (see Section 3.7 of the Terms of Service);
- AI inference: processed via a multi-provider AI Cascade (Google Vertex AI/Gemini → Moonshot AI/Kimi → Groq/Meta Llama → local models via Ollama). EU-based processing is used for the primary provider; fallback providers in the US and China operate under the transfer mechanisms in Section 9 and zero-data-retention terms. Locally executed models involve no external data transfer at all;
- An automated cross-region backup is planned but not yet implemented; see Section 11.7 of the Terms of Service.
8.5 Google's Limitations: Per the Google Cloud Terms of Service: (a) Google has no obligation to assess Customer Data for legal compliance; (b) Google's notification of a Data Incident is not an acknowledgment of fault; (c) Google disclaims warranties and limits liability per its own terms; (d) Google may process data in any country where it maintains facilities unless a data location commitment is in place.
Legalica has configured all persistent data storage within the EU (europe-west3). Transient compute and certain Third-Party LLM API calls route to endpoints outside the EU; such transfers are protected as described in Section 9.
9. INTERNATIONAL DATA TRANSFERS
9.1 EU Transfers: All intra-EU transfers are permitted under GDPR Chapter V without additional safeguards.
9.2 Transfers to Third Countries (Non-EU): Transfers to the United States, China, and other third countries are conducted via:
| Mechanism | Application | Status |
|---|---|---|
| EU-US Data Privacy Framework | Google LLC | Certified |
| SCC 2021/914 Module Two | Controller → Processor transfers (incl. Google Cloud Functions us-central1, Groq Inc.) | Executed |
| SCC 2021/914 Module Two | Moonshot AI (China) — AI cascade fallback #2 | SCC execution and TIA finalization in progress (pre-launch) |
| Supplementary measures | Encryption in transit (TLS 1.3); zero data retention at AI providers; no model training | Implemented |
9.3 Transfers to China (Moonshot AI): When the primary and secondary cascade routes are unavailable, User Input may be processed by Moonshot AI (Beijing Moonshot AI Technology Co., Ltd.) on servers outside the EU. This transfer relies on transient-processing (zero-retention) terms and a contractual no-training prohibition; execution of the EU Standard Contractual Clauses (2021/914) and finalization of the supporting Transfer Impact Assessment are in progress and are tracked for completion before this fallback route is relied upon in production. Only the prompt and minimal context necessary for the response are transmitted. Users and Enterprise customers who prefer EU-only processing may request EU-only cascade routing (which disables the China fallback) via privacy@legalica.app.
9.4 Transfer Impact Assessment (TIA): Legalica has conducted a TIA for third-country transfers. A summary is available upon request at privacy@legalica.app.
9.5 Government Access: If Legalica or a subprocessor receives a government access request: (a) we will notify you unless prohibited by law; (b) we will challenge the request if grounds exist; (c) we will disclose only the minimum required by law.
PART II — DATA PROCESSING AGREEMENT
10. PROCESSING DETAILS (GDPR ARTICLE 28)
10.1 Subject Matter: Processing of Personal Data submitted by Controller and Authorized Users through the Platform.
10.2 Duration: Duration of Controller's Platform use plus applicable retention periods.
10.3 Nature and Purpose:
| Nature | Collection, storage, organization, use, disclosure by transmission, erasure |
| Purpose | Providing Platform services: AI legal research, document drafting, corporate intelligence |
| Data Subjects | Controller's clients, employees, counterparties, and other individuals in User Input |
| Categories | Names, contact info, professional titles, corporate affiliations, legal case details, financial information |
| Special Categories | Not intended; may occur if included in User Input by Authorized Users |
10.4 Controller Warranties: Controller warrants: (a) all necessary consents obtained; (b) appropriate notices provided to Data Subjects; (c) no violation of Applicable Law; (d) no submission of Personal Data in violation of data protection obligations.
11. PROCESSOR OBLIGATIONS
11.1 Documented Instructions: Legalica processes Personal Data only on documented instructions from the Controller, unless required by Union or Member State law.
11.2 Confidentiality: All persons authorized to process Personal Data are bound by confidentiality obligations.
11.3 Security Measures:
| Category | Implementation |
|---|---|
| Encryption in transit | TLS 1.3 |
| Encryption at rest | AES-256 (Google Cloud default encryption) |
| Key management | Google Cloud KMS |
| Access controls | Role-based access, least-privilege principles, strong authentication for internal access |
| Network security | Google Cloud VPC and firewall rules; DDoS absorption at Google's network edge |
| Data isolation | Firestore/Storage security rules enforcing per-user isolation |
| Audit logging | Google Cloud Monitoring and Firebase diagnostics |
| Authentication | Firebase Authentication with hashed credentials and rate limiting |
11.4 Subprocessor Engagement: Legalica may engage subprocessors per Section 15. At least 14 days' notice for new subprocessors. Legalica remains fully liable for subprocessor performance.
11.5 Data Subject Rights Assistance: Legalica assists Controller in responding to Data Subject rights requests under GDPR Chapter III.
11.6 Compliance Assistance: Legalica assists Controller with: Art. 32 (security), Art. 33 (breach notification), Art. 34 (communication), Art. 35 (DPIA), Art. 36 (prior consultation).
11.7 Return or Deletion: Upon termination, Legalica will delete or return all Personal Data per Controller's choice, unless storage is required by law.
11.8 Audit Rights: (a) Once per calendar year upon 30 days' notice; (b) additional audits after a breach, material non-compliance, or supervisory authority order; (c) audit scope limited to systems relevant to Controller's data; (d) Legalica cooperates and provides access.
11.9 Documentation: Legalica makes available all information necessary to demonstrate compliance with Art. 28 GDPR.
12. AI ACT TRANSPARENCY OBLIGATIONS
Legalica is a deployer of general-purpose AI (GPAI) models within the meaning of Regulation (EU) 2024/1689 (AI Act). Legalica ensures its AI-related processing complies with:
- (a) Art. 50 (Transparency): users are informed that they interact with an AI system (the Platform is expressly presented and operated as an AI system), and AI-generated documents exported from the Platform carry an AI-content notice;
- (b) Arts. 53–55 (GPAI obligations): these obligations rest with the providers of the underlying models (Google, Moonshot AI, Groq/Meta, open-source model authors), not with Legalica as deployer;
- (c) Human oversight by design: every AI Output is subject to user review; nothing is auto-filed or auto-sent;
- (d) DPIA support: documentation and assistance for DPIAs involving AI processing, including assessments of automated decision-making risks, algorithmic bias, and data subject rights.
13. DATA BREACH NOTIFICATION
13.1 Timeline: Where Legalica acts as processor, it notifies the Controller without undue delay and targets notification within 36 hours of becoming aware of a Personal Data Breach. Where Legalica acts as controller, it notifies the Estonian Data Protection Inspectorate within 72 hours where required by Art. 33 GDPR, and affected data subjects without undue delay where required by Art. 34 GDPR.
13.2 Notification Content: (a) Nature of breach; (b) categories and approximate number of Data Subjects affected; (c) likely consequences; (d) measures taken or proposed; (e) contact point.
13.3 Documentation: All breaches are documented with facts, effects, and remedial actions (Art. 33(5) GDPR).
13.4 Infrastructure Provider Breaches: If a Data Breach originates from Google Cloud infrastructure, Firebase Authentication, or any other Infrastructure Provider: (a) Legalica will notify Controller within 36 hours of learning of the breach from the provider; (b) Legalica will pass through all information provided by the Infrastructure Provider; (c) Legalica's liability is subject to Section 9.3 of the Terms of Service; (d) Controller may also contact Google directly via support.google.com/cloud/contact/dpo.
14. NO-TRAINING COVENANT
14.1 Absolute Prohibition: Personal Data processed under this DPA shall NOT be used to train, fine-tune, or improve any machine learning models, AI systems, or algorithms. Personal Data shall not be included in training datasets for any purpose.
14.2 LLM Subprocessor Obligations: All LLM subprocessors are contractually bound to: (a) process solely for generating responses; (b) not retain beyond response generation; (c) not use for model training; (d) implement zero-retention measures.
14.3 Google-Specific AI Terms: Google Cloud's AI terms state: "Google will not use Customer Data to train or fine-tune any AI/ML models without Customer's prior permission or instruction." This applies to all Google Cloud AI services used by Legalica.
15. SUBPROCESSORS AND INFRASTRUCTURE CHAIN
15.1 Current Subprocessors: The current list of subprocessors is maintained on the Subprocessors page, which forms part of this Policy. Summary:
| Subprocessor | Service | Location | Role | Transfer Mechanism |
|---|---|---|---|---|
| Google LLC | Cloud infrastructure, auth, storage, AI (Vertex AI/Gemini) | EU (storage) / US (transient compute) | Key Infrastructure Provider & Primary LLM | SCC 2021/914, EU-US DPF, zero-retention |
| Moonshot AI (Beijing Moonshot AI Technology Co., Ltd.) | AI language model — Kimi (cascade fallback #2) | China | LLM provider (fallback) | SCC 2021/914 + TIA, zero-retention contractual obligation |
| Groq, Inc. / Meta Platforms (Llama) | AI language model — Llama via Groq API (cascade fallback #3) | US | LLM provider (fallback) | SCC 2021/914, zero-retention |
| Ollama (self-hosted / local) | Local model inference (cascade fallback #4) | Local (no external transfer) | Local LLM runtime (fallback) | No transfer — processed within application layer |
| GLEIF | LEI data | International | Registry (public data) | Public data |
| OpenCorporates | Corporate registry | International | Registry (public data) | Public data |
Note — payments: Creem (Armitage Labs OÜ, Estonia), our Merchant of Record, is not a subprocessor: it processes buyer payment data as an independent controller (see Section 7.4) and is therefore listed separately, not in the subprocessor table above.
15.2 Infrastructure Chain Disclosure
Full processing chain for a typical user query:
1. User submits query → Legalica application (Cloud Functions, us-central1 — transient) 2. Authentication check → Firebase Authentication (Google, EU) 3. Data retrieval → Cloud Firestore (Google, EU) 4. AI processing → AI Cascade: Vertex AI/Gemini (EU) → Kimi/Moonshot (China) → Groq/Llama (US) → Ollama (local) Each provider queried sequentially; fallback on failure. Zero-data retention enforced. 5. Response storage → Cloud Firestore (Google, EU) 6. Document attachment → Cloud Storage (Google, EU) 7. Purchase/payment → Creem checkout (Merchant of Record, independent controller)
15.3 Subprocessor Changes: At least 14 days' advance notice for new subprocessors (30 days for Infrastructure Provider changes). Objections may be raised to privacy@legalica.app. If unresolved, Controller may terminate with pro-rata refund.
16. STANDARD CONTRACTUAL CLAUSES
16.1 Incorporation: Where Customer Data is transferred to a third country without an adequacy decision, EU SCC 2021/914 are incorporated by reference:
- Module Two: Controller to Processor
- Module Three: Processor to Subprocessor
16.2 SCC Specifications:
| Clause | Selection |
|---|---|
| Clause 7 (Docking) | Included |
| Clause 9 (Subprocessors) | Option 2 — general written authorization |
| Clause 11 (Redress) | privacy@legalica.app as contact point |
| Clause 13 (Supervisory authority) | Andmekaitse Inspektsioon (Estonia) |
| Clause 17 (Governing law) | Law of Estonia |
| Clause 18 (Forum) | Courts of Estonia |
16.3 Annexes:
- Annex I.A (Parties): Data Exporter: [Customer]; Data Importer: Legalica OÜ
- Annex I.B (Processing): As described in Section 10
- Annex I.C (Supervisory authority): Andmekaitse Inspektsioon
- Annex II (Security measures): As described in Section 11.3
- Annex III (Subprocessors): As described in Section 15 and on the Subprocessors page
PART III — COOKIE POLICY
17. COOKIE TYPES AND PURPOSES
Legalica uses a minimal set of cookies and similar technologies. We do not use advertising cookies, marketing pixels, or cross-site tracking technologies of any kind.
17.1 Strictly Necessary (Essential): Cannot be disabled. No consent required (Directive 2002/58/EC, Art. 5(3) exemption).
| Item | Provider | Purpose | Duration |
|---|---|---|---|
| Authentication tokens | Firebase Authentication (Google) | Session state, sign-in persistence (stored in browser storage, not as marketing identifiers) | Session |
| klaro | Legalica (Klaro open-source consent manager) | Stores your cookie-consent choice (first-party cookie) | 365 days |
| Security tokens | Legalica / Firebase | CSRF and request integrity protection | Session |
17.2 Performance & Analytics: Consent required. Disabled by default until you accept.
| Cookie | Provider | Purpose | Duration |
|---|---|---|---|
| _ga | Google Analytics 4 | Distinguishes unique visitors (aggregate statistics) | 2 years |
| _ga_* | Google Analytics 4 | Maintains session state | 2 years |
Google Analytics is configured with IP anonymization and is used only for aggregate usage measurement (page views, session counts). The analytics cookies (_ga, _ga_*) are set only after you consent via the cookie banner. If you do not consent, no analytics cookies are set or read; Google may then receive only anonymous, cookieless "pings" (functional and aggregate, non-identifying information such as browser type and country) used to produce aggregate statistical modeling. Google Analytics data is not used for advertising, and no Google Ads, Google Signals, or remarketing features are enabled.
17.3 Functionality and Preferences: We do not use functionality cookies. Interface preferences (such as your language selection) are stored in your browser's local storage or in your account settings — not in cookies — and are not transmitted to third parties. Such storage is limited to what is strictly necessary to provide the service you request.
18. CONSENT MANAGEMENT
18.1 Consent Banner: Upon first visit, a compact notice presents: (a) "Accept" — analytics cookies enabled; (b) "Reject" — only essential cookies; both options are displayed with equal prominence; (c) "Settings" — granular control. Non-essential cookies are never set before you make an active choice; continuing to browse is not treated as consent. Once you choose, the banner does not reappear for 365 days, unless you reopen it earlier yourself or we materially change our cookie practices (in which case we ask again).
18.2 Granular Control: The Settings panel (open-source Klaro consent manager) allows you to toggle Google Analytics independently. Essential items remain always active and cannot be disabled because the Platform would not function without them.
18.3 Consent Record: Your choice is stored in a first-party cookie named "klaro" for 365 days. If you are signed in, we additionally keep a record of your choice (time, choice, policy version) in our Firebase database as proof of consent (GDPR Art. 7(1)). You may modify your choice at any time via the "Cookie Settings" link in the website footer — withdrawal is as easy as giving consent — or by contacting privacy@legalica.app.
18.4 Withdrawal: Consent may be withdrawn at any time, as easily as it was given, without affecting the lawfulness of processing before withdrawal. Non-essential cookies are immediately disabled upon withdrawal.
18.5 Browser Controls: Users may also control cookies via browser settings. Disabling cookies may affect Platform functionality.
19. FIRST-PARTY VS. THIRD-PARTY COOKIES
First-party: Set by Legalica — consent record, preferences;
Third-party: Set by Google — Analytics (consent-gated, aggregate measurement only) and Firebase Authentication (essential). Subject to Google's privacy policy.
Advertising: None. Legalica does not set or permit any advertising, retargeting, or marketing cookies or pixels, and does not engage in behavioral profiling of sensitive categories.
PART IV — DATA RETENTION
20. RETENTION SCHEDULE
20.1 Account Information
| Data | Retention | Basis |
|---|---|---|
| Name, email, profile | Account duration + 2 years | Contract + legal obligation |
| Credentials | Account duration | Contract |
| Login history | 12 months | Security (legitimate interest) |
| Cookie consent records (proof of consent) | Account duration + 2 years | Accountability (GDPR Art. 5(2), 7(1)) |
| Subprocessor-update subscription email | Until unsubscription or discontinuation of the notice list | Consent |
20.2 User Input and AI Output
| Data | Retention | Basis |
|---|---|---|
| Queries/search terms | Session only (at AI providers — zero retention) | No-training covenant |
| Uploaded documents | Account duration or user deletion | Contract |
| AI Output | Account duration or user deletion | Contract |
| Chat history | Account duration or user deletion | Contract |
20.3 Corporate Intelligence
| Data | Retention | Basis |
|---|---|---|
| KYC/UBO queries | Session only | Privacy-by-design |
| KYC reports | Account duration or user deletion | Contract |
| Risk assessments | Account + 3 years (if regulatory) | Legal obligation |
| Registry cache | 30 days | Technical necessity |
20.4 Google Workspace Data
All synced data retained only during active sync period. Deleted upon Google Workspace disconnect or account deletion.
20.5 Payment and Billing
| Data | Retention | Basis |
|---|---|---|
| Purchase confirmations (product, amount, date, status) | 7 years | Estonian Accounting Act (Raamatupidamise seadus) § 12 |
| Invoices and VAT records | Issued and retained by the Merchant of Record (Creem) for purchases processed by it | Merchant of Record arrangement |
20.6 Logs and Analytics
| Data | Retention | Basis |
|---|---|---|
| Server access logs | 12 months | Security |
| Error logs | 6 months | Stability |
| Security event logs | 24 months | Legal obligation |
| Aggregated analytics | Indefinite (anonymized) | Improvement |
21. DELETION PROCEDURES
21.1 User-Initiated Deletion: Individual documents and conversations deleted immediately upon user action.
21.2 Account Deletion:
| Phase | Timeline |
|---|---|
| Request verification | Within 7 days |
| Active data deletion | Within 30 days |
| Backup purge | Within 90 days (consistent with provider deletion lifecycles) |
| Deletion certificate | Upon request |
21.3 Automated Deletion: Session data: immediately after session ends; Cached data: per TTL (typically 30 days); Expired tokens: upon expiration; Orphaned files: 30 days after parent deletion.
21.4 Legal Holds: Data may be retained beyond standard periods for: litigation hold, court order, legal claims, regulatory audit.
22. USER RIGHTS
22.1 GDPR Rights:
| Right | Article | How to Exercise |
|---|---|---|
| Access | Art. 15 | Email privacy@legalica.app |
| Rectification | Art. 16 | Account settings or privacy email |
| Erasure | Art. 17 | Privacy email or account deletion |
| Restriction | Art. 18 | Privacy email |
| Portability | Art. 20 | Privacy email |
| Objection | Art. 21 | Privacy email |
| Withdraw consent | Art. 7(3) | Cookie Settings or privacy email |
| Lodge complaint | Art. 77 | Andmekaitse Inspektsioon or your local DPA |
Response time: one month (Art. 12(3) GDPR), extendable by two further months for complex or numerous requests, with notice. Identity verification required before processing.
22.2 Rights Under Other Jurisdictions:
| Jurisdiction | Key Additional Rights |
|---|---|
| California (CCPA/CPRA) | Right to know, delete, correct, opt-out, non-discrimination |
| Brazil (LGPD) | Right to explanation of automated decisions |
| Canada (PIPEDA) | Right to access, challenge accuracy |
| Singapore (PDPA) | Right to access, correction |
| South Africa (POPIA) | Right to access, correction, objection |
| Japan (APPI) | Right to disclosure, correction, cessation |
| China (PIPL) | Right to know, decide, limit, access, copy, correct, delete |
PART V — COOKIE CONSENT BANNER
23. BANNER TEXTS AND SETTINGS PANEL
23.1 Primary Banner (Default): The banner is a compact notice (open-source Klaro consent manager), themed in the Platform's neutral grey palette:
- Title: Cookies
- Body: "We use essential cookies to run the site and — with your consent — Google Analytics for aggregate statistics. If you decline, no analytics cookies are set and only anonymous, cookieless measurement applies. No advertising cookies." — followed by a link to this Policy
- CTAs (equal prominence): [Accept] [Reject] — plus a "Settings" link
- Link: Privacy Policy
23.2 Settings Panel Title: Cookie settings
23.3 Category Descriptions for Panel:
- Essential: Necessary for the website to function (authentication, security, consent record). Always active; cannot be switched off.
- Google Analytics: "Aggregate usage measurement (GA4) with IP anonymization. The _ga / _ga_* cookies are set only after your consent; without consent, no analytics cookies are set or read and only anonymous, cookieless pings apply. No advertising features (no Google Ads, no Google Signals, no remarketing)." [Toggle: OFF by default]
23.4 After Your Choice: The notice closes immediately and does not reappear for 365 days. You can change or withdraw your choice at any time via "Cookie Settings" in the footer — withdrawing is as easy as accepting (GDPR Art. 7(3)). On withdrawal, the analytics cookies are deleted automatically and Google is instructed to stop analytics storage.
CHANGES TO THIS POLICY
We may update this Policy. Material changes: 30 days' notice via email and Platform notice. Where mandatory law requires fresh consent for a processing change, we will obtain it.