Privacy Policy

This Privacy Policy describes how SentireSystems LLC, a Delaware limited liability company (“SentireSystems,” “Company,” “we,” “our,” or “us”), collects, uses, discloses, and retains personal information in connection with the SentireSystems AI-powered voice booking platform and related services (the “Platform”), as defined in the Master Service Agreement (“MSA”) between SentireSystems and each subscribing business client (“Client”). This Privacy Policy is incorporated into and forms part of the MSA. Capitalized terms not defined here have the meanings given in the MSA.

This Policy addresses two distinct categories of individuals: (1) Clients and their authorized business users who access the Platform through the white-label business dashboard (“Business Users”); and (2) the end users — callers and members of the public — whose calls are handled by the Platform on behalf of Clients (“End Users” or “Callers”). SentireSystems operates as a data processor with respect to End User personal information processed on behalf of Clients, and Clients operate as the data controller responsible for the lawfulness of such processing.

1.1 Information Collected from Business Users (Clients and Their Staff). When a Client registers for, accesses, or uses the Platform, SentireSystems may collect the following categories of information: (a) Account Registration Data: business name, contact name, email address, telephone number, billing address, and payment information (processed by our payment processor; SentireSystems does not store full payment card data). (b) Dashboard and Configuration Data: agent personality settings, business hours, service offerings, booking rules, voice profile identifiers (including ElevenLabs voice IDs configured per tenant), Twilio telephone number assignments, and Google Calendar OAuth tokens stored on a per-tenant basis. (c) Usage and Analytics Data: login activity, dashboard interaction logs, feature usage patterns, call volume and booking success metrics, system health data, and error events, collected through PostHog (product analytics) and Sentry (error and performance monitoring). (d) Communications: support requests, feedback, and other communications submitted to SentireSystems.

1.2 Information Collected from End Users (Callers). When an End User places an inbound call to a business using the Platform, SentireSystems collects and processes the following information on behalf of the applicable Client: (a) Caller Telephone Number, captured automatically via Twilio at call initiation and used for call routing, booking records, and, where applicable, outbound communications subject to Section 4 below. (b) Call Audio Recordings — the Platform records all inbound calls as a core feature, streamed in real time via Twilio Media Streams over WebSocket to the Platform's voice pipeline for transcription and processing. (c) Call Transcripts — real-time speech-to-text transcription of caller audio produced by Deepgram's Streaming API (with confidence scoring) and stored as part of the call log for each Client tenant. (d) Appointment and Booking Records — caller name, telephone number, requested service, selected provider, and scheduled appointment date and time. (e) Callback Tasks and Messages — where a call cannot be resolved, a callback task record is created containing the caller's name, telephone number, and the reason the call was unresolved. (f) Conversational Inputs and Outputs — the full content of the natural-language conversation between the caller and the AI voice agent, processed through OpenAI's GPT-4o API and retained as part of the call transcript. (g) Consent Records — where a Caller provides prior express written consent to receive outbound automated SMS messages or AI-generated voice calls, a record of that consent is stored in accordance with Section 5 below and the MSA.

1.2.1 End User Notice — Call Recording. All inbound calls handled by the Platform are recorded as a core feature. End Users who have questions about call recording, or who wish to object to the recording of their call in accordance with applicable federal or state law, should contact the applicable Client business directly. Client is solely responsible for providing all required pre-call disclosures informing callers that their call may be recorded and processed by an AI voice system, and for responding to any End User objections to recording under applicable law. SentireSystems does not provide End Users with a mechanism to opt out of call recording, as recording is integral to the Platform's operation and cannot be disabled on a per-caller basis.

1.3 Voice and Biometric Data. Where the Platform's ElevenLabs text-to-speech and voice synthesis integration is used to record, process, or clone human voice data, the resulting voice recordings and voiceprints may constitute biometric identifiers under applicable state law, including the Illinois Biometric Information Privacy Act (740 ILCS 14/1 et seq.) and comparable statutes in other jurisdictions. Client is solely responsible for compliance with any applicable biometric data laws, including obtaining required written releases from individuals whose voice or likeness is submitted as input, and for maintaining a publicly available retention and destruction policy where required by law. SentireSystems makes no representation that its data handling practices satisfy any specific biometric data statute.

1.4 Automatically Collected Technical Data. SentireSystems automatically collects certain technical information in connection with Platform operation, including IP addresses, browser and device identifiers, session durations, API call timing and latency metrics, and system error logs. This information is used for Platform performance monitoring, security, and improvement.

1.5 Data Not Permitted on the Platform. The Platform is not designed or configured to comply with the Health Insurance Portability and Accountability Act (“HIPAA”) or the Payment Card Industry Data Security Standard (“PCI DSS”). Clients must not submit, upload, or cause to be processed through the Platform any Protected Health Information as defined under the HIPAA Privacy Rule (45 C.F.R. § 160.103), or any payment card data regulated under PCI DSS. SentireSystems makes no representation that the Platform satisfies any HIPAA, PCI DSS, or equivalent regulatory requirement.

2.1 Platform Operation and Service Delivery. SentireSystems uses collected information to operate, maintain, and improve the Platform, including: routing and handling inbound calls; transcribing and processing caller audio; booking and confirming appointments via the Google Calendar API; generating AI-powered conversational responses via OpenAI's GPT-4o API; synthesizing AI voice responses via ElevenLabs' Streaming API; managing per-call session state via Redis (with automatic session cleanup upon call termination); storing call logs, transcripts, and appointment records in SentireSystems' multi-tenant Supabase PostgreSQL database (with Row-Level Security enforcing per-tenant data isolation); and displaying call logs, transcripts, analytics, and agent configuration data on the white-label business dashboard.

2.2 Communication and Account Management. SentireSystems uses Business User contact information to communicate with Clients regarding their accounts, subscription terms, service changes, billing, support, and legal notices.

2.3 Outbound Communications on Behalf of Clients. Where a Client has enabled outbound voice or SMS features of the Platform and the applicable consent and authorization requirements under the MSA (Section 5) and applicable law are satisfied, SentireSystems uses Caller telephone numbers and consent records to transmit AI-generated outbound communications on the Client's behalf, including appointment reminders, no-show notifications, follow-up callbacks, and, where authorized, promotional campaign messages. All such use is subject to the consent and compliance obligations set out in Section 4 of this Policy and the MSA.

2.4 Analytics and Platform Improvement. SentireSystems may use aggregated, de-identified, and anonymized data derived from Client Data — including call volume, booking success rates, average call duration, and system latency metrics — for platform analytics, product development, and service improvement purposes, provided that such data cannot reasonably be used to identify any Client or individual End User. SentireSystems uses PostHog for product analytics and Sentry for error tracking and performance monitoring in connection with these purposes. End Users who wish to request that their personal information not be included in analytics processing should direct such requests to the applicable Client business. Client is responsible for communicating any such requests to SentireSystems in writing as required by applicable law and Client policy.

2.5 Security and Fraud Prevention. SentireSystems uses technical and usage data to detect, investigate, and prevent unauthorized access, abuse, and other security incidents.

2.6 Legal Compliance and Enforcement. SentireSystems may use or disclose personal information to comply with applicable legal obligations, respond to lawful requests from regulatory authorities, and enforce the MSA and this Policy.

3.1 Third-Party Providers Integrated into the Platform. The Platform integrates the following third-party service providers (“Third-Party Providers”), each of which may process Client Data and End User personal information as part of their services. Third-Party Provider terms are subject to modification at any time without notice to SentireSystems or Client. SentireSystems makes no representation that any description of Third-Party Provider terms in this Policy is current or complete, and nothing in this Policy constitutes legal advice regarding the effect of any Third-Party Provider's terms on Client or End Users. Client is solely responsible for reviewing and monitoring the current terms of each Third-Party Provider before and during use of the Platform.

(a) Twilio, Inc.: inbound call handling, per-tenant telephone number routing, and bidirectional audio streaming via WebSocket. Twilio's terms of service are available at twilio.com/en-us/legal/tos.

(b) Deepgram, Inc.: real-time speech-to-text transcription of caller audio with confidence scoring. Deepgram's terms of service are available at deepgram.com/legal.

(c) OpenAI, LLC: conversational intelligence, intent extraction, slot filling, and response generation via the GPT-4o API. SentireSystems accesses OpenAI services through the OpenAI API as a business customer; such use is governed by OpenAI's customer agreements and Usage Policies, available at openai.com/policies/usage-policies. Client is solely responsible for reviewing OpenAI's current terms, including any data use, model training, opt-out, and liability provisions applicable to API customers; OpenAI's data controls and privacy portal are available at privacy.openai.com. End Users whose conversation data has been processed through OpenAI's API may submit deletion or access requests directly to OpenAI at privacy.openai.com or by email to dsar@openai.com.

(d) ElevenLabs, Inc.: text-to-speech voice synthesis via the ElevenLabs Streaming API, with per-tenant voice customization. Client's use of ElevenLabs services through the Platform is subject to ElevenLabs' Terms of Service, available at elevenlabs.io/terms-of-use, and where applicable, ElevenLabs' OEM Terms. ElevenLabs' AI voice models are owned exclusively by ElevenLabs; no right, title, or interest in any voice model is transferred to Client or any End User by virtue of this Policy or use of the Platform. By providing voice recordings or audio input through the Platform's ElevenLabs integration, Client grants ElevenLabs a broad license to that input and any resulting voice model for purposes that include research and development of AI models; the current scope of that license, and any available opt-out rights with respect to model training, are set out in ElevenLabs' current Terms, which Client is solely responsible for reviewing. ElevenLabs may require individual consent for collection of sensitive information, including voice data that may constitute biometric data under applicable law. Client is responsible for ensuring any required individual consents are obtained prior to submitting voice data through the Platform's ElevenLabs integration. End Users who wish to exercise rights of access, correction, or deletion with respect to voice data processed through ElevenLabs may direct requests to ElevenLabs at legal@elevenlabs.io.

(e) Google LLC: real-time calendar availability checking and appointment creation via the Google Calendar API (OAuth 2.0), with per-tenant OAuth tokens stored encrypted in SentireSystems' database. Google's terms of service are available at policies.google.com/terms.

(f) Supabase, Inc.: multi-tenant PostgreSQL database (with Row-Level Security for per-tenant data isolation), authentication, real-time dashboard subscriptions, and call recording storage. Supabase's terms are available at supabase.com/terms.

(g) Amazon Web Services, Inc. (“AWS”): cloud infrastructure and container orchestration (AWS ECS/Fargate), content delivery (CloudFront), and DNS management (Route 53). All API keys are stored in AWS Secrets Manager. AWS's terms are available at aws.amazon.com/legal.

(h) PostHog, Inc.: product analytics, call funnel tracking, and call outcome metrics. PostHog's terms are available at posthog.com/terms. (i) Sentry (Functional Software, Inc.): error tracking, performance monitoring, and system health alerting. Sentry's terms are available at sentry.io/terms. (j) Redis (Upstash or AWS ElastiCache): per-call conversational session state and turn history. Session data is automatically purged upon call termination.

SentireSystems will maintain a current list of Third-Party Providers that process Client Data and will provide reasonable advance notice to Clients before adding a new subprocessor, in accordance with Section 8.7 of the MSA. Client may raise a good-faith data protection objection to any proposed new subprocessor within ten (10) days of receiving such notice. The Parties will cooperate in good faith to resolve any such objection within thirty (30) days. If the objection cannot be resolved within that period, Client may terminate the affected services on written notice to SentireSystems.

3.2 Client-Controlled Disclosure. Client Data, including call logs, transcripts, appointment records, and callback tasks, is disclosed to the applicable Client business through the white-label dashboard and is subject to the Client's own privacy and data governance practices. SentireSystems does not control Client's downstream disclosure or use of End User personal information obtained through the Platform.

3.3 Legal Disclosures. SentireSystems may disclose personal information to law enforcement, courts, regulators, or other governmental authorities where required by applicable law or legal process, or where SentireSystems reasonably believes disclosure is necessary to protect the rights, property, or safety of SentireSystems, its clients, or the public.

3.4 Business Transfers. In connection with a merger, acquisition, asset sale, or other business transaction, personal information held by SentireSystems may be transferred to a successor entity, subject to that entity's assumption of obligations consistent with this Policy.

3.5 No Sale of Personal Information. SentireSystems does not sell personal information of End Users or Business Users to third parties for their independent marketing or commercial purposes.

4.1 Inbound Session Processing; Purely Informational Outbound Calls. Actions taken by the Platform during an active inbound call session — including booking an appointment, confirming availability, and collecting caller information — do not constitute outbound telemarketing under the FTC Telemarketing Sales Rule (16 C.F.R. Part 310) (“TSR”) and do not require prior express written consent under the TSR or the TCPA (47 U.S.C. § 227). This exception applies only to actions completed within the caller's original inbound call session. Outbound AI-generated calls or SMS messages that are purely informational in nature — such as appointment reminders for appointments previously scheduled by the caller and no-show notifications — are not subject to the TSR's written agreement requirement, provided the message contains no solicitation, upsell, promotional offer, or inducement to purchase any good or service. Notwithstanding the foregoing, because the Platform uses an AI-generated or prerecorded voice, all such calls remain independently subject to the TCPA's prior express written consent requirement regardless of their informational character. Client is solely responsible for obtaining and maintaining TCPA-compliant written consent records before placing any such communications.

4.2 Outbound Communications; Prior Express Written Consent Required. For any AI-generated voice call, SMS message, or other outbound communication placed by the Platform after the close of a Caller's inbound session (“Outbound Communication”), prior express written consent from the recipient is required before any such communication is placed or sent. SentireSystems operates as a technology facilitator for Outbound Communications; Client is the “seller” and/or “telemarketer” as those terms are defined under the TCPA and TSR and bears primary responsibility for compliance with all applicable telemarketing, robocall, and communications laws.

4.2.1 Capacity to Consent; Minors. Consent under the TSR must be express and informed. Because individuals under the age of 18 generally lack legal capacity to enter into binding agreements under applicable contract law, prior express written consent obtained from a minor may not be legally enforceable. Client must not direct Outbound Communications to any individual known or reasonably believed to be under 18 without first obtaining verifiable parental or guardian consent, and bears sole responsibility for any required age-verification procedures.

4.2.2 SMS Opt-In Disclosures. Where a Caller opts in to receive SMS messages through the Platform, that opt-in is voluntary and affirmative: the Caller must either voluntarily provide their mobile telephone number and initiate contact with the Client's business by phone or text, or affirmatively reply to an opt-in request as described in Section 4.3 below. Message frequency varies and is determined entirely by the Caller's own interactions with the applicable Client business; no fixed number of messages is guaranteed. Message and data rates may apply, depending on the Caller's mobile carrier and plan. Consent to receive SMS messages is never required as a condition of purchasing any good or service from the Client business. Callers may reply STOP at any time to opt out of further messages, or reply HELP for assistance, as further described in Section 4.4 below. Mobile telephone numbers and SMS consent records collected through the Platform are not shared or sold to any third party for that third party's own marketing purposes. A consumer-facing summary of these disclosures is also published at sentiresystems.com/sms-terms.

4.3 SMS Confirmation Opt-In Mechanism. Where the Platform is configured to send SMS messages, SentireSystems engineers and maintains an automated SMS confirmation opt-in mechanism covering system-initiated automated texts — specifically, the missed-call recovery text sent after an unanswered call and the dropped-call recovery text sent after a call disconnects mid-conversation. The first such automated text to a given Caller telephone number is a single opt-in request identifying the Client business, describing the messages to be sent, and disclosing message frequency, applicable message and data rates, and STOP/HELP instructions. No further automated SMS communications of that kind are delivered to that number until the Caller returns an affirmative reply (“YES” or equivalent). A Caller's affirmative reply, or the Caller independently texting the Client's number, constitutes an E-SIGN-compliant record of prior express written consent for future automated SMS messages from the specific Client business, stored as a consent record in accordance with Section 5 below. This opt-in mechanism does not gate replies within a conversation the Caller initiated by texting the Client's number directly, or follow-up messages within that same active conversation, as the Caller's own outbound text is itself the opt-in signal for that thread.

4.4 Opt-Out and Revocation. Any Caller may revoke consent for outbound communications at any time by replying STOP, CANCEL, UNSUBSCRIBE, QUIT, or END to any automated SMS, or by verbally requesting to be removed during an AI-generated voice call. Upon receipt of any such opt-out, the Platform immediately adds the Caller's number to the Client's entity-specific Do Not Call list and permanently ceases all further automated SMS communications and AI-generated voice calls to that number from that Client, without human intervention. All opt-out requests and their date and time of receipt are recorded and retained as required by the MSA.

4.5 Calling Hour Restrictions. All Outbound Communications are placed only between 8:00 a.m. and 9:00 p.m. local time at the location being called. No exception to this restriction applies to AI-generated or prerecorded voice calls.

4.6 Client Responsibility. Client is solely responsible for: obtaining and maintaining valid prior express written consent records for all Outbound Communication recipients; scrubbing contact lists against the National Do Not Call Registry within the preceding thirty-one (31) days before enabling any outbound campaign feature; ensuring all outbound call and SMS content complies with applicable federal and state telemarketing, robocall, and communications laws; and providing written authorization to SentireSystems before enabling any outbound voice or SMS campaign feature, as required by the MSA.

4.7 SMS Program Disclosures. Mobile telephone numbers collected for SMS purposes are used solely to deliver the automated text messages described in this Section 4 and are not shared or sold to third parties for their own marketing or commercial purposes. Message frequency varies depending on the End User's interactions with the applicable Client business — for example, a single automated text following a missed call, or an ongoing two-way conversation initiated by the End User — and no fixed number of messages is guaranteed. Message and data rates may apply, as determined by the End User's mobile carrier and service plan.

5.1 Consent Record Contents. SentireSystems records and stores each Caller's prior express written consent obtained through the Platform's SMS opt-in mechanism. Each consent record includes, at minimum: the consenting individual's telephone number; the date and time of the opt-in request SMS transmission; the date and time of the Caller's affirmative reply; the disclosure language presented at the time of consent (including the specific Client business name, the nature of communications consented to, and any voice call disclosure required by the MSA); and the specific Client business for which consent was obtained.

5.2 Retention Period. Client shall maintain written records of all prior express written consents obtained for Outbound Communications for a minimum of four (4) years from the date of collection, or such longer period as required by applicable law, in accordance with Section 5.3 of the MSA. SentireSystems will store consent records in its database for the same minimum period with respect to consents collected through the Platform's automated mechanisms.

6.1 Security Measures. SentireSystems maintains commercially reasonable technical and organizational measures to protect Client Data and End User personal information, including: (a) encryption of data in transit (TLS) and at rest; (b) Row-Level Security (RLS) enforced at the database level (Supabase PostgreSQL), ensuring that each Client tenant's data is fully isolated and no Client can access another Client's data; (c) role-based access controls, with Business Users limited to their own tenant's data and Platform administrators operating under a separately authenticated administrative role; (d) storage of all API keys and credentials in AWS Secrets Manager, with no credentials stored in application code or version control; (e) encrypted storage of per-tenant Google Calendar OAuth tokens; (f) per-call Redis session isolation, with automatic session cleanup upon call termination; and (g) continuous system health monitoring and alerting via Sentry.

6.2 Breach Notification. In the event of a confirmed security breach resulting in unauthorized access to or disclosure of Client Data or End User personal information processed through the Platform, SentireSystems will notify the affected Client without undue delay to the extent required by applicable law. Such notice will describe, to the extent then known, the nature of the incident, the categories of data and individuals affected, the likely consequences, and the measures taken or proposed to address the incident. Client is responsible for providing any required downstream notice to End Users and regulatory authorities.

7.1 Client Data Retention During Term. SentireSystems retains Client Data — including call logs, transcripts, appointment records, callback tasks, and agent configuration settings — for the duration of the Subscription Term and for a period of thirty (30) days following termination or expiration of the MSA (the “Export Window”), during which Client may request a data export in a commonly used machine-readable format (JSON or CSV). Audio recordings are made available in their stored format. After the Export Window, SentireSystems will permanently delete Client Data, subject to the exceptions in Section 7.3 below.

7.2 Session Data. Per-call conversational session data stored in Redis (including turn history and booking progress) is automatically purged upon call termination and is not retained beyond the conclusion of the applicable call session.

7.3 Exceptions to Deletion. SentireSystems' deletion obligation following the Export Window is subject to the following exceptions: (a) Legal Hold — SentireSystems may retain Client Data beyond the Export Window to the extent required by applicable law or legal process; (b) Backup Systems — Client Data may persist in routine backup systems for a period not to exceed an additional thirty (30) days following the Export Window, after which all backup copies will be purged; and (c) Third-Party Provider Retention — to the extent that Client Data has been transmitted to and retained by Third-Party Providers (including Deepgram, OpenAI, and ElevenLabs) pursuant to their own data retention terms, SentireSystems' deletion obligation is limited to data within SentireSystems' direct control and does not extend to data retained by such Third-Party Providers under their own terms. Client is solely responsible for reviewing and, if desired, exercising any applicable deletion rights directly with such Third-Party Providers under their current terms. With respect to OpenAI, deletion requests may be submitted through privacy.openai.com or to dsar@openai.com. With respect to ElevenLabs, inquiries regarding access, correction, or deletion of personal data may be directed to legal@elevenlabs.io.

7.4 Voice Configuration Data; Non-Portability. AI voice profiles, voice characters, and voice identifiers configured through Third-Party Providers (including ElevenLabs voice IDs) are references to Third-Party Provider-hosted models and cannot be exported, transferred, or reproduced by SentireSystems at the end of the Subscription Term. Upon termination, SentireSystems will provide Client with a written summary of voice configuration parameters (including agent personality settings and voice identifiers) stored at the time of termination, but makes no representation that such identifiers will remain valid or accessible outside the Platform or through any other service.

8.1 California Consumer Privacy Act. To the extent that Client's use of the Platform involves the processing of personal information of California residents, the California Consumer Privacy Act (Cal. Civ. Code § 1798.100 et seq.) (“CCPA”) and the California Privacy Rights Act (“CPRA”) may apply. As between SentireSystems and Client, Client is the business (or service provider acting on behalf of a business) responsible for providing CCPA-required disclosures to End Users and honoring applicable consumer rights requests. SentireSystems processes End User personal information on behalf of Client as a service provider under the CCPA and will not sell or share such information for cross-context behavioral advertising.

8.2 Other State Privacy Laws. SentireSystems acknowledges that other state privacy statutes — including those enacted in Virginia, Colorado, Connecticut, Texas, and other jurisdictions — may apply to Client's processing of End User personal information through the Platform. Each Party will comply with all applicable privacy laws to the extent required by law. Client acknowledges that End User personal information processed through Third-Party Providers integrated into the Platform — including OpenAI's API — may be subject to state-specific consumer rights (including rights of access, correction, deletion, and portability) that Clients are responsible for facilitating with respect to their End Users. OpenAI's state privacy disclosures and consumer rights portal are available at privacy.openai.com.

8.3 Data Processing Addendum. Applicable law may require execution of a data processing addendum (“DPA”) for Clients serving End Users in California and other regulated states. The Parties will execute a mutually agreed DPA promptly and in any event prior to SentireSystems processing personal information of End Users located in any such jurisdiction, as provided in Section 8.8 of the MSA.

8.4 Biometric Information. Where the Platform is used to record, process, or clone human voice data, applicable state laws (including the Illinois Biometric Information Privacy Act, 740 ILCS 14/1 et seq., and comparable statutes) may classify voice recordings and voiceprints as biometric identifiers subject to specific collection, retention, and destruction obligations. Client is solely responsible for compliance with any applicable biometric data laws, including obtaining required written releases and maintaining a publicly available retention and destruction policy. SentireSystems makes no representation that its data handling practices satisfy any specific biometric data statute.

8.5 International Transfers. The Platform is operated from the United States. If Client or its End Users are located outside the United States, Client acknowledges that personal information will be transferred to and processed in the United States, where data protection laws may differ from those of Client's or End Users' jurisdiction. Client is responsible for ensuring that any such transfer complies with applicable law.

8.6 End User Rights. Under applicable state privacy laws, including the CCPA and comparable statutes, End Users (callers) who are residents of a covered jurisdiction may have the right to request access to, correction of, deletion of, or portability of their personal information processed through the Platform. Because SentireSystems processes End User personal information as a service provider on behalf of Clients, End Users should direct such requests to the applicable Client business in the first instance, as Client is the data controller responsible for facilitating those rights. SentireSystems will reasonably cooperate with Client in responding to verified End User rights requests to the extent that the relevant data is within SentireSystems' direct control. End Users may also contact SentireSystems directly at hello@sentiresystems.com; SentireSystems will direct the inquiry to the applicable Client. SentireSystems cannot guarantee a response to requests directed to a Client that is no longer an active subscriber.

The Platform's web-based dashboard may use cookies, local storage, and similar tracking technologies for authentication session management, user preference retention, and product analytics (via PostHog). Business Users may configure their browser to refuse cookies, but doing so may impair certain dashboard functionality. SentireSystems does not use third-party advertising cookies or engage in cross-context behavioral advertising through the dashboard.

The Platform is not directed to individuals under the age of 18, and SentireSystems does not knowingly collect personal information from children under 18. If SentireSystems becomes aware that it has inadvertently collected such information, it will delete it promptly. Clients must not configure the Platform for use in contexts where callers are primarily children under 13 without appropriate safeguards. Please discontinue use of the site if you are under 18.

This Privacy Policy is governed by the laws of the State of Delaware, without regard to conflict-of-laws principles, consistent with the governing law provision of the MSA (Section 13.1). Any dispute arising under this Policy is subject to the dispute resolution provisions of the MSA.

SentireSystems may update this Privacy Policy from time to time to reflect changes in the Platform, applicable law, or SentireSystems' data practices. Material changes will be communicated to Clients in accordance with the notice provisions of the MSA (Section 13.3). Continued use of the Platform following notice of a material change constitutes acceptance of the updated Policy. The “Last Updated” date at the top of this Policy reflects the date of the most recent revision.

Questions, requests, or concerns regarding this Privacy Policy or SentireSystems' data practices should be directed to SentireSystems LLC at hello@sentiresystems.com.

End Users (callers) who wish to submit a privacy inquiry, data access or deletion request, or complaint regarding SentireSystems' processing of their personal information should contact SentireSystems at hello@sentiresystems.com. SentireSystems will acknowledge receipt of End User inquiries within a reasonable time and will either respond directly or direct the inquiry to the applicable Client business, as appropriate. Where the requested action requires the cooperation of the applicable Client business, SentireSystems will notify the End User of that requirement and provide the Client's contact details to the extent reasonably available. End Users in California and other states with applicable privacy statutes may also contact their state attorney general's office or applicable data protection authority if they believe their privacy rights have not been honored.

The above contact details may be updated from time to time. In accordance with Section 13.3 of the MSA, notices to SentireSystems are effective when directed to the contact details published on SentireSystems' website or as otherwise provided to Client in writing, whichever is more current. Client is responsible for directing privacy-related inquiries to the most recently communicated contact details.