Acceptable Use Policy
The rules that protect InterfaceKit, its resources, and the people who use them.
- Effective
- July 27, 2026
- Last updated
- July 27, 2026
1. Follow the law and respect rights
You may not use InterfaceKit to violate law; infringe intellectual property, privacy, publicity, or other rights; harass, threaten, defraud, or deceive people; distribute malware; facilitate unauthorized access; or create or distribute unlawful material.
You may not use InterfaceKit in a way that subjects us or another person to sanctions, export-control violations, or other unlawful restrictions.
2. Protect systems and availability
- Do not probe, scan, or test a system or vulnerability without our prior written permission.
- Do not disrupt, overload, degrade, or interfere with the service or another user.
- Do not bypass authentication, technical restrictions, rate limits, plan limits, or access controls.
- Do not introduce malware, destructive code, or requests designed to exploit a parser, agent, browser, API, or worker.
- Do not use deceptive traffic, forged headers, or other methods to conceal unauthorized activity.
3. Protect accounts and credentials
- Do not obtain, test, or use another person’s account, token, sign-in code, or agent key without authorization.
- Do not expose credentials in public repositories, client-side code available to untrusted users, logs, datasets, screenshots, shared prompts, or public support messages.
- Do not sell, rent, sublicense, or share an account or agent key with unrelated third parties.
- Notify humans@interfacekit.io promptly if a credential may be compromised.
4. Use documented access methods
Automated access must use documented routes, valid credentials, and reasonable request patterns. Do not scrape, crawl, mirror, or bulk-copy the service through undocumented methods, and do not continue automated requests that produce repeated errors or unexpected load.
You are responsible for every application and AI agent that uses your credentials. Keep credentials in a trusted environment, limit access, validate outputs, and rotate a key when exposure is suspected.
5. Do not repackage InterfaceKit
You may use licensed resources to build your own products under the Terms of Service. You may not mirror, resell, sublicense, publish, or redistribute InterfaceKit resources as a standalone design system, code library, dataset, training corpus, template catalog, reference service, agent endpoint, or product that substitutes for InterfaceKit.
You may not use automated extraction to recreate a substantial part of the catalog or to train, evaluate, or supply a competing library or retrieval service unless we give written permission.
6. Third-party content and brands
Do not present InterfaceKit references as official assets of a third-party product or imply sponsorship, endorsement, or affiliation that does not exist. You are responsible for replacing third-party names, marks, content, and distinctive product details when your intended use requires it.
7. Enforcement
We may investigate suspected violations and may throttle, block, rotate credentials, remove access, suspend an account, or preserve relevant records. We consider the nature, severity, duration, repetition, impact, and efforts to correct the issue.
Where practical and appropriate, we will explain the action and provide a way to appeal. We may act without advance notice when needed to address an urgent security, legal, or safety risk.
To report abuse, disclose a security concern, appeal an action, or ask whether a use is permitted, email humans@interfacekit.io.
Questions about this document?
humans@interfacekit.io