Privacy policy
Clear rules for business and caller data.
This policy explains what AlloBoss AI handles when a service business uses our AI dispatcher, CRM, analytics, and beta application form.
Effective August 10, 2026 · Applies to the AlloBoss AI founding beta1. Scope and roles
This policy applies to the AlloBoss AI website, founding beta, AI call handling, CRM, dispatch, analytics, and related support.
For account and beta-application data, AlloBoss AI decides why and how the data is used. For caller, customer, job, recording, and transcript data submitted through a business customer’s phone line, the business customer generally decides the purpose of processing and AlloBoss AI processes that data to provide the service.
Each business must provide legally required notices, configure the service lawfully, and have an appropriate basis for collecting and recording caller information.
2. Information we collect
- Account and application data: owner name, business name, email, phone, location, trade, preferred plan, language, call volume, and messages submitted to us.
- Caller and job data: caller name and number, service address, requested service, timing, notes, appointment details, and technician assignment.
- Call content: audio recordings, transcripts, summaries, consent events, call outcome, duration, and transfer or callback status when recording is enabled.
- Business operations: orders, calendar events, technician status, recorded revenue, costs, payouts, and performance metrics entered by the business.
- Technical data: device, browser, IP address, timestamps, diagnostics, security events, and interaction data needed to operate and protect the service.
- Billing data: plan, usage, invoices, and payment status. Payment-card details should be handled by the payment provider rather than stored directly by AlloBoss AI.
We do not intentionally request Social Security numbers, bank credentials, medical records, government IDs, or payment-card numbers during ordinary service calls. Business customers must not configure the dispatcher to collect them unless a separate written agreement and appropriate safeguards are in place.
3. How we use information
We use information to answer and route calls, create customers and jobs, schedule service, provide callbacks and handoffs, generate transcripts and summaries, show business analytics, calculate usage, support users, prevent abuse, troubleshoot, secure the service, comply with law, and improve call flows.
We do not sell personal information. We do not use caller recordings or transcripts for targeted advertising. We will not use customer call content to train a shared AI model unless the business customer has expressly agreed to that use in writing.
4. Calls, recordings, and transcripts
The AI dispatcher should identify itself and provide the configured recording notice at the beginning of a call. In jurisdictions requiring every party’s consent, recording and persistent transcription must remain off until affirmative consent is received.
If a caller declines recording, the configured flow should disable recording and transcription, transfer the caller to a person, offer a callback, or provide another non-recorded channel. Consent and recording rules vary by location; see our Call Recording Standard.
6. Retention and deletion
We retain information only for as long as needed to provide the service, maintain business records, resolve disputes, prevent fraud, and meet legal obligations. Business customers control operational retention settings where available and may request deletion or export of their data.
Deleting a record from the active product may not immediately remove encrypted backups or records that must be retained by law. Those copies remain protected and are removed through the applicable backup lifecycle.
7. Security
We use safeguards designed for the sensitivity of call and customer data, including secure transport, access restrictions, separation of business accounts, logging, data minimization, vendor review, and incident-response procedures. No system is perfectly secure, and we do not guarantee that unauthorized access can never occur.
The founding beta does not claim SOC 2, HIPAA, PCI DSS, or ISO certification unless a current certification is explicitly listed in the Trust Center.
8. Your choices and rights
Depending on where you live, you may have rights to access, correct, delete, or obtain a copy of personal information, or to appeal a denied privacy request. We may need to verify identity and authority before completing a request.
Callers should first contact the service business they called because that business controls the customer relationship. The business may forward the request to AlloBoss AI when our assistance is needed. The service is not directed to children under 13.
9. Contact and policy changes
For a privacy request during the founding beta, use the application form on the main site and begin the final message with “Privacy Request.” Do not include sensitive documents or account credentials in the form.
We may update this policy as the product, vendors, or law changes. Material changes will be shown by a new effective date and, when appropriate, an in-product notice.