01
Use Ajani for legitimate, authorized work
You may use Ajani only for lawful business purposes and only with data, accounts, systems, recipients, and instructions you are authorized to use. You must not use Ajani to violate law, another person's rights, a platform rule that applies to you, or a contract that governs a connected service.
Do not use Ajani to facilitate fraud, deception, harassment, stalking, exploitation, discrimination, violence, or other material harm; impersonate a person or organization; conceal the source or commercial nature of a message; or create false evidence of a live system, client result, endorsement, or human action.
02
Security and service integrity
Do not introduce malware, probe or bypass security, scrape or access accounts without authorization, interfere with service operation, overwhelm an endpoint, reverse engineer protected components except where law permits, expose credentials, or help another person do any of those things.
Promptly report suspected unauthorized access, exposed credentials, abusive automation, or a security weakness to hello@ajaniautomation.com. Do not publicly disclose a vulnerability before Ajani has a reasonable opportunity to investigate and reduce harm.
03
Calls, texts, emails, and direct messages
Before a workflow contacts someone, the client must have the legal right and any required consent to contact that person through that channel for that purpose. Recipient lists must be current and lawfully obtained. Sender identity, subject lines, caller information, message content, timing, and frequency must be accurate and not misleading.
Clients must maintain and apply do-not-contact, suppression, and revocation records; include required identification and opt-out instructions; promptly honor STOP, unsubscribe, and other valid revocations; and comply with applicable calling hours, frequency limits, telemarketing, do-not-call, email, carrier, and platform rules.
Ajani may require consent records or campaign details before enabling a route. Approval by Ajani does not replace the client's legal review, and neither party may contract away duties that law places on its own conduct.
04
Voice, calls, and recording consent
The public recorder is intended for your own narration. Do not record or upload another speaker, a phone call, a meeting, or confidential audio unless you have provided all required notice and obtained all required permission in every applicable jurisdiction.
A client system that records, transcribes, analyzes, or generates voice requires a project-specific review of consent, disclosure, retention, access, and vendor obligations before launch. Do not use Ajani to identify a person from their voice or create a biometric voiceprint unless Ajani has expressly approved a separate written process.
05
Human review and high-impact decisions
AI or automated output may not be the sole basis for a decision that determines a person's eligibility, access, rights, or treatment in healthcare, employment, housing, education, credit, lending, insurance, legal services, government benefits, or another similarly significant area.
Clients must designate accountable people, verify material output, monitor live workflows, provide an appropriate appeal or human-contact path, and maintain a fallback for failures. Ajani systems are not emergency services and must not be the sole route for emergency, clinical, safety-critical, or legally required communication.
06
Sensitive and regulated information
Do not place protected health information, full payment-card numbers, government identifiers, biometric templates, precise credentials, children's data, or other regulated or highly sensitive information into the public intake or a general-purpose AI route.
A project may process regulated information only after Ajani confirms in writing that the use case, provider chain, security controls, data-processing terms, and any required industry addendum are approved. A warning or client instruction cannot make an unapproved provider eligible for regulated data.
07
Controls clients must maintain
- Accurate business rules, lawful source data, and current recipient permissions.
- Named owners for approvals, exceptions, escalations, and human handoffs.
- Least-privilege credentials and prompt removal of former team members.
- Testing before launch, ongoing monitoring, and documented fallback procedures.
- Records supporting consent, opt-outs, claims, client instructions, and required notices.
- Prompt reporting of errors, complaints, unauthorized use, or changed legal requirements.
08
Review, restriction, and reporting
Ajani may investigate suspected violations; request information or evidence; pause a message, integration, or workflow; restrict access; or terminate use when reasonably necessary to protect people, clients, providers, platforms, or Ajani. Ajani will ordinarily give notice and an opportunity to correct a non-urgent issue when appropriate.
Report suspected abuse to hello@ajaniautomation.com. Include the affected workflow or account, what occurred, and any time-sensitive risk. Ajani may preserve relevant records while investigating or meeting legal duties.