Privacy Policy

1. Who we are

DeployMeter is operated by SkyStar Solutions, Lda, a company registered in Portugal (NIPC 517189020) — "DeployMeter", "we" or "us" in this policy.

For anything related to your personal data, contact us at privacy@deploymeter.com.

2. Our two roles

We are the controller of the data needed to run our relationship with you: your user account, your organization's billing, support requests, and visits to deploymeter.com.

For the engineering data that a customer connects to DeployMeter — pull requests, commits, pipelines, issues and the people behind them — the customer is the controller and we act as its processor, under our Data Processing Agreement (Art. 28 GDPR). If you are a developer whose employer uses DeployMeter, your employer decides what is collected and who in your organization can see it; please contact them first, and we will help them answer you.

Data Processing Agreement

3. What we collect

Depending on how DeployMeter is used, we process:

Account data — name, email address, profile picture, your password (stored only as a one-way hash), the sign-in accounts you link (GitHub, your company's single sign-on) and your role in the organization. When you sign in we record the session's IP address and browser (user agent) and keep a sign-in history, to protect your account.
Organization and billing data — organization name, plan, subscription state and billing contact. Card details are entered directly with Stripe and never reach our systems.
Engineering data from the sources an organization connects (GitHub, GitLab, Jira, Linear, Slack): pull request and commit metadata, author names, emails and usernames, reviews, pipeline runs, deployments, issues and stand-up check-ins.
Code changes — pull request diffs are fetched to analyse them. We do not keep your source code: we store the derived metrics and analysis, and an organization can set a retention period for the raw analysis output.
Local tracking data, only if a developer installs our command-line tool: the repository name and the developer's GitHub username, the times of coding activity, branch names, commit identifiers and change sizes. Never file contents.
Coding-assistant detection — not active yet: it starts only after our data protection impact assessment is complete. When active, and only where the organization's setting and the developer's own choice allow it, the command-line tool records which coding assistants, from a fixed list, were running inside that repository's folder. Nothing else: no process list, arguments, file paths or folder names. The organization sees how many people chose each option, never who. These records are cleared after 90 days, and a developer can turn detection off for themselves at any time.
AI tool usage and cost — Copilot seats and usage, and spend reported by AI coding tools an organization chooses to connect.
Survey answers — developer experience surveys can be anonymous, and results are only shown in aggregates of at least three respondents.
Technical data — IP addresses and request logs used to keep the service secure and to limit abuse.

4. Why we use it, and on what legal basis

To provide the service you or your organization signed up for — accounts, metrics, analysis, notifications (performance of a contract, Art. 6(1)(b) GDPR).
To bill subscriptions and keep accounting records (legal obligation, Art. 6(1)(c)).
To keep the service secure, prevent abuse and fix problems (legitimate interests, Art. 6(1)(f)).
To improve DeployMeter using aggregated, non-identifying statistics (legitimate interests, Art. 6(1)(f)).
When we process engineering data as a processor, we do so only on the customer's documented instructions.

We do not sell personal data, we do not use it for advertising, and we do not make decisions with legal or similarly significant effects about anyone based solely on automated processing.

5. AI analysis

Some features use Anthropic, our AI provider: pull request diffs, titles and descriptions (to estimate effort and classify changes), free-text survey answers (only for questions that reach the anonymity threshold), stand-up check-ins, CI failure details, aggregated team metrics, and messages sent to the in-app support assistant. We never send integration tokens or account credentials. Diffs are sent as they are, so a secret committed to a pull request would be part of what is analysed. Anthropic processes this data under commercial terms that do not allow it to train its models on it.

AI analysis produces metrics about work items, not ratings of people. Organizations control, through visibility policies, whether individual figures are shown at all.

7. Where your data lives

Our servers and database are hosted in Germany, in the European Union. Some subprocessors — Stripe, Anthropic and Slack — process data in the United States; those transfers are covered by the European Commission's Standard Contractual Clauses (2021/914) or an adequacy decision.

8. How long we keep it

Account and organization data — for as long as the account is active.
Sign-in data — a session's IP address and browser are deleted 30 days after the session expires; the sign-in history is kept for 12 months.
When an organization is deleted, its data is kept for a 30-day grace period, in case the deletion was a mistake, and then permanently erased — except the billing and accounting records we are legally required to keep, which are held with Stripe and in our accounting.
When the last member of an organization deletes their account, nobody is left who could cancel the deletion, so the organization and its data are erased right away, without the grace period.
Raw analysis output — for the retention period the organization chooses, or until the organization is deleted.
File paths changed by each merged pull request, and the maintainability scores derived from them — we store the paths, never the file contents; the retention period the organization chooses deletes both, or they go when the organization is deleted.
Incoming webhook payloads — deleted once processed; those that cannot be processed are deleted after 30 days.
Billing and accounting records — for the period required by Portuguese law.
Backups expire on a rolling schedule; erased data disappears from them when they expire.

9. Your rights

Under the GDPR you can ask to access, rectify or erase your personal data, to restrict or object to its processing, and to receive it in a portable format. Organization owners can export all of their organization's data, anonymize or delete a developer, and delete the organization directly from the app.

To exercise any right, write to privacy@deploymeter.com. We answer within one month. If your data reached us through your employer, we will coordinate with them as the controller.

You also have the right to lodge a complaint with a supervisory authority — in Portugal, the Comissão Nacional de Proteção de Dados (www.cnpd.pt).

10. Cookies

We only use cookies that the service needs: to keep you signed in and secure, and to remember preferences such as your language and selected period. We do not use analytics or advertising cookies, and we do not load third-party trackers.

11. Security

Integration tokens are encrypted with AES-256-GCM, all traffic is encrypted in transit, every query is scoped to a single organization, and sensitive access is recorded in an audit log. The details are on our Security & Trust page.

Security & Trust

12. Children

DeployMeter is a professional tool and is not intended for anyone under 16.

13. Changes to this policy

When we change this policy we update the date at the top, and for material changes we notify organization owners in advance.