Data Handling

This document explains how oklido collects, processes, stores, and protects your data.

Data Collection

What We Collect

Data CategoryExamplesPurpose
IdentityName, emailAccount management
DocumentsUploaded filesCore service
MetadataFile names, types, datesOrganisation, search
UsageFeatures used, timestampsService improvement
TechnicalIP address, browserSecurity, debugging

How We Collect Data

  1. Directly from you - Account registration, uploads
  2. Automatically - Usage tracking, error logging
  3. From third parties - Auth0 (authentication), email providers

What We Don't Collect

  • Government ID numbers (unless in documents you upload)
  • Health information (unless in documents you upload)
  • Biometric data
  • Location tracking

Data Processing

Document Processing

When you upload a document:

  1. Upload - File received over encrypted connection
  2. Storage - Encrypted and stored in AWS S3
  3. Extraction - Text extracted for search and classification
  4. Classification - AI determines document type
  5. Indexing - Metadata indexed for search

Email Processing

When syncing from Gmail/Outlook:

  1. Access - Emails read via OAuth (read-only)
  2. Filter - Only matching emails processed
  3. Extract - Attachments extracted
  4. Process - Same as document upload
  5. Email content - Read but NOT stored

Data Storage

Primary Storage

DataLocationEncryption
DocumentsAWS S3 (London)AES-256
DatabaseAWS RDS (London)AES-256
BackupsAWS S3 (London)AES-256

Security Measures

  • Encryption at rest (AES-256)
  • Encryption in transit (TLS 1.3)
  • Access controls (IAM, RBAC)
  • Audit logging
  • Regular security testing

Data Access

Who Can Access Your Data

RoleAccess Level
YouFull access to your data
Your team membersBased on assigned role
External usersOnly shared documents
oklido staffNo access (by design)
AWSInfrastructure only (encrypted)

oklido Staff Access

oklido staff cannot access your documents or data:

  • No "god mode" or admin access to customer data
  • Support staff can only see account metadata
  • All access is logged and audited
  • Background checks for all employees

Exceptions

We may access data only if:

  • You explicitly request support assistance
  • Required by law enforcement with valid legal process
  • Necessary to investigate abuse or security incidents

Data Sharing

We Share Data With

RecipientPurposeData Shared
AWSInfrastructureEncrypted documents
Auth0AuthenticationEmail, name
StripePaymentsBilling info
VercelHostingAnonymous usage

Full subprocessor list →

We Never

  • Sell your data
  • Share data for advertising
  • Allow third-party tracking
  • Share with data brokers

Data Minimisation

We only collect data necessary for:

  • Providing the service you signed up for
  • Maintaining security
  • Complying with legal requirements
  • Improving the service (anonymised)

Data Quality

You can update or correct your data:

  • Profile data - Edit in Settings
  • Document metadata - Edit in document details
  • Billing information - Update in Subscription settings
  • Other data - Contact support

Data Security

Comprehensive security measures protect your data:

Incident Response

If a data breach occurs:

  1. We contain and investigate immediately
  2. We notify affected users within 72 hours
  3. We notify the ICO if required
  4. We take steps to prevent recurrence

Full incident response policy →

Questions

For questions about data handling: