Privacy Policy
SBOMBox is the trade name of Guni Innovations Pte. Ltd. (“SBOMBox”, “we”, “us”). We help software teams generate, score and monitor software bills of materials (SBOMs). Our tools are built so that your source code never leaves your environment and we receive only what you choose to upload. This policy explains what personal data we process, why, and the choices and rights you have.
1. Introduction
This policy covers our website, dashboard, API, CLI, installer, CI integrations (including the GitHub Action and GitLab component), trust center pages and related services (the “Services”). It is written to meet the Singapore Personal Data Protection Act 2012 (PDPA), the EU General Data Protection Regulation (GDPR), the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection (FADP), India’s Digital Personal Data Protection Act 2023 (DPDP Act) and the California Consumer Privacy Act as amended by the CPRA (CCPA), where each applies.
This policy informs you about our processing. It is not a request for consent. Where the law requires consent, for example for non-essential cookies or marketing, we ask for it separately and you can withdraw it at any time.
2. Who we are
- Legal entity: Guni Innovations Pte. Ltd. (Singapore UEN 202302437E).
- Trade name: SBOMBox.
- Registered address: 68 Circular Road #02-01, 049422, Singapore.
- General contact: sia@sbombox.com for support, sales and any other question.
- Security reports: dpo@sbombox.com, or see our vulnerability disclosure policy.
- Data Protection Officer: dpo@sbombox.com. The DPO is also our grievance officer under the DPDP Act.
Contact details for each kind of request are in section 22.
3. Our role in processing personal data
- Controller (data fiduciary under the DPDP Act) for account, authentication, billing, website, cookie, support, sales and privacy-request data. We decide why and how this data is used, and this policy describes it.
- Processor (data intermediary under the PDPA, service provider under the CCPA) for personal data that appears in Customer Content: the SBOMs, package metadata, project data and CI provenance our customers upload. The customer is the controller, decides what to upload, and needs its own lawful basis.
Our Data Processing Addendum governs processing we do as a processor. It applies automatically to every customer: no signature is needed, and a countersigned copy is available on request.
4. Personal data we process
| Category | Examples | Source |
|---|---|---|
| Account | Email address, name, avatar, organisation membership and role | You, or your identity provider (GitHub, GitLab, Google) |
| Authentication & security | Hashed API and OAuth tokens, encrypted TOTP secret, hashed recovery codes, sessions, IP address, user agent | You and your devices |
| CI trust and provenance | Repository, workflow and branch names, run identifiers and commit SHAs from your CI provider’s signed identity token; the trust rules you configure | Your CI provider, when you push from CI |
| Audit log | Actor, action, resource, timestamp, IP address, user agent, outcome | Generated when you use the Services |
| SBOM & project metadata (Customer Content) | Component names, versions, licences, suppliers, hashes, repository names, commit SHAs, CI provenance claims; may include author or maintainer names and emails from package manifests | Your CLI, CI or uploads |
| Billing | Plan, invoices, billing contact. Card data is handled by Stripe and never stored by us | You and Stripe |
| Demo requests & sales contacts | Name, work email, company, phone (optional), team, what you want to see, number of products, current approach, timeline, message, the page you came from, consent record | You, through the Book a demo form |
| Support & privacy requests | Messages, request type, region, relationship to us, authorised-agent details, declaration, verification records | You |
| Website & consent | Consent choices, essential cookies, standard web server logs (IP address, user agent, requested URL); website analytics as described in section 18 | Your browser |
We do not receive source code, build artefacts or secrets. We do not ask for special-category (sensitive) data, government identifiers or children’s data, and Customer Content should not contain them. We do not collect “sensitive personal information” as defined by the CCPA.
5. How we collect personal data
- Directly from you: when you sign up, configure an organisation, request a demo, contact us or make a privacy request.
- From sign-in providers: GitHub, GitLab or Google share your profile and verified email when you choose to sign in with them.
- From your tooling: the CLI, CI action and GitHub or GitLab integrations send the SBOMs and provenance you configure them to send (see section 6).
- From our payment processor: Stripe tells us about payment status and invoices.
- Automatically: essential cookies, server logs and the audit log record how the Services are used. Website analytics follow the choices in section 18.
6. What our CLI, installer, CI integrations and free audit send
Our tools run in your environment. This table lists, for each one, exactly what reaches us and what reaches anyone else, so your security team can approve them without reverse-engineering network traffic.
| Tool or command | Runs on | Sent to SBOMBox | Sent to third parties |
|---|---|---|---|
| sbombox generate, score, check, compliance, fix and share | Your machine or CI runner | Nothing | Nothing by default. share writes an aggregate-only report to a local file |
| Registry enrichment (opt-in, off by default) | Your machine or CI runner | Nothing | Package names and versions, sent directly to the public registry concerned (PyPI, npm, crates.io, Maven Central, deps.dev, ecosyste.ms). Their privacy policies apply |
| sbombox push, sbombox ci, the GitHub Action and the GitLab component | Your CI runner | The SBOM document, project name, commit SHA and the claims in your CI provider’s identity token used to verify provenance | Nothing |
| sbombox login | Your machine | A device-authorisation request. The resulting token is kept in your operating system keyring, or a file only you can read | Nothing |
| Installer (install.sh) | Your machine | A standard download request for the script (IP address, user agent) | Download requests to astral.sh (uv), PyPI (the CLI) and GitHub (the SBOM generator). Downloads are checksum-verified |
| Free SBOM audit at /audit | Our servers | The file you drop, processed in memory to calculate the score, then discarded. It is not stored, logged or used for anything else, and no account is needed | Nothing |
The CLI and CI integrations contain no telemetry, usage analytics or crash reporting. You can run generation, scoring and checks fully offline.
7. How we use personal data
- Provide, secure and support the Services: sign-in, MFA, organisation access, scoring, monitoring and reports.
- Verify where an SBOM came from: check CI identity tokens against the trust rules your organisation set.
- Prevent abuse and keep the Services secure: rate limiting, fraud prevention, tamper-evident audit logging.
- Process payments and keep financial records.
- Send service and security notices, such as sign-in codes, vulnerability alerts and CRA deadline reminders. These are part of the Services and are not marketing.
- Respond to demo requests and sales enquiries, and follow up about them.
- Respond to support and privacy requests.
- Improve the website and product using aggregated usage analytics, with consent or an opt-out as described in section 18. We do not use Customer Content to train AI models.
- Comply with law and establish, exercise or defend legal claims.
We do not use personal data for purposes incompatible with these. If we ever want to, we will update this policy and ask for consent where the law requires.
8. SBOM content: processing and retention
Purpose-limited. We process Customer Content only to provide the Services to the customer that uploaded it: parsing, validating, scoring, matching against vulnerability sources, and showing or sharing results as the customer directs.
Immutable by design. SBOM documents are stored in content-addressed, write-once storage so they can serve as evidence. Erasure therefore works by expiry and by destroying per-tenant encryption keys (cryptographic shredding), rather than by editing objects in place.
Derived metadata. Scores, findings, VEX decisions and audit records are stored separately from the SBOM document and follow the organisation’s retention setting.
Operational reality. Backups, logs and diagnostics may briefly hold fragments of data before they rotate out. They are protected by the same controls and are never used for any other purpose.
9. Public pages and shared reports
SBOMs, projects and reports are private to your organisation by default. Organisation administrators can choose to publish items on a public trust center page, mark an SBOM as public, or create a share link. Anything published this way can be viewed by anyone who has the address, including any names or emails it contains.
- Only organisation owners and administrators can publish.
- You can unpublish or revoke a link at any time; it stops working immediately. We cannot recall copies others have already downloaded.
- Before publishing, remove personal data the audience does not need. If you are named in a published SBOM and want it removed, see section 14.
10. Legal bases for processing
Where the GDPR, UK GDPR, FADP or PDPA applies we rely on the bases below. Under the DPDP Act we process personal data on the basis of consent or a legitimate use under section 7.
| Activity | GDPR / UK GDPR / PDPA | DPDP Act (India) |
|---|---|---|
| Accounts and providing the Services | Contract | Consent, or legitimate use where you provided the data for this purpose |
| Processing Customer Content on customer instructions | Customer’s basis; we act as processor | Customer is the data fiduciary |
| CI provenance verification | Contract; legitimate interests in the integrity of evidence | Legitimate use |
| Security, abuse prevention and audit logging | Legitimate interests; legal obligation | Legitimate use |
| Billing, tax and accounting records | Contract; legal obligation | Legitimate use (compliance with law) |
| Demo requests and sales follow-up | Consent (the checkbox on the form) and legitimate interests | Consent |
| Marketing emails | Consent | Consent |
| Non-essential cookies and analytics | Consent; in the notice countries listed in section 18, legitimate interests with an opt-out | Consent |
| Privacy requests | Legal obligation | Legal obligation |
Where we rely on legitimate interests, we have balanced them against your rights. You can ask the DPO for that assessment.
12. International data transfers
We are based in Singapore, and our application, database and SBOM storage run in Singapore. Some providers operate in other countries: email is sent from Japan, and payment, error monitoring and sign-in providers operate in the United States and elsewhere. Wherever data is processed it is encrypted in transit and at rest.
- From the EEA, UK and Switzerland: we rely on adequacy decisions or the EU Standard Contractual Clauses with the UK Addendum and Swiss adaptations, as set out in DPA Annex IV.
- From Singapore: we ensure recipients provide a standard of protection comparable to the PDPA, through contract and the Personal Data Protection Regulations 2021.
- From India: we do not transfer personal data to any country the Central Government restricts under section 16 of the DPDP Act.
Enterprise customers who need a different processing region can agree one in an Order.
13. Data retention
| Data | Retention |
|---|---|
| Account data | Life of the account; erased or anonymised 14 days after a deletion request (grace period), subject to the exceptions below |
| SBOM and project data | Per your organisation’s retention setting (default 365 days) and until you delete it |
| Files dropped on the free SBOM audit | Not stored. Processed in memory and discarded when the response is sent |
| Audit log | At least 12 months; personal identifiers (IP, user agent, email) are scrubbed on erasure while the chain stays verifiable |
| Demo requests | 24 months from submission, then deleted automatically; sooner if you ask |
| Billing records | As required by tax and accounting law (typically 5-7 years) |
| Privacy request records | 3 years after closure, as evidence of compliance |
| Consent records | For the life of the consent plus 3 years |
14. Your privacy rights
Do it yourself in a few clicks
| You want to | Where |
|---|---|
| Download a copy of your personal data | Settings → Privacy → Download my data (machine-readable JSON) |
| Delete your account | Settings → Privacy → Delete account (14-day grace period, cancellable by email) |
| Sign out other devices or revoke a token | Settings → Security and Settings → API tokens |
| Change how long SBOM data is kept | Set by your plan; email sia@sbombox.com to agree a shorter or custom period |
| Change cookie choices | Cookie preferences in the site footer |
| Stop marketing email | The unsubscribe link in any marketing email |
| Anything else, or you have no account | The privacy request form or dpo@sbombox.com |
We verify your email before acting on a request and respond within 30 days of verification. Where the law allows an extension for a complex request, we tell you before the deadline. Authorised agents can act for you with signed authorisation. Requests are free unless manifestly unfounded or excessive.
EEA, UK and Switzerland (GDPR, UK GDPR, FADP)
- Be informed about how we use your data (this policy).
- Access your data and receive a copy.
- Rectify inaccurate or incomplete data.
- Erase your data where there is no reason to keep it.
- Restrict processing while a dispute is resolved.
- Data portability, in a machine-readable format.
- Object to processing based on legitimate interests, and to direct marketing at any time.
- Not be subject to decisions based solely on automated processing that significantly affect you (see section 15).
- Withdraw consent at any time, without affecting earlier processing.
- Complain to a supervisory authority (see section 22).
India (DPDP Act 2023)
- Obtain a summary of your personal data and how it is processed, and the identities of others it was shared with (section 11).
- Correct, complete, update or erase your data (section 12).
- Withdraw consent as easily as you gave it (section 6(4)).
- Grievance redressal through our DPO, and then the Data Protection Board of India (section 13).
- Nominate someone to exercise your rights in the event of death or incapacity (section 14).
Singapore (PDPA)
- Access your data and information about how it has been used or disclosed in the past year.
- Correct errors or omissions.
- Withdraw consent, with notice of the likely consequences.
- Complain to the Personal Data Protection Commission.
California (CCPA)
California residents can request to know, access, correct and delete personal information, and to opt out of sale or sharing. We do not sell or share personal information, and we do not collect sensitive personal information. We will not discriminate against you for exercising these rights.
If you are named in a customer’s SBOM
Package manifests sometimes contain an author’s or maintainer’s name or email, which then appears in an SBOM a customer uploads. That customer is the controller of its SBOMs and is your first point of contact. If you contact us instead, choose “I am named in SBOM or package metadata a customer uploaded” on the form. We will acknowledge your request within 5 business days, pass it to the relevant customer, and help where we can, including when the item has been published.
15. Automated scoring and human review
SBOMBox automatically scores SBOMs against published requirements (BSI TR-03183-2, CISA, NTIA and CRA readiness checks) and matches components against vulnerability sources. These scores describe software, not people, and we do not use them to make decisions about individuals. We do not use AI models to produce scores. Results are informational and do not replace your own security or legal review.
Every score links to the requirement-level results that produced it, so you can see why. If you believe a score or finding is wrong, email sia@sbombox.com with the project and SBOM identifier and a person will review it.
16. Account deletion
When you delete your account we deactivate it immediately, revoke your sessions and tokens, and email a cancellation link. After a 14-day grace period we anonymise your profile, remove sign-in methods, memberships and MFA data, delete demo requests made with your email, and scrub personal identifiers from audit entries. We keep records the law requires (such as billing) and minimal evidence that a deletion occurred. If you are the only owner of an organisation that has other members, transfer ownership first.
17. Security
We use encryption in transit and at rest, hashed and peppered tokens, encrypted MFA secrets, least-privilege access, role-based permissions, request throttling and a tamper-evident audit trail. See our Security page.
No system is perfectly secure. If a personal data breach occurs we will notify supervisory authorities and affected people as the law requires: under the GDPR within 72 hours where required, under the PDPA as required by Part 6A, and under the DPDP Act to the Data Protection Board and affected people as required by section 8(6). Customers are notified within 48 hours under the DPA.
To report a vulnerability, email dpo@sbombox.com or follow our vulnerability disclosure policy.
19. Marketing communications
We only send marketing email with your consent, or where the law allows us to contact business customers about similar services. Every marketing email has a one-click unsubscribe link, and we never make unsubscribing depend on signing in. Service and security notices (sign-in codes, vulnerability alerts, billing and policy changes) are part of the Services and continue while you have an account.
20. Children’s privacy
The Services are for professionals and are not directed at children under 16 (under 18 where the DPDP Act applies). We do not knowingly collect their personal data. If we learn that we have, we will delete it without undue delay.
21. Changes to this policy
We post updates here with a new version number and date. For material changes we notify account holders by email or in-product notice at least 30 days before they take effect. Consent records reference the policy version in force when you made your choice, and earlier versions are available on request.
| Version | Date | What changed |
|---|---|---|
| 2.1 | 12 November 2026 | Added what the CLI, installer, CI integrations and free audit send; public pages and shared reports; a self-serve rights table; human review of scores; marketing; one contact address |
| 2.0 | 11 November 2026 | Rewritten for SBOMBox: roles, retention, DPDP Act and FADP coverage, account deletion |
22. Contact
Everything except privacy rights
sia@sbombox.com for support, sales, legal notices and general privacy questions. One inbox, read by a person.
Security reports
dpo@sbombox.com. See our vulnerability disclosure policy and security.txt.
Data Protection Officer
dpo@sbombox.com. Use the subject line “Privacy Enquiry”, “DSAR”, “Grievance” or “Score review” so your message reaches the right queue. The DPO is our grievance officer under the DPDP Act.
Guni Innovations Pte. Ltd. (UEN 202302437E), 68 Circular Road #02-01, 049422, Singapore.
Privacy requests
Use the privacy request form. We respond within 30 days of verifying your email, extendable for complex requests where the law allows.
Supervisory authorities
We would like the chance to resolve a concern first, but you can contact your authority at any time:
- Singapore: Personal Data Protection Commission, our lead authority.
- EEA: your national data protection authority (list on the EDPB website).
- UK: the Information Commissioner’s Office.
- Switzerland: the Federal Data Protection and Information Commissioner.
- India: the Data Protection Board of India.
- California: the California Privacy Protection Agency.
Privacy · Terms · DPA · Subprocessors · Privacy requests · Security