Acceptable use policy
This policy protects RRCC, participating businesses, and their customers during beta. It is a draft-only public surface and remains subject to legal review.
Use RRCC to help the owner or operator decide what to do next before a lead goes cold. Do not use it to bypass consent, safety, approval, or human-review boundaries.
Allowed use
- Review missed-lead context and prioritize owner/operator follow-up.
- Record manual actions, notes, and outcomes when the workflow is enabled for a beta account.
- Use draft suggestions as human-reviewed context, not as instructions that execute themselves.
- Contact RRCC about support, privacy, security, or legal-review questions.
Prohibited use
- Uploading passwords, API keys, tokens, raw provider payloads, or unnecessary sensitive data.
- Trying to access another business account, customer record, provider account, or internal route.
- Using RRCC to prepare deceptive, unlawful, harassing, abusive, or unwanted customer messages.
- Attempting to bypass outbound locks, approval gates, rate limits, spend controls, or audit logs.
- Testing security controls, scraping, or disrupting RRCC without written permission.
Beta enforcement
- RRCC may limit, suspend, or remove beta access for unsafe or prohibited use.
- Future phase capabilities may require additional review, consent evidence, or owner approval.
- AI assistance remains draft-only and not autopilot.
- Outbound messaging remains locked unless separately approved.
Acceptable use questions should go to support@mail.getrrcc.com.
Back to RRCC