Privacy

What we hold, and for how long.

Dusklin AI is a brand of Odile Labs (OdileUSA L.L.C.), a Florida company founded by Tolga Coskun. This page describes what each product collects, who processes it, and how to make us delete it. It was last updated on 13 October 2026 to add Jobber to the CRM connections and say exactly what we read and write there. On 11 October 2026 it was updated to describe Store Chat, the AI sales assistant for online stores. On 9 October 2026 it was updated to say that the free line check can build a demo page for your business, and that replies to Facebook and Instagram messages may be written by Claude, an AI model made by Anthropic, and that we keep a short sales note for people who ask about our service. On 8 October 2026 it was updated to disclose Meta Pixel and to describe, for CRM connections (HubSpot, Pipedrive and LeadConnector), exactly what we read and write, how we protect it, and how to remove it. On 7 October 2026 it was updated to describe, for Google Calendar and Gmail, exactly what we access, how we use and protect it, and how long we keep it. Before that, it was updated on 28 September 2026 to say plainly that an owner can have the whole account deleted, and, the same day, to name all eight pages that carry the OpenAI measurement pixel — the sitelink pages had it too, not only the three named before. Before that, it was updated on 24 September 2026 to describe what happens when you talk to a demo from our pages, and to list the one activation text among the messages we send. On 20 September it added Drafts inquiries alongside business automation inquiries, and the free website speed audit, which began emailing a copy of its result that day. The OpenAI advertising pixel on /missed-calls and /contractors was disclosed here on 17 September; it had been live and undisclosed since 12 September.

After Hours, the phone receptionist

When a caller reaches a number we operate for a business, we receive the caller's phone number, a transcript of the conversation, and any message, name, or callback number the caller gives. Where the business has connected a calendar, we also receive the appointment the caller books.

That data exists so the business owner can read what their callers wanted. It is stored with our hosting provider and is visible to the business it belongs to and to Dusklin AI. Our speech provider keeps the audio and transcript for 90 days so the business can listen back in its console; our telephony provider keeps the call's numbers and times as carriers do. Since 12 October 2026 our speech provider is set not to use calls to train its models, and the language model that answers the calls is provided under terms that bar training on them.

To check that the receptionist answered well, we send the words of recent calls, what the caller and the receptionist said and not the audio, to TypeSafe, a language-model provider, which scores each call against a short list of questions, such as whether a caller's question was answered or passed on. The words a caller speaks can include their name and number. TypeSafe processes them under its own terms and may keep them for a period set by those terms; we do not control that period. The scores stay with Dusklin AI and are used only to improve the receptionist.

We keep call records, audio and transcripts for 90 days and the messages themselves for up to twelve months, then delete them. A business owner can ask us to delete theirs sooner.

The invoice audit and the Cost Recovery Diagnostic

When a shipper, a distributor or a club sends us invoices, rate agreements or energy bills for an audit, through audit.dusklin.ai or by email, we receive the documents and whatever they contain: vendor names, account numbers, addresses, line items and prices. Photos and scans are read by a third-party vision model to turn them into line items; the pages are sent for that one call only, under API terms that exclude training on them.

The documents and the findings are stored on our own server in the United States and are visible to the client they belong to and to Dusklin AI. We use them for the audit and for nothing else: no lists, no benchmarks sold on, no contact with the vendors on the invoices unless the client asks us to dispute a charge. Payment for the diagnostic goes through our payment processor; we never see a card number.

We delete the documents within 30 days of the audit or pilot ending, or sooner on request, and the client can ask for a copy of every finding first.

Private clubs and other businesses on the phone receptionist

A club or a business that gives us its phone line gets the After Hours treatment above, with two additions: a transfer, when a caller asks for the gatehouse, security or a manager, connects the caller to the number or extension the club gave us, and a message meant for a department is labelled with that department. We hold those numbers only to route calls.

Talking to a demo from our pages

When you press Talk to it here and allow the microphone, your browser streams your voice to our speech provider until you press End call, leave the page, play another sound or the demo hangs up, and for ten minutes at most. The demo says it is an AI and that the call is recorded. The page says this before you press the button, the demo asks whether that is all right, and if you say no it ends the call. Our speech provider keeps the audio of both sides, a transcript and its automatic assessment of the call for 90 days, then deletes them; our own systems keep no audio and no full transcript. If the demo takes a message, books a time or promises you a callback, a language model may read the call to pull out the name, number and details you give; those are sent to us and kept like any other message, for up to twelve months, and a booking also stays on that demo's calendar until 90 days after the booked day. The businesses in the demos do not exist, so a made-up name and number work just as well. Our analytics count only that a call started, ended or could not get the microphone, and we do not use demo calls to train models; since 12 October 2026 our speech provider is set not to either. Write to hello@odilelabs.com to have a call deleted sooner.

The tap-through call on the home page needs no microphone. If you use its microphone button, one short clip is turned into text by your browser's own speech service or by our server, used to pick the next line, and not kept by us.

The free line check and the free greeting

When you ask us to check your business line, we keep the business name, the number, your email and the time zone you chose for 90 days, together with the record of the one call we placed: when it was dialled and whether a person, voicemail or nothing answered. We first check with Google's Places service that the number is published as a business's line; that lookup sends the name and number to Google and nothing else. If you pick a trade, we also keep it and the city you typed, and build a demo page where an AI receptionist answers as your business; that page holds the business name, number, trade and city, is reachable only by its link, and is deleted when you ask. No audio is recorded and nothing is said to a voicemail. You receive one email with the result and no other mail from that request; reply "no more" and you hear nothing further from us.

When you take a free phone greeting, we keep the business name, the email you gave, the text and the audio file for 90 days so the download link works, and we send one email with that link. The wording is read by our speech provider, which holds nothing beyond making the file.

Dusklin Reviews

We read the public reviews of a business from the Google Places API and draft replies to them. The reviews are already public. The drafts are generated by a language model. We store the business name, its place identifier, and the drafts we produced. We do not collect anything from the reviewers beyond what Google publishes.

Plate, the calorie counter

A photo you send is passed to a model to be described and estimated, then discarded. We do not store the photo, and we do not keep a history of what you ate. There is no account and no sign-in.

Website support chat

The support bot’s replies come from our AI assistant (the same one that answers our phone line), run by our voice and AI provider, ElevenLabs: your chat messages, with email addresses and phone numbers removed first, are sent to it to write each reply. The support bot stores your chat with our hosting provider, Cloudflare, under a private browser session for 7 days by default. In Privacy and history you can choose 1, 7 or 30 days or delete stored content. Minimal pause and replay records remain to respect a human handoff or stopped automation. We do not link customers by name or send marketing from chat.

The curated FAQ and human enquiry work without model processing. If you separately enable contextual AI, new chat messages and up to eight eligible recent chat turns go to Anthropic to interpret your question. Enquiry contact and request fields are excluded. Email and phone strings in chat are redacted, but the filter cannot detect every personal detail: keep names, addresses, passwords and other personal details in the separate enquiry form. You can withdraw AI consent at any time. Anthropic processes API requests under its privacy policy; deleting the Dusklin transcript does not recall a request already processed by Anthropic.

Only when you consent to an enquiry do we share its contact details, request and conversation with the Dusklin team. A human handoff without that consent shares only the fact that help was requested. An appointment is a request until a person confirms it. The shared monthly AI quota can run out; the bot then labels its FAQ fallback.

Store Chat (AI sales assistant on online stores)

On a store that uses Store Chat, or on a Store Chat demo, what you type is sent to Anthropic, with email addresses and phone numbers removed first, so its AI model can pick matching products and policies from the store's public catalog. The reply itself is built from that catalog, never written freely by the model. Your chat is stored with our hosting provider, Cloudflare, for 7 days, and a scrambled version of your internet address is used only to limit abuse. If you choose to send an enquiry, we keep your name, email or phone and question for 30 days and send them to that store's owner; on a demo for a store that has not signed up, they go to the Dusklin AI team instead. The store catalog and policies we read are already public, and we keep a copy for up to 6 hours.

Email and sign-up

If you sign up for a product we hold the business name, your email address, your phone number, and your business hours, because the product cannot work without them. Payments run through our payment processor, which holds the card details; we never see them. If we email you and you reply, that correspondence sits in our company mailbox.

Business automation and Drafts inquiries

If you request an automation or Drafts review, we store your name, business, creator or project name, email, optional phone number, and the workflow or project description you submit, together with a request reference, date, service type and status. These records are held with our hosting provider for up to two years so Dusklin AI can review and respond to your inquiry. You can ask for a copy or deletion using the contact details below. The inquiry does not subscribe you to marketing, connect your mailboxes, authorize messages to your customers, publish content or launch advertisements. Please do not include passwords, API keys or customer message contents. If we agree to provide a service, the connected accounts, access permissions and data retention are defined in that service's scope before setup.

Free website speed audit

If you use the free speed audit on /websites, we store the website address, the name and the email address you enter, together with the date and the result, for up to one year with our hosting provider. The address you give is sent to Google’s PageSpeed Insights service, which loads that public page to measure it; your name and email are not sent to Google. The score is shown to you on the page, and we send one copy of it to the email address you entered, through Resend, our email delivery provider. That is the only email the request sends: it does not add you to a list or start a sequence. If someone entered your address without your knowledge, reply to the email or write to hello@odilelabs.com and we will delete the record.

Data from Google APIs

Some of our own tooling reads YouTube channels and calendars that we or our customers own, using Google's APIs and only with the account holder's consent through Google's own permission screen. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell that data, do not use it for advertising, and do not let humans read it except where you ask us to fix something or the law requires it.

Google Calendar and Gmail, for After Hours owners

What we access. If an owner connects Google Calendar, we read the busy and free times of the one calendar they choose (Google's free/busy answer carries no event titles or details), create an event there for each booking the receptionist makes, and delete only events we created ourselves. A health check confirms the connection still works by asking Google for one event and keeping only whether Google answered; the event is not stored. If an owner connects Gmail, we only send messages from their address: follow-ups the owner wrote or approved, to their own customers. We never read, search or store anything in their mailbox. We keep the Gmail address they connected.

How we use it. Only to run those features for that owner: offering callers times that are actually free, putting the booking on the owner's calendar, and sending the owner's follow-up. We do not use Google user data for advertising, to build profiles, or to train any AI or machine-learning model, ours or anyone else's.

Who receives it. Nobody buys it or receives it for their own use. The open times are read to the caller during that call by the voice service that answers the line; the booking goes to the owner's own Google Calendar and the follow-up to the customer the owner chose. Our hosting provider, Cloudflare, stores the encrypted connection token for us.

How we protect it. Every request to Google and to our servers travels over HTTPS (TLS). The long-lived refresh token Google gives us for each connected calendar or mailbox is encrypted before it is stored, with AES-256-GCM and a key derived separately for each business, so one business's token cannot be decrypted with another's. The secret that key comes from is held as a protected server secret, never in our code or on a page. Short-lived access tokens expire within an hour. Only the signed-in owner can connect or disconnect an account, no token is ever shown in the console or included in an email, and nobody at Dusklin AI reads calendar or mail content.

How long we keep it, and how to delete it. We keep the encrypted token only while the connection is in use. An owner can disconnect Gmail from the console at any time, which revokes our access at Google and deletes the token at once. For Calendar, write to hello@odilelabs.com and we delete the token within 30 days, usually the same day; closing the account deletes both. Anyone can also remove our access at any time at myaccount.google.com/permissions, after which the stored token no longer works. The bookings already on an owner's calendar are theirs and stay there.

CRM connections, for After Hours owners

What we access. An owner can connect HubSpot, Pipedrive, LeadConnector or Jobber, either by approving access on the CRM's own permission screen or by pasting a key the CRM issued. We use the connection only for that owner's business. Before a call, we look up the caller's number and read the matching contact's name, email, owner and deal stage. During a call, if the owner leaves that switched on, the receptionist can look a contact up, create or update the caller as a contact, add a note, open a deal and, on a LeadConnector calendar the owner chose, book the appointment the caller agreed to. Callers in the console's customer list are copied to the CRM as contacts (their number, and their name and email when known), and so are the owner's edits there. After a call, we add a note with the call's summary to the caller's contact; with LeadConnector we also add the call to that contact's conversation, and, only if the owner turns it on, we open one deal per caller. With Jobber, which the owner connects by approving access on Jobber's own screen, we look the caller up among the business's clients, create or update them as a client, add the call as a request, and, when the caller agreed a time, add a job with a visit at that time; for that we read and write clients, requests, jobs and visits. We do not read anything else in the CRM, and we never delete anything there.

How we use it. Only to run those features for that owner: greeting a known caller properly, and putting each call where the owner already works. We do not sell CRM data, use it for advertising, build profiles from it, or use it to train any AI or machine-learning model.

Who receives it. The contact details read before or during a call are passed to the voice service that answers the line, for that call only. The notes, contacts, deals, conversation entries and appointments we write go to the owner's own CRM. Our hosting provider, Cloudflare, stores the encrypted connection for us.

How we protect it. Every request to the CRM and to our servers travels over HTTPS (TLS). The key or the access and refresh tokens are encrypted before they are stored, with AES-256-GCM and a key derived separately for each business, so one business's connection cannot be decrypted with another's. No key or token is ever shown in the console or included in an email; the console shows only its last four characters, or that it came from the CRM's sign-in. Only the signed-in owner can connect or disconnect a CRM.

How long we keep it, and how to delete it. We keep the encrypted connection only while it is in use. Disconnect in the console deletes the stored key and tokens at once. For each call we keep a delivery receipt (the call's id, the caller's number, the summary and whether the CRM accepted the note) for 90 days, so a failed write can be retried without being written twice. The owner can also remove our access in the CRM itself at any time. What we wrote to the CRM belongs to the owner and stays there.

Text messages (SMS)

Apart from alerts to our own team, two kinds of text message leave our system, plus one activation text to a business owner when their receptionist goes live. All of them come from a phone number we own.

• To a business owner who signed up. When your receptionist takes a call, we text you the caller's name, number and what they wanted. You give us that mobile number yourself on the sign-up form, and ticking the consent box beside it is what turns these messages on — leave the box unticked and your messages stay in the console only. If you ticked it, you also get one text when your receptionist goes live, with the number to forward your calls to.
• To someone who called a customer's line and hung up. They get one message saying the call was missed, inviting them to reply with a good time to be called back. It is sent once per call, never repeated, and only to a number that dialled the business.

Reply STOP to any message and we stop texting that number; reply HELP for help. Message and data rates may apply from your carrier. Message frequency depends on how many calls come in.

Mobile phone numbers and consent to receive text messages are never shared with third parties or affiliates for marketing purposes, and are never sold. Mobile numbers are used only for the transactional messages described on this page — never for marketing. OdileUSA L.L.C. does not engage in affiliate marketing or third-party lead generation, and the only messages it sends for a customer business are the call notifications, the one activation text and the missed-call texts described on this page. For texting, a caller's number goes only to the business whose line they called and to the telecommunications provider that carries the message on our behalf, which is what makes delivery possible.

Messages to our Facebook Page and Instagram account

When you message Dusklin AI on Facebook Messenger or Instagram, Meta passes us your message, your name as Meta shows it and the ID Meta gives you for our Page. We use them only to answer you. Some common questions, such as prices or how the service works, get an automatic reply set up in Meta's own inbox tools. To pick the right answer, the text of your message may be sent to TypeSafe, a language-model provider, which says what kind of message it is, for example a demo request or a price question; TypeSafe does not write to you. Other replies are written by Claude, an AI model made by Anthropic, working in our Meta Business Suite inbox: it reads the conversation and answers only from the facts published on this site, and Anthropic processes that text under its own terms. Tolga can read and take over any conversation. Our reply goes back through Meta. When a conversation needs Tolga, he is sent your name and a link to the conversation, not the message text. We keep the ID of the last message we answered in each conversation, its type and when we answered, so we never answer twice, and, if you ask about our service, a short sales note with your name, your business and what you asked; the messages themselves stay in Meta's inbox. To have us delete what we hold about you, message us "delete my data" or write to hello@odilelabs.com; we do it within 30 days, usually the same day.

Website analytics

Our pages use Google Analytics to count visits and see which page someone arrived from. It sets a cookie in your browser and records the page you viewed, the link that sent you and a coarse location from your IP address. We use it for one thing: to tell whether anything we publish is being read. We do not use it to build an advertising profile and we do not pass it to any ad network. The other Google tag on these pages is the ads conversion tag described below. Eight of our pages also carry an OpenAI measurement pixel, named below. Browser settings and extensions that block analytics work here and cost you nothing on this site.

Advertising measurement

When we run ads, the same Google tag reports back that a visit turned into a phone call or a signup, so we can tell which ads are worth paying for. It reports the event, not who you are — we do not send Google your name, email or phone number. We use this Google tag for conversion measurement. If you block the cookie, nothing about your visit is reported.

We also advertise inside ChatGPT, and the pages the ad and its sitelinks point at — /afterhours, /salons, /palm-beach, /contractors, /demo, /missed-calls, /linecheck and /calculator — carry OpenAI's measurement pixel as well. It loads a script from bzrcdn.openai.com and sets two first-party cookies, __oppref and __obref, which record that you arrived from one of our ads. When someone who arrived that way later starts a trial, our server tells OpenAI that the ad worked. That report carries the plan and the amount, plus the IP address and browser user-agent of the original visit, which is how the click and the signup are matched; it does not carry your name, email or phone number. Blocking the pixel or clearing those cookies stops the report and changes nothing else about the site.

Pages on dusklin.ai that use Google Analytics also use Meta Pixel. It receives page views (PageView), successful signup starts (Lead), and trial or subscription starts after checkout (StartTrial or Subscribe), with the plan price and currency for the checkout events, the browser’s IP address and cookie identifiers. We send no form contents, names, email addresses or phone numbers to Meta Pixel. We use it to measure and retarget Meta ads. Meta keeps this data according to its own retention policies. You can manage personalised ads in Meta’s ad preferences and use your browser’s tracking and cookie settings to block or clear the pixel’s cookies.

What we never do

We do not sell personal data, and we do not use call transcripts or customer data to train models. The only thing any ad network ever receives from us is the measurement described under Advertising measurement above — an event, an amount, cookie identifiers, and the IP and browser string needed to match a click to it. Customer records, call transcripts, caller numbers and message contents are never sent to an advertiser.

Your choices

Write to hello@odilelabs.com and ask for a copy of what we hold about you, or ask us to delete it. We usually answer within a day or two, and never later than 30 days. A business owner can have the account itself closed and deleted the same way, with everything stored under it: the calls, messages, customers and settings. The same applies to the account the After Hours by Dusklin iPhone app signs in to. We email to confirm when it is done. What the receptionist is and is not allowed to do, and what we check every morning, is on the trust page. If you cancel a subscription, tell us if you want the data gone as well; otherwise it ages out on the schedules above.

Children

Our products are sold to businesses and are not directed at anyone under 13.

Changes

If this page changes in a way that affects you, we will say so here with a new date at the top, and email current customers.

Company

OdileUSA L.L.C., Florida, United States
Registered office: 7901 4th St N Ste 300, St. Petersburg, FL 33702
Dusklin AI and Dusklin After Hours are product names used by OdileUSA L.L.C.

Contact

hello@odilelabs.com

Terms

Terms of service