Privacy Policy

Dint+ Inc. is responsible for the Dint+ platform described in this notice. The SMS section identifies Dint Group LLC as the operator responsible for the Dint+ Customer Care SMS program. Use the Privacy requests link below or the privacy inbox shown on the Contact page to ask about processing, exercise rights, or appeal a response. You can start a request without signing in. Independent transaction participants may be responsible for their own use of information received to fulfill a booking.

We process information you provide, such as names, email addresses, phone numbers, profile details, authentication and account identifiers, verification status, and account settings, to create and secure accounts, authenticate sessions, display profiles, communicate with you, and provide selected features. Information also comes from transaction participants and providers performing authorized checks.

We process submitted posts, reviews, ratings, mentions, tags, messages and message metadata, uploads, listings, bookings, reservations, and support requests for communication, publishing, fulfillment, moderation, and dispute handling. Your audience choices affect who can see content. Information shared with recipients may be retained by them. Encryption and access differ by feature; this notice does not promise that every data type or message is end-to-end encrypted.

Dint Group LLC, an LLC under Dint+ Inc., operates the Dint+ Customer Care SMS program and is responsible for its messaging and consent records. For this program, we process the mobile number you supply, your email when supplied, your request or signup choice, and relevant messaging and opt-out records. When you affirmatively submit SMS consent at /sms or during signup, we save the exact consent statement and version, collection method and source, and server receipt time in our consent register. Authorized support staff can access the record in a protected consent register; an email notification may also be sent when configured. The optional /sms/email flow still requires you to send the prepared email; a draft alone does not submit consent. We also use limited network information to prevent abusive submissions. A signup consent receipt does not establish account creation or verification of the supplied phone number. We use these records to respond to your request, establish consent, deliver permitted messages, handle support, prevent abuse, and honor opt-outs.

We do not sell mobile information or SMS opt-in data, and we do not share mobile information with third parties or affiliates for their marketing or promotional purposes. SMS opt-in data and consent are excluded from information disclosed for those purposes. Limited disclosure to service providers, including Twilio and communications carriers, is permitted only as necessary to operate and deliver the messaging service, process support requests, and maintain consent or suppression records on our behalf. Legally required disclosures remain subject to applicable law; they do not authorize marketing use.

Message frequency varies with your request. Message and data rates may apply. Reply STOP to opt out or HELP for assistance, or contact support. We retain consent and opt-out evidence as needed to honor your choices, resolve delivery disputes, prevent unauthorized contact, and meet applicable obligations. An opt-out record may be retained to prevent future messages even after an account is closed. Use Privacy requests to ask about access, correction, deletion, or other rights.

A customer who uses a Dint+ Line to communicate with you is responsible for their own sender identity, messaging purpose, consent collection, and privacy notice. Dint+'s Customer Care consent does not authorize that customer's messages. Forwarding a call or speaking with an AI answering agent does not by itself authorize unrelated SMS or marketing.

For the Line recipient-consent flow at /sms/line, we process your submitted mobile number to bind permission to that sender and ownership period. The consent register retains a protected number identifier, the sender, Line, purpose, exact disclosure and version, submission and confirmation times, and the inbound YES or NO message reference. Message contents and phone numbers are processed through the messaging service to verify and deliver the exchange. STOP records prevent further sending. The page temporarily stores its receipt access token in your browser's session storage so you can return after sending your confirmation; closing the browser session or clearing site data removes that local receipt access. These records are used to establish and enforce your choice, handle disputes and support, and meet applicable obligations. They are not sold or shared for another party's marketing.

A call forwarded to a Dint+ Line can pass the caller's number, the called or forwarding number where available, call timestamps, duration, routing and delivery details, and audio needed for the chosen answering feature to Dint+ and its communications providers. Configured AI providers process the audio and context needed to answer; enabled transcription, summaries, and conversation history are made available according to the feature and account permissions. Twilio supports carrier connectivity and LiveKit supports configured realtime media. Other selected AI providers are described in this policy.

Line owners must disclose AI participation and provide legally required notices and consent for recording or transcription before that processing begins. An owner's decision to enable AI does not replace a caller's rights or any required caller consent. Do not assume every call is recorded or that every feature stores the same data. Review the feature-specific settings and notices. Contact the Line owner or Dint+ support with the relevant call reference for a privacy request; do not send unnecessary sensitive call content by email.

Web and app interactions can create device and installation identifiers, session data, operating-system and browser information, network and request logs, IP addresses, diagnostics, cookie and SDK data, security events, and fraud or verification results. These support authentication, delivery, troubleshooting, abuse prevention, and service reliability.

Optional website analytics collect event and random session identifiers, time, generalized page categories, referrer domain, and broad device and browser categories after analytics consent. Private path identifiers and query strings are excluded from this page-analytics payload. Cookie preferences let you reject or withdraw optional website analytics and Crisp chat. Browser Do Not Track and Global Privacy Control disable this website’s optional analytics.

Location features can use precise coordinates with device permission and locations you enter, such as service or booking addresses. Approximate location may be inferred from network information or a selected city. These data support nearby discovery, service areas, routing, and fulfillment. Public maps may show a coarser location than the coordinates used internally.

Camera, microphone, and photo or file access support the capture, calls, uploads, identity, and AI features you select. Contacts support contact discovery or invitations where offered; calendar access supports scheduling or calendar integration; push permission supports notifications. Availability differs between web, iOS, and Android. Permission to use a device capability is not permission for unrelated processing. Use browser or operating-system settings to revoke access; revocation does not erase information already submitted.

Transactions create records of participants, amounts, currency, payment and payout references, methods and masked details, balance changes, holds, refunds, chargebacks, tax details where required, and verification or fraud-review outcomes. We use these for fulfillment, accounting, payment support, eligibility, fraud prevention, and legal obligations. Stripe payment and connected-account flows process payment or payout details; some data are collected directly by Stripe.

Provider onboarding can include legal and business identity, credentials, licenses, evidence, background-check consent, and check results. Veriff integration supports identity verification where invoked. Required checks and information depend on the activity. Do not email identity documents; use the secure flow presented to you.

AI features process prompts, conversation context, saved memories, uploaded files and documents, generated content, preferences, settings, feedback, usage and technical logs, and feature identifiers. These data support responses, personalization, specialist agents, retrieval, recommendations, moderation, billing, troubleshooting, and requested actions.

Selected processing is sent to the provider used for the feature. OpenAI integrations support configured AI and media functions; ElevenLabs integrations support configured voice generation and custom voices. Providers and features can vary. A particular vendor is not used for every interaction. Do not upload unnecessary sensitive information. This notice does not create consent to train a general-purpose model or promise that every provider has the same retention and training terms.

Calling and media features process audio, video, facial images, selected avatar images, voice samples, generated speech, transcripts, session metadata, and related content as needed for the chosen feature. LiveKit integrations support realtime media. Avatar integrations include configurable HeyGen, D-ID, and LemonSlice providers; only the selected provider processes a particular avatar session.

Call Assistant call history includes transcripts and summaries; that feature does not save an audio recording. Other media features may operate differently. Custom-voice features send authorized samples for voice generation. An image, voice sample, or avatar is personal information when it relates to a person. Generating content from a likeness and using it to identify a person are different purposes; review any additional verification notice presented by the feature. Review the feature’s notice and obtain the necessary permissions before submitting someone else’s media.

Content you choose to share with wellness, therapy, fitness, nutrition, medication, or other specialist services or AI may reveal health or other sensitive information. Identity records, precise location, private communications, and voice or facial media may also be sensitive. We process submitted information to provide the selected feature, protect users, and satisfy applicable obligations; do not provide more than is needed. An AI feature is not a medical provider or an emergency service.

Search, recommendations, provider matching, ranking, personalization, eligibility checks, moderation, and security controls use automated processing and information relevant to the feature. Results may reflect supplied preferences, location, availability, content, transaction state, and activity. An AI recommendation is not a guarantee. Contact us to challenge an error, request human review, or exercise an applicable automated-decision right. Not every automated operation is a decision producing legal or similarly significant effects.

Where a legal basis is required, we process information as necessary to provide the requested contract or take requested pre-contract steps; meet legal obligations such as accounting and lawful requests; protect legitimate interests such as security, fraud prevention, service support, and proportionate improvement, balanced against your rights; or with consent where required, including optional technologies and applicable sensitive processing. Withdrawing consent does not invalidate earlier lawful processing. Special-category information requires any additional condition imposed by applicable law.

Relevant customers, hosts, providers, businesses, and other transaction participants receive the information needed for communications and fulfillment. Public content is visible to its selected audience. Service providers support payments, identity, hosting, communications, media, AI, security, analytics, and customer support. Confirmed integrations include Stripe, Veriff, Firebase for configured mobile messaging and related services, LiveKit, OpenAI, ElevenLabs, configured avatar providers, Cloudflare Turnstile security checks, and optional Crisp chat. Their involvement depends on the feature you use.

We may disclose information where legally required, to protect rights or safety, investigate fraud or security issues, establish or defend claims, or in connection with a lawful business transfer with applicable safeguards and notice. A processor’s access for a defined service is different from another marketplace participant’s independent use.

This website’s optional analytics are controlled by Cookie preferences. The website does not implement an advertising-pixel loader or a sale-of-data flow. This describes the website implementation, rather than a legal classification of every processor or mobile SDK. You can submit any applicable request to opt out of sale or sharing, targeted advertising, or certain profiling through Privacy requests. Global Privacy Control disables optional website analytics; it does not delete an account or stop essential processing.

Depending on your location and the applicable law, you may request access to or knowledge of your information, correction, deletion, a portable copy, restriction, objection, withdrawal of consent, or review or appeal of a denied request. California residents whose information is subject to the CCPA may also opt out of sale or sharing and limit covered sensitive-information uses, and may exercise rights without unlawful discrimination. Rights can be subject to legal exceptions.

Use Privacy requests or the privacy contact. Tell us the right you want to exercise and your region. We may verify ownership using existing account information and a secure process proportionate to the request, and may require an authorized agent to show authority. We do not require account creation to initiate a request. Opt-outs are not subject to the same identity verification as access to specific records. We will explain a denial or applicable exception and how to request review. You may complain to your competent privacy authority where that right applies.

Use the Account and data deletion link below to request closure or deletion without signing in. The mobile app also has an account-deletion screen. Removing the app is not account deletion. Review recurring subscriptions and open transactions separately. Profile and account privacy settings let you change supported details, visibility, and read receipts. Device settings control permissions and push notifications; Cookie preferences controls optional website technologies.

Account and profile data are kept while needed to maintain the account, provide requested services, and complete closure. Content, AI conversations, memories, and generated assets are kept according to the selected feature and deletion controls, with separate records potentially requiring separate deletion. Transaction, payout, tax, consent, and dispute records may remain after closure for required accounting periods, claims, fraud prevention, and legal holds.

Security and diagnostic records are retained as needed to investigate incidents, protect services, and troubleshoot. Support and privacy-request records are retained to resolve requests and demonstrate their handling. Verification records are retained according to the check, applicable obligations, and necessary review. Backups and processor systems can require additional deletion cycles; retained data must remain protected and limited to the reason for retention.

Website page-analytics sessions have a 30-minute inactivity window; unsent analytics events expire after 24 hours or when the tab’s session storage ends. The referral cookie lasts up to 14 days. Cookie preferences expire after 180 days. These browser periods are not backend retention guarantees. Request information about retention or deletion exceptions through the privacy route.

Providers and infrastructure may process information outside your home country. Where transfer restrictions apply, the responsible parties must use an applicable lawful mechanism, such as an adequacy decision or contractual safeguards, and any required supplementary protections. Contact us for information about safeguards relevant to your request. This notice does not claim a certification or an adequacy decision for every destination.

Safeguards include authentication, access restrictions, protected session cookies, validation, secure provider flows, and feature-specific protections. No system is perfectly secure. We investigate suspected security incidents and provide notifications to affected people or authorities where legally required. Use support to report a concern; do not send credentials or exploit details through public posts.

Dint+ features require the eligibility and legal capacity described in the Terms and any higher age requirement shown for the offering. Do not provide a child’s sensitive information or use a restricted feature on a child’s behalf without the required authority and lawful basis. A parent or guardian concerned about a child’s account or information can contact the privacy team to request review or deletion.

The version, last updated date, effective date, and change summary appear with this document. Material changes require appropriate notice and renewed agreement where required before the affected activity continues. A new notice is not retroactive permission for a different use of your information. Contact Dint+ Inc. through the linked contact and request pages.