Privacy policy

What Squadlog collects, why, and what it never keeps.

Squadlog processes data about your employees’ work on GitHub. This policy is written to be read, not skimmed. It covers the service at squadlog.app, the iOS app and the emails we send.

Version 1.1 · effective 4 December 2026
In short
  • We read GitHub metadata: authors, dates, PR and review events, diff sizes.
  • Each commit diff is read once, in memory, by our own models on our own servers, then discarded.
  • We never store source code, issues, comments or secrets.
  • We never send code or data to a third-party AI provider, and never train on your data.
  • We take no automated decision about a person. Effort scores and rankings are shown to your managers only, as information for a human.
  • Everything is hosted in Paris (EU). Raw events kept 12 months, team aggregates 12 months.

01 Who we are

Squadlog is operated by Kadiaak OÜ, a private limited company registered in Estonia (registry code 16357744), Sepapaja tn 6, 15551 Tallinn. Kadiaak OÜ is the data processor for the data of your workspace and the data controller for your account data (name, email, billing).

Your company is the data controller for the data about its developers. This policy explains what we do on your behalf and what we do for our own account.

Company
Kadiaak OÜ, Tallinn, Estonia
Registry code
16357744
VAT
EE102437021
EU representative
Not required: established in the EU

02 What we collect from GitHub

Through a read-only GitHub App installed by your organization, we receive: repository names and visibility, branch names, commit SHAs, authors, timestamps and line counts, pull request titles, numbers, states, authors, requested reviewers, review events and timestamps, and the login, display name and avatar URL of contributors. We do not request access to issues, discussions, comments, actions, packages or secrets.

When a commit lands on a tracked branch or a pull request merges, we fetch its diff. The diff is read once, in memory, to produce a one-line summary and an effort score. It is never written to disk, never logged and discarded immediately. Repositories you exclude are never fetched.

03 What we collect about you

For managers and workspace owners: name, email, password hash, passkeys or GitHub sign-in, time zone, notification preferences, and the actions you take in the product (pages opened, reports generated) for security and support. For billing: company name, VAT number, address and the last four digits of the card, held by our payment provider.

If you use the iOS app, we also keep for each phone its push token, platform, time zone and app version, to deliver notifications and apply quiet hours. That record is deleted when you sign out of the app, when the app is removed from the phone, or with your account.

04 Why we process it

To show team dashboards, timelines, alerts, digests and reports to the managers you designate. To write plain-language summaries and effort scores. To send the emails you enabled. To secure the service and bill the subscription. We do not use any of it for advertising, profiling outside the product, or training models.

Legal basis (your data)
Contract (art. 6.1.b GDPR), legitimate interest for security
Legal basis (developer data)
Your instructions as controller; your own basis is usually legitimate interest with information of employees
Automated decisions
None. Art. 22 GDPR does not apply.

05 Where it is processed

All production systems, databases and backups run in the European Union, in Paris, France: Laravel Cloud (Laravel Holdings Inc.) hosts the service on Amazon Web Services infrastructure, region eu-west-3, under standard contractual clauses. Transactional email is sent via Resend under standard contractual clauses; emails contain no source code. Payments are processed by Stripe Payments Europe Ltd. Push notifications of the iOS app go through Expo (650 Industries Inc.), then Apple Push Notification service. Both receive the phone’s push token and the text of the notification (for example a repository and pull request reference, a team name or the first sentence of a report), never source code. No other sub-processor receives workspace data.

Hosting
Laravel Cloud (Laravel Holdings Inc.), US, SCC
Infrastructure
Amazon Web Services EMEA SARL, eu-west-3 (Paris, FR)
Email
Resend, US, SCC
Payments
Stripe Payments Europe Ltd, IE
Push notifications
Expo (650 Industries Inc.), US, SCC, then Apple Push Notification service
AI inference
Our own models. No third party.

06 How long we keep it

Raw events: 12 rolling months. Team aggregates and generated summaries: 12 months after the period they describe. Reports: until deleted by a manager. Account data: for the life of the account plus 30 days. Backups: 30 days. When a workspace is deleted, everything is purged within 30 days and we confirm by email.

07 Your rights and your developers’ rights

Developers can ask their employer, who can use the product to export (Settings › Compliance › Export a member’s data) or erase (Erase a member) all data about a person in one action. Managers can export or delete their own account data from Settings. Anyone can write to [email protected]; we answer within 30 days and usually within a few days. You may lodge a complaint with the Estonian Data Protection Inspectorate (AKI) or your local authority.

08 Informing employees

We provide an information notice for your developers, describing what is tracked, what is not and their rights, a works council information template and a processing record you can attach to your own register; informing your employees remains your responsibility as controller. The product takes no decision about a person: effort scores and rankings are information for a human manager, and alerts are signals for one.

09 Data processing agreement

Our DPA (art. 28 GDPR) is incorporated into the terms and can be signed online from Settings › Compliance; a countersigned PDF is returned by email. It lists sub-processors, audit rights, breach notification within 48 hours and deletion on termination.

DPA
Online, Settings › Compliance
Breach notification
Within 48 hours of confirmation
Sub-processor changes
30 days’ notice by email

10 Cookies

The marketing site sets no analytics cookies. The app sets the cookies it needs to work: a session cookie, a security token against cross-site request forgery and, if you tick “remember me”, a login cookie. We do not use advertising trackers.

11 Changes

We announce changes to this policy by email to workspace owners at least 30 days before they take effect, with a diff of what changed. Previous versions are available on request.

Questions about this documentWrite to [email protected]. We answer within a working day.