Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Store keys separately by project, permission level and environment.
- Confirm whether request logs are kept, for how long and who can view them before use.
- Customer data, production code and payment information should not enter untrusted relay environments.
Step 1: Separate keys and permissions
Do not use one key for every project. Test, production, personal and team tools should have separate keys, permissions and quotas.
Do not put keys in public repositories, frontend code, screenshots, chat records or shared documents. Give colleagues access through a secure configuration system or dashboard permissions when possible.
Step 2: Check logging and retention
Before using an AI relay, determine whether it stores request content, response content, errors and user identifiers. Also check retention periods, who can view logs and whether deletion is supported.
If the relay does not explain its logging policy clearly, do not send customer records, internal code, financial information, account passwords or real proxy credentials.
Step 3: Use a fixed access environment and retain records
Use a fixed proxy exit and workstation for dashboard sign-in, key management and billing review, instead of letting different members enter the management dashboard casually from different environments.
For a stable proxy environment, visit the PuppyIP website. After purchase, follow the PuppyIP tutorials to check the setup.
Frequently Asked Questions
Can the relay’s administrators see my requests?
It depends on the implementation and logging policy. Before use, confirm whether request content, response content and error details are logged.
Can a team share one key?
Long-term sharing is not recommended. Separate keys by project and member so limits, auditing and revoking access are easier.