How Analese handles information.

This policy applies to the Analese website, dashboard, AI receptionist, connected communication features, and related workflows (the “Service”). Analese is the product described on this page.

For an access, correction, export, deletion, or privacy question, use the contact form. The Terms of Service and Security pages provide the related service and operational context.

Depending on the features and connections an owner enables, the Service can receive:

• Account and session information used to sign in and maintain a workspace.
• Business profile information, hours, services, greetings, configuration settings, plan state, and connection state.
• Caller and customer names, phone numbers, email addresses, notes, tags, and communication preferences.
• Call events, recording or audio references, voicemail audio and transcripts, transcript snippets, AI summaries, and appointment or intake details. Recording and retention settings are owner intent; provider lifecycle evidence is shown only when observed.
• CRM records, waitlist entries and offers, review-request details, and chat-lead submissions.
• Integration credentials or scoped access tokens needed for a connection the owner chooses to use.

The Service uses this information to answer and triage calls, identify intent, book appointments, send reminders and follow-ups, capture leads, and operate waitlist and review-request workflows. It also populates the dashboard and audit history so an owner can review what happened.

Information can also support calendar, CRM, and email synchronization; customer support and security operations; billing and plan operation where applicable; and product analytics. The exact workflow depends on the plan, settings, and connections an owner enables.

Call, chat, and voicemail text, together with related conversation context, can be sent through the platform-managed AI proxy to generate replies, summaries, classifications, or extracted details. The proxy is part of the platform path used by the product; this policy does not name an unverified model vendor or make a claim about model training or retention.

Owners remain responsible for reviewing the receptionist configuration, greetings, disclosures, and booking rules that operate on their behalf.

Analese's SMS consent invitation is: “Thanks for contacting Analese. You're messaging our AI assistant. By replying, you consent to receive AI-generated responses and to have your messages used for customer service and recordkeeping. Message and data rates may apply. Message frequency may vary. Reply STOP to opt out.”

In this message, “replying” means replying with one clear keyword from the opt-in list: YES, START, SUBSCRIBE, UNSTOP, Y, OK. That keyword reply is express written consent to receive further SMS. An arbitrary reply or a web form checkbox does not grant consent. Message frequency may vary, and message and data rates may apply. The operational details are also described on the SMS program page and the Terms .

The opt-out keywords are STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT, OPTOUT, REVOKE. They are handled before every other intent, including when a message contains multiple control words. The exact opt-out response is: “You have successfully been unsubscribed. You will not receive any more messages from this number. Reply START to resubscribe.” The HELP and INFO keywords are HELP, INFO; the exact help response is: “Reply STOP to unsubscribe. Msg&Data Rates May Apply.” HELP and INFO remain available after an opt-out. START is the keyword-only resubscription path; free-form “resubscribe” is not accepted.

The Service keeps the current status and keyword audit for each user and phone number, and gates missed-call text-back, appointment confirmations and reminders, waitlist offers, review requests, and receptionist replies with that same status. Future non-essential SMS is blocked without affirmative keyword consent and after an opt-out. Owner-only voicemail notification emails are a separate internal notification path and are not a caller SMS opt-in disclosure.

STOP may be sent at any time. Read the SMS program page for the separate Sample #6 flow summary and the complete control-message display.

If an owner connects a phone or SMS line, calendar, CRM, or email account, the Service exchanges the information needed to provide that selected connection—for example, availability for booking, a lead or appointment record, a daily summary, or a configured follow-up. Access is intended to stay within the scope granted by the connection.

Connections can be disconnected from the available product controls. This policy does not promise a particular processor contract, deletion timetable, or vendor list beyond what the app and the Security overview currently describe.

The Service uses authentication and session cookies to keep accounts signed in. Where enabled, the browser may also receive an optional Polsia analytics visitor key and send a corresponding analytics beacon. The site includes a locally served Meta Pixel script and a no-script page-view pixel path.

Cookies and similar technologies may be used where these features are enabled. This policy does not claim that a consent banner exists or attempt to infer a complete third-party cookie inventory from those paths.

Account and dashboard access is protected by the installed authentication and session controls. Workspace data is scoped to the owner and authorized staff access; administrative views are separated from ordinary customer views, and connected services use the scope of the credential or token granted by the owner.

The operational safeguards described on the Security page include HTTPS/TLS for connections and platform-managed storage protections, along with the product’s configured call, transcript, and vertical guardrails. These statements describe shipped controls, not an independent security or regulatory certification.

The repository does not define one universal fixed retention period for every record. Conversation history, transcripts, and booking information can be downloaded through the dashboard where the relevant feature is available, and the product has a daily export path. Cancellation is available from the dashboard, and owners can use the available disconnect, delete, and export controls for the relevant connection or record.

Audio URLs do not all have the same lifecycle: voicemail links backed by the original recording service can expire, while other stored audio references may follow the underlying account or connection. Append-only audit records and owner-managed exports can follow different lifecycles from ordinary dashboard records. The owner still needs to approve the retention schedule, deletion service level, and jurisdiction-specific rights before this policy is final.

Use the contact path to request access, correction, export, deletion, or answers about privacy. The final policy should add the rights, identity-verification, and response details required for the jurisdictions in scope.

The canonical policy route is /privacy. If the Service or its data practices change, the owner should update this page and the effective-date and notice language. Questions and requests should go through the contact form.

This policy is not a promise of a fixed retention period, a processor commitment, or independently certified TCPA or other compliance.