InfraScan Cloud – Data Security & Privacy Statement
This statement is addressed to everyone who uses InfraScan Cloud at infrascan.soldevelo.com: people who sign in to the dashboard, members of their organizations, and visitors to the website.
1. Privacy Policy
SolDevelo processes personal data in accordance with Regulation (EU) 2016/679 of the European Parliament and of the Council (General Data Protection Regulation, "GDPR"). This statement explains what personal data we process when you visit the website, sign in to InfraScan Cloud or use it, why, and what rights you have. The free, open-source InfraScan CLI runs on your own machines and doesn't send us any data.
2. About personal data
Personal data is any information relating to an identified or identifiable natural person, such as a name, an email address or an IP address.
2.1 Data we collect when you sign in
You sign in with GitHub or Google. We receive and store your verified email address, your name and the address of your profile picture as given by that provider, and your account ID there, so we can recognise you next time. We never see or store your GitHub or Google password.
If you came to us through a link tagged with a campaign (for example one whose address contains utm_source=hn), we keep that tag on our server while you sign in and store it with your account when it's created: the source, medium, campaign and content named in the link. We use it only to count, in aggregate, which channels bring new users, and we don't show it to anyone else. Without such a tag we record that you came directly. The tag of a sign-in that isn't finished is deleted from our server within an hour.
2.2 Data we collect when you use the dashboard
- Your organization's name, its members and their roles (owner, admin, member), and when they last signed in.
- Invitations: the invited person's email address, who invited them and when.
- An audit log of actions in your organization (for example connecting an account, starting or deleting a scan, accepting a risk, changing a role), with the email address of whoever did it and the time.
- Alert settings: the address of the Slack webhook your organization saves for alerts, whether the last alert was delivered, the lowest severity that alerts, and whether you get alert emails.
- API tokens for AI agents: the name given to each token, who created it and when, and when it was last used. We store a token only as a hash, so we can't show it again; revoking a token deletes it.
2.3 Technical data
- Our servers record requests in their logs: IP address, the address requested, the time, the referring page and the browser's user agent. We use them to run the service, investigate errors and protect it from abuse, and to count visits in aggregate (for example how many people opened a page, or came from a given site or campaign), without profiling anyone.
- Two cookies, both strictly necessary, so they don't require consent: a session cookie that keeps you signed in for up to 14 days, and a sign-in cookie that protects signing in with GitHub or Google, which expires after 10 minutes and is deleted when you finish signing in. The website outside the dashboard sets no cookies.
- Your browser's local storage keeps your choice of light or dark theme and the account shown in the overview chart. These settings stay in your browser and aren't sent to us.
2.4 Data in the accounts and repositories you connect
When you connect an AWS account or add a repository, we store what's needed to scan it: the AWS account ID, the role's ARN and the connection's External ID, or the repository's URL. Scans store their results: resource names, identifiers, tags and settings, file paths and short excerpts of code. These can include personal data, such as the names of IAM users or names in resource tags. For this data SolDevelo acts as a processor on behalf of your organization, which remains its controller, and processes it only to provide the service. A data processing agreement is available on request at infrascan-support@soldevelo.com.
Our access to your AWS account is read-only and explicitly can't read secrets or data such as S3 objects, database items, logs or environment variables (see the role's published template). Each scan uses temporary credentials that we keep in memory only and never store.
2.5 What we don't do
We don't use third-party analytics, advertising or tracking cookies, we don't record sessions, and we don't sell personal data or use it for profiling. The visit counts in 2.3 come from our own server logs.
3. Personal Data Administrator
The administrator (controller) of the personal data described in sections 2.1–2.3 is SolDevelo Sp. z o.o., with its registered office at Al. Zwycięstwa 96/98, 81-451 Gdynia, Poland, entered in the National Court Register under KRS 0000332728, NIP 586-224-03-31, REGON 220828585, share capital PLN 60,000.
You can contact us about personal data by email at privacy@soldevelo.com or by post at the address above.
4. Legal basis and the purpose of personal data processing
- Providing InfraScan Cloud: your account, your organization, scans and their history (Art. 6(1)(b) GDPR, performance of a contract).
- Sending you service emails: alerts about your organization's accounts and repositories (new critical or high findings, an AWS account we can no longer connect to), which you can turn off in Settings or with the link in each email, and an invitation when someone invites your address to their organization (Art. 6(1)(b) GDPR for members; Art. 6(1)(f) GDPR, our and the inviting organization's interest in letting you know, for invited people).
- Keeping the service secure and working: server logs, the audit log, limits and abuse prevention (Art. 6(1)(f) GDPR, our legitimate interest).
- Learning which channels bring users: the campaign tag stored when your account is created, and aggregate visit counts from server logs (Art. 6(1)(f) GDPR, our legitimate interest in understanding and improving how people find the service).
- Answering your questions and requests, including support (Art. 6(1)(b) or (f) GDPR).
- Meeting legal obligations, such as keeping records required by law (Art. 6(1)(c) GDPR).
- We don't send marketing emails; if that changes, only with your consent (Art. 6(1)(a) GDPR).
Providing personal data is voluntary, but without signing in you can't use the dashboard.
We keep personal data for these periods:
- Account and organization data, including the campaign tag you signed up with: while your account exists, and up to 30 days after you ask us to delete it.
- Scans and findings: until an owner or admin deletes them, or automatically after the period your organization sets in Settings (scan history), or when your organization is deleted.
- Invitations: deleted 30 days after they're accepted, declined, withdrawn or expire (they expire after 30 days).
- Audit log: 12 months; older entries are deleted automatically.
- Server logs: 30 days.
- Database backups: 14 days, after which deleted data is gone from them too.
5. What rights are provided to the persons whose data we process
You have the right to:
- access your personal data and receive a copy of it,
- have it corrected,
- have it deleted or its processing restricted,
- object to processing based on our legitimate interest,
- withdraw consent at any time, where processing is based on consent,
- receive your data in a portable format.
Send requests by email or post to the addresses in section 3; we answer within one month. You can also lodge a complaint with the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych), ul. Stawki 2, 00-193 Warsaw.
Your name, email address and profile picture come from your GitHub or Google account; change them there and they update when you next sign in.
6. Additional important information
Means of security
We protect personal data with organizational and technical measures: encrypted connections (HTTPS), access to the service's data limited to the people who run it, and separation of each organization's data, which our automated tests check for every part of the API. SolDevelo's information security management system is certified to ISO/IEC 27001.
The rules for data exposure
We share personal data only with providers that help us run the service, and with authorities when the law requires it:
- Amazon Web Services: hosting of the service and its database, and sending our emails (Amazon SES), in AWS's US East (N. Virginia, us-east-1) region in the United States.
- GitHub (Microsoft) and Google: signing in, when you choose them.
- Slack, when your organization sets up alerts: we send alert messages (names of accounts and repositories, findings and resources) to the Slack channel your organization chose. Slack processes them for your organization, under its agreement with Slack.
- AI agents your organization connects: with an API token created in the dashboard's settings, an AI agent of your choice (for example Claude Code or Cursor) can read your organization's accounts, repositories, findings and suggested fixes. We answer its requests; we don't send your data to any AI provider ourselves. The provider of that agent processes what it reads for your organization, under its agreement with them.
- Google Fonts: the website's fonts are loaded from Google's servers, which receive your IP address.
The service is hosted in the United States, and some of these providers are based there. Transfers of personal data outside the European Economic Area rely on the EU–US Data Privacy Framework or the European Commission's standard contractual clauses.
Automated decision-making processes
We don't make decisions about people based solely on automated processing, including profiling. Grades and findings describe the infrastructure that was scanned, not people.
Removal of customer-provided data
Owners and admins can delete scans and remove members in the dashboard. To delete your account or your organization, write to us at privacy@soldevelo.com or infrascan-support@soldevelo.com; we delete it within 30 days.
Information on user tracking
InfraScan Cloud uses no third-party analytics, no tracking cookies and no session recording. We learn which channels bring users only from the campaign tag stored at sign-up and from aggregate counts of our own server logs (2.1, 2.3). If we add any other tool, we'll update this statement and ask for consent where it's required.
Public scan reports
Reports of scans of public repositories made with the earlier InfraScan website are published at /report/…. They contain the repository's name and address and findings about its public code, not data about the people who started the scans. If you maintain such a repository and want its report removed, write to us.
Changes to this statement
We'll update this statement when the way we handle data changes, and tell signed-in users about significant changes before they take effect.