Privacy Policy
Privacy should not require blind trust.
Clawdbase exists to improve trust on the internet - not to exploit user data. Verification infrastructure should minimize unnecessary data exposure while making trust signals transparent, portable, and verifiable.
Registry Privacy Principles
Who we are
Clawdbase is operated by inVerus LLC.
This page explains what information we collect, how we use it, what becomes public, how Trust and Confidence signals operate, and how data is processed.
Clawdbase.ai is a product of inVerus LLC. Trust and Confidence signals are powered by the inVerus API.
This policy is provided for transparency and does not limit rights granted under applicable privacy laws.
Operator: inVerus LLC, a Delaware limited liability company.
What we collect
Only what the trust layer needs.
We may collect public ecosystem data, verification signals, platform usage data, and communication data.
1. Public Ecosystem Data
We may index public information related to agents, repositories, creators, organizations, skills, package registries, and open ecosystem trust signals.
2. Verification Signals
When users voluntarily connect providers, we may process GitHub associations, repository ownership proofs, connected accounts, domain signals, and related metadata.
3. Platform Usage Data
We may collect limited technical information such as browser type, device type, referral sources, page interactions, session metadata, and diagnostic logs.
4. Communication Data
If you contact us, we may retain email correspondence, support inquiries, verification requests, bug reports, or related communications.
This information is processed to support verification, origin analysis, Trust and Confidence scoring, provenance, registry integrity, inVerus API infrastructure, and discovery functionality.
Legal bases
Why we process data.
Legitimate interests
Maintaining trust infrastructure, preventing abuse, improving verification systems, protecting registry integrity, and supporting ecosystem security.
User consent
Where users voluntarily connect accounts, submit verification signals, or take actions that require consent.
Contractual necessity
Where processing is needed to provide requested services, account functionality, verification, or registry participation.
Legal obligations
Where processing is needed to comply with applicable law, lawful requests, or security obligations.
Public vs private
Public trust signals. Protected private credentials.
Public Information
Certain information may become publicly visible when intentionally associated with public registry participation or verification.
- Public creator profiles
- Public Trust and Confidence scores powered by the inVerus API
- Public skills, agents, repository associations, and verification signals
Private Information
Private credentials and non-public verification artifacts are not publicly exposed without permission.
- Private repository access
- Authentication tokens
- Internal verification records
- Confidential submissions or account data
Scores and profiling
Trust signals are not guarantees.
Clawdbase displays probabilistic Trust and Confidence signals powered by the inVerus API and derived from available ecosystem evidence.
Trust and Confidence scores are informational, evolve over time, and depend on available verification and ecosystem signals. They support verification, provenance, origin analysis, and ecosystem trust visibility.
Trust and Confidence scores are not guarantees, certifications, endorsements, or security audits. Clawdbase and the inVerus API provide informational infrastructure signals and do not make solely automated legal or similarly significant decisions about individuals.
Users remain responsible for their own execution and trust decisions.
Public indexing
The registry indexes public ecosystem signals.
Clawdbase may process publicly accessible ecosystem information in order to maintain registry integrity, support verification, improve Trust and Confidence scoring, and reduce impersonation risk.
If you believe publicly indexed information should be reviewed or removed, contact:
ContactCookies and analytics
Operational telemetry, not hidden surveillance.
Clawdbase may use cookies, local storage, and related technologies to maintain sessions, improve functionality, analyze usage, and secure platform operations.
These technologies may include authentication cookies, infrastructure monitoring, analytics providers, and performance tooling. Users may modify browser settings to restrict cookies, though some functionality may be affected.
International transfers
Infrastructure may operate in the United States.
Clawdbase infrastructure and data processing systems may operate in the United States and other jurisdictions.
By using Clawdbase, users acknowledge that information may be processed and stored outside their country of residence, including in the United States. Where required, Clawdbase implements reasonable safeguards intended to support lawful international data transfers.
What we do not do
Trust infrastructure should not exploit users.
Clawdbase does not:
Your rights
Control requests should be simple.
Depending on your jurisdiction, you may have rights relating to access, correction, deletion, portability, restriction, objection, or withdrawal of consent.
We may require reasonable verification before processing certain requests.
Residents of certain U.S. states, including California, may have additional privacy rights under applicable law.
Clawdbase does not sell personal information as traditionally defined under California privacy law.
Security
No internet system can promise absolute safety.
Clawdbase uses reasonable technical and organizational safeguards designed to protect registry infrastructure, verification systems, connected accounts, and platform integrity.
However, no internet-based system can guarantee absolute security. Users should maintain strong authentication practices, secure connected accounts, and exercise caution when interacting with autonomous systems.
Third parties and retention
External systems and retention periods vary.
Third-party services
Clawdbase may integrate with GitHub, package registries, cloud infrastructure providers, analytics providers, and related ecosystem services. Their own terms and privacy policies may also apply.
Data retention
Clawdbase retains information only as long as reasonably necessary to operate services, maintain registry integrity, support verification systems, comply with legal obligations, and improve ecosystem trust infrastructure, or until deletion is requested where applicable.
Children and updates
This policy may evolve.
Children's Privacy
Clawdbase is not intended for use by children under the age of 13. We do not knowingly collect personal information from children. Accounts, API access, commercial use, and organization-level features are intended only for users who are at least 18 years old or otherwise legally able to enter into binding terms.
Policy Updates
This Privacy Policy may evolve as platform capabilities, registry infrastructure, verification systems, and legal requirements change. Updated versions will be published on this page with a revised effective date.
Final principle
Verification should precede execution.
Trust infrastructure reduces uncertainty. It does not eliminate risk.
Clawdbase.ai is a product of inVerus LLC, a Delaware limited liability company.