CIRCUITPATH / RESPONSIBLE USE
Acceptable-use policy
Purpose: CircuitPath is intended for lawful, permission-based workflows. This policy applies to the website, account and reservation flows, and any future proxy connection. The network is not live today, and no clause here authorizes activity that is unlawful or outside a target service's permission.
1. Good-faith use
Examples of generally appropriate direction include regional quality assurance, localization testing, ad verification, market research, public-data workflows, uptime or availability checks, and other testing or research for which you have the necessary authorization. You are responsible for checking the law, contract, robots or access rules, privacy requirements, and rate limits that apply to your workflow.
A residential IP address does not make a request anonymous, authorized, or compliant. Do not describe CircuitPath as a way to evade accountability, identity checks, security controls, or a website's access decision.
2. Prohibited activity
You must not use CircuitPath, attempt to use it, or allow anyone else to use your account for:
- credential stuffing, password spraying, account takeover, phishing, impersonation, or unauthorized access;
- malware, ransomware, botnet control, spam, unsolicited bulk messaging, denial-of-service, flooding, or service disruption;
- fraud, payment abuse, chargeback abuse, ad or click fraud, fake engagement, ticket or inventory abuse, or manipulation of rankings or metrics;
- bypassing authentication, paywalls, access controls, geographic restrictions, bans, rate limits, or security measures without express permission;
- collecting, inferring, deanonymizing, selling, or exposing non-public personal data without a lawful basis and authorization;
- scraping or automated access that violates applicable law, a contract, a target service's terms, or an explicit no-automation instruction;
- exploiting minors, trafficking, harassment, threats, discrimination, or other abuse of people or services;
- scanning, probing, attacking, or attempting to compromise CircuitPath, its hosting, Google/Firebase, Wise, residential providers, or another network;
- concealing the origin of unlawful conduct or using multiple accounts to evade suspension; or
- any activity that creates an unreasonable risk to residential participants, third parties, providers, or the security or availability of a system.
3. Customer responsibilities
- Obtain and retain evidence of authorization for the workflow, target, data, and volume you use.
- Use only the minimum request rate, data, retention, and access scope needed for the authorized purpose.
- Protect credentials, do not share them publicly, and notify CircuitPath promptly if they may be compromised.
- Respect opt-outs, deletion requests, privacy rights, copyright, confidentiality, and applicable export or sanctions rules.
- Stop the workflow if CircuitPath, the target service, a provider, or a rights-holder asks you to stop.
- Ensure your employees, contractors, integrations, and downstream users follow this policy.
4. Monitoring and enforcement
CircuitPath may use account, reservation, authentication, usage, security, and provider information to detect abuse and protect the service. We may rate-limit, block requests, suspend or terminate accounts, revoke future credentials, cancel or review reservations, preserve evidence, notify affected providers, or refer suspected unlawful activity to appropriate authorities. We will seek to act proportionately, but emergency suspension may happen without advance notice.
A suspension is not a finding that a person is legally liable. Where operationally and legally appropriate, CircuitPath may provide a reason and consider an appeal with evidence of authorization and remediation. Do not create a new account to evade enforcement.
5. Security and abuse reports
Do not include passwords, API keys, payment credentials, or unnecessary personal data in a report. Send abuse and security reports to auralisstudiossupport@gmail.com. The operating entity, response process, and any dedicated security contact must still be documented before live proxy access is enabled.
6. Residential sourcing and future launch
No residential-network provider is connected in the current release. Before any provider is connected, CircuitPath must complete sourcing and informed-consent review, revocation and opt-out handling, privacy review, credential controls, usage attribution, abuse operations, and India-egress verification. This policy does not by itself prove that any future provider satisfies those requirements.
7. Policy changes
We may update this policy as the service, providers, threats, or law change. The version and date at the top will identify the current text. Material changes will be communicated where appropriate, and a future service may impose stricter controls for a particular network or customer segment.
8. Related pages and release gate
See the Privacy notice, Terms of service, and Pre-launch reservation terms. A live proxy launch requires the final legal entity, contacts, provider review, monitoring, response process, and customer terms to be approved and published first.