Acceptable Use Policy
What you may and may not do with the product and the data in it.
- Version
- 1.0
- Effective
Draft — pending legal review
This document is published in draft while it is reviewed by counsel. It is not yet binding and may change before the Launch Program opens. Questions: support@inspic.io.
This policy forms part of the Terms of Service. It applies to everyone using Inspicio, including anyone you invite into your workspace and anything you build against our API.
The short version: use it to run your own Amazon business. Do not use it to build a competing data product, and do not point it at things that are not yours.
1. What you may do with the data
- Use it to make decisions about your own business — sourcing, pricing, listing, advertising, stock.
- Export it and share it inside your own organisation.
- Show it to your accountant, your investor or your agency, as part of advising you.
- Build internal tooling against our API for your own workspace.
2. What you may not do with the data
- Resell, sublicense, publish or redistribute it, in bulk or in substantial part.
- Use it to build, train or improve a product that competes with ours.
- Present it as your own data product to third parties, whether free or paid.
- Systematically extract the database — by scraping the dashboard, by looping the API beyond your rate limit, or by any other means — in order to reconstruct it elsewhere.
An agency running research on behalf of named clients is fine. An agency reselling a data feed derived from our output is not. If you are not sure which side of the line your use sits on, ask us first — we would rather answer than enforce.
3. What you may not do to the service
- Attempt to access another workspace's data, or any account that is not yours.
- Probe, scan or test the security of the service without our written permission. If you find a vulnerability, report it — see section 6.
- Circumvent rate limits, authentication, plan gating or usage accounting.
- Use the service as a proxy to scrape Amazon or any other site on your behalf.
- Reverse engineer, decompile or attempt to derive the source of the software or the models behind it.
- Interfere with the service's availability for anyone else, including by deliberately expensive or automated request patterns.
- Share an account or an API key outside your organisation.
4. What you may not do with the content
- Anything unlawful under Egyptian law or the law that applies to you.
- Infringe anyone's intellectual property, including by using an AI-generated listing title that copies a competitor's protected content.
- Upload malware, or content designed to harm the service or its users.
- Submit verification evidence that is forged, altered or belongs to someone else.
- Use the product to harass, defame, or run a coordinated campaign against a competitor seller.
5. API use
- Stay within your plan's published rate limits. If you need more, ask rather than retrying harder.
- Identify your integration honestly in the user agent.
- Cache responses where you can, rather than re-requesting data that has not changed.
- Keep API keys out of client-side code, public repositories and shared documents. A key found in public is revoked without notice.
6. Reporting a security problem
Write to support@inspic.io with enough detail to reproduce it. We will acknowledge within two business days. We will not pursue you for a good-faith report made without accessing other people's data, destroying anything, or degrading the service — please give us a reasonable window to fix the issue before publishing.
7. Enforcement
Depending on what has happened and how deliberate it looks, we may get in touch, rate-limit the account, revoke an API key, suspend the workspace, or terminate it. For anything that threatens other users or the service itself we act first and explain afterwards. Where the breach is a mistake and the damage is nil, expect an email rather than a suspension.