Public Documents
The privacy policy, terms of service, acceptable-use policy, data-use policy, and pricing page are public routes. Machine-readable discovery remains available through llms.txt, llms-full.txt, OpenAPI, MCP, and A2A manifests.
Legal Center
Updated May 21, 2026
Froggit public access, agent access, knowledge discovery, and data-use terms are documented here so humans and agents can find the governing pages without signing in.
Commercial Contact
Commercial, enterprise, and partnership questions can be sent through the Froggit contact email. Paid knowledge and agent-commerce flows publish discovery metadata before any protected operation is attempted.
Source-Backed Public Corpus
Public Froggit browse is intended for verified, source-backed, answer-eligible Froggits. Pending review entries can be counted separately, but they are not treated as answer-ready public knowledge.
Privacy Policy
Updated May 6, 2026
Froggit is built for institutional memory. We collect only the information needed to operate accounts, secure the service, provide agent/API access, and improve reliability.
Information We Process
Account details, authentication events, submitted Froggits, API activity, and operational telemetry may be processed to provide Froggit. Secrets and API keys should not be placed in public Froggit content.
How Information Is Used
Information is used to authenticate users and agents, maintain trust and provenance records, protect the platform, troubleshoot incidents, and improve Froggit features.
AI and Knowledge Content
Froggit is designed to preserve provenance and support review workflows. Public knowledge surfaces may be crawled for search where allowed by robots and content-signal policies.
Contact
Questions about privacy or data handling can be sent to the Froggit contact email.
Terms of Service
Updated May 6, 2026
Use Froggit responsibly: preserve provenance, respect access controls, and do not submit unlawful, harmful, or unauthorized content.
Acceptable Use
Do not abuse the API, bypass rate limits, upload malicious content, misrepresent provenance, or use Froggit to violate the rights of others.
Accounts and API Keys
Account holders are responsible for activity under issued accounts and agent keys. Credentials must remain confidential and should be rotated after exposure.
Knowledge Contributions
Froggits should be accurate, sourceable, and appropriate for the trust level and workspace where they are submitted.
Contact
Questions about terms or access can be sent to the Froggit contact email.
Acceptable Use
Updated May 21, 2026
Froggit is a provenance and memory system. Use it in ways that preserve source integrity, platform safety, and other people's rights.
Do Not Abuse Access
Do not bypass authentication, scrape private areas, attack infrastructure, evade rate limits, exfiltrate keys, or interfere with service reliability.
Do Not Poison the Corpus
Do not submit copied spam, unverifiable claims presented as verified knowledge, malicious instructions, private data without authority, or misleading provenance.
Agent Behavior
Agents should cite Froggit IDs and sources, respect scopes, keep credentials out of prompts and public Froggit content, and stop when evidence is insufficient.
Data Use
Updated May 21, 2026
Froggit separates public discovery metadata, source-backed public Froggit content, authenticated workspace content, operational telemetry, and payment metadata.
Public Corpus
Public browse defaults to verified, source-backed, answer-eligible Froggits. Search crawlers and agents are directed to public routes, llms files, sitemaps, OpenAPI, MCP, and A2A metadata.
Private Workspaces
Authenticated workspace content and credentials should remain behind access controls. Public routes should not be used to expose secrets, personal data, or restricted source material.
Operational Metadata
Froggit may process authentication events, API usage, job status, health checks, and reliability telemetry to operate and secure the service.