Privacy policy
DevTeam · Last updated 23 September 2026
This policy covers DevTeam — the internal services used by the development teams working on the DevTeam project. It explains what we receive when you sign in with a Google account, what we do with it, and how to have it removed.
These services are operated by the DevTeam engineering team, who are the data controller for the purposes of this policy. Contact: admin@devteam.guru.
What we receive from Google
When you choose to sign in with Google, we ask Google for two standard OpenID Connect scopes. You see and approve them on Google's own consent screen.
| Scope | What it gives us |
|---|---|
email | Your email address and whether Google has verified it |
profile | Your name, profile picture URL, locale, and your Google account identifier |
That is the whole of it. We do not request, and cannot read, your Gmail, Drive, Calendar, Contacts, Photos or any other Google service.
What we do with it
We use it for exactly one thing: to work out which existing account belongs to you, so you can sign in without a separate password.
Signing in with Google does not create an account here. Automatic account creation from Google sign-in is disabled. If no account is already linked to your Google identity, the sign-in is refused and nothing about you is stored.
We do not use this information for advertising, profiling or analytics.
What we store
For accounts that are linked to Google, our database holds:
- your Google account identifier (an opaque number Google assigns), which is what we match on;
- your name and email address, as part of your account;
- the URL of your Google profile picture, used as your avatar.
We do not store Google passwords — we never see them — and we do not retain Google access or refresh tokens beyond the sign-in itself.
Separately from Google sign-in, these services store what you would expect of engineering tooling: the code you push, your comments and issues, your build history, and the sign-in timestamps and IP addresses kept for security purposes.
Who we share it with
Nobody. We do not sell, rent or share this data with third parties. It is not used for advertising and it is not passed to analytics providers.
Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Where it is held
On infrastructure we operate ourselves. These services are not open to the public: most of them are unreachable from the public internet, and access is limited to team members and to our own build automation.
How long we keep it
For as long as your account exists. When an account is removed, the linked Google identifier, name, email address and avatar reference are removed with it.
Content you contributed — commits, merge requests, comments — may remain, since it forms part of the project history and of records other people rely on. Git commits in particular carry author details inside the repository history itself and cannot be rewritten without altering that history.
Unlinking or deleting your data
You can, at any time:
- revoke this application's access from your Google account permissions page, which stops any further sharing from Google's side;
- ask us to unlink Google from your account, or to delete the account entirely, by writing to admin@devteam.guru.
We act on such requests within 30 days.
Children
These are internal tools for our engineering teams. They are not directed at children and are not intended for use by anyone under 16.
Changes to this policy
If this policy changes we will update the date at the top of the page. Material changes affecting people with accounts will also be communicated directly.