DETAILFORGE

DETAILFORGE is operated by GLODUSK (“DETAILFORGE”, “we”, “us”, “our”). This Privacy Policy explains what personal information we collect, how we use and share it, how long we keep it, and the rights you have over it. We’re the data controller for personal information collected directly through our marketing site, sign-up flow, and the DETAILFORGE platform. Where a shop uses DETAILFORGE to handle their own customers’ information, the shop is the controller of that data and we’re a processor acting on the shop’s instructions.

1. Definitions

Personal information: information that identifies or could reasonably be linked to an individual.
Shop: a business with a DETAILFORGE account; the data controller for its own catalog, customer, and quote records.
Customer: an end user who interacts with a shop’s embedded configurator or shared quote link.
Service: the DETAILFORGE platform, including the marketing site, the web app, the DETAILFORGE phone app for iOS and Android, embedded surfaces, and APIs.
Subprocessor: a third party we engage to process personal information on our behalf.

2. Information we collect

From shops (account holders)

Account: email address, workspace name, role. You sign in with Google or with a one-time code we email you, through Supabase Auth; there is no password.
Business information you provide: shop name, address, phone, website, owner name, brand assets.
Catalog content: services, packages, finishes, labor rates, pricing rules.
Customer and quote records you create within your workspace.
Conversations with Ember, the shop’s AI assistant, on the web and in the phone app: what you type, the text of what you say, and Ember’s replies and actions (see Section 5, Assistant conversation records).
Billing: payment method tokenized by Stripe; we never see or store full card numbers.
Missed-call text agreement: before a shop can turn on missed-call texts, its owner ticks a statement of the shop’s duties for those texts. We record who ticked it and when, and the record stays with the shop even if that person’s account is later deleted.
Square, if your shop connects it: a shop can choose to connect its own Square account in Settings. We keep that account’s Square keys, encrypted, with its Square merchant ID and the access the shop granted. With them we read the shop’s completed Square payments taken since it connected (the amount, the shop’s note and order reference, any refund, and the buyer’s email when Square has it) and its Square locations; its Square bookings from a day ago to 60 days ahead, with each booking’s customer name, email and phone, unless the shop turns bookings off; and, only when the shop asks in Import data, its Square customers (name, company, email, phone, address, note) and its Square catalog (items, prices, durations, descriptions, categories). Every 15 minutes we read the last 2 days of payments and the bookings, once a day the last 30 days of payments, and the shop can also sync at any time.

From customers (people using a shop’s embed or share link)

Name, email, and phone you type into a lead-capture form.
Mobile number and SMS consent status, when you ask a shop to text you your quote.
Vehicle selections, reference photos uploaded, and finishes chosen during a quote flow.
Conversation content with the AI assistant (your typed prompts, the text of spoken requests, and the assistant’s replies).
Voicemail: when a shop’s AI phone line can’t take your call because the shop’s voice minutes are used up, you are asked to leave a message after the tone. If you do, your message is recorded (up to 2 minutes) and Twilio turns it into text. The recording and the text go to the shop: its owners and managers can play the recording and read the text in Calls, and so can DETAILFORGE admins. The recording is kept at Twilio and the text is kept with the shop’s call record, until they are deleted. This is the only time we keep a recording of your voice.
Missed-call texts: when a shop has turned on missed-call texts and you call its own DETAILFORGE texting number and nobody answers, we keep a record of that call for the shop: your phone number (unless it was hidden or not a number), Twilio’s ID for the call, how the call ended, whether we texted you or why not, and when. If you left “OK to text me” unticked on the shop’s form, you get no text unless you agreed to texts later. If we text you, the text and your number also go into the shop’s Messages, like any text from the shop, and your reply goes to the shop. See Section 7 and our text messaging page.
Square: when a shop has connected Square and you book with it in Square, your name, email and phone from that booking come into the shop’s DETAILFORGE calendar. When you pay the shop through Square, we read that payment (including your email, when Square has it) to record it on your job. If you pay with a Square payment link from the shop, or choose Pay with Square on your invoice, you pay on Square’s own page: your card details go to Square and never pass through DETAILFORGE.

From the DETAILFORGE phone app

The phone app is for a shop’s own people. Each permission below is optional: the app asks before it uses one, and you can turn any of them off at any time in your phone’s settings.

Location: your device’s precise location, while the app is in use, to show where you are on the map of your stops. When you tap On My Way, the app sends your location to us to work out an arrival time. When On My Way is sent for your stop, by you or by a manager, and your shop uses tracking links, the app also sends your position while that trip is open, so the customer can follow your drive on the tracking link sent to them by text or email. On Android, the app keeps sending your position during the open trip while you use other apps or the screen is off, through a service that shows a notification for as long as it runs; the app does not ask to use your location all the time. On iPhone, if you also allow location “Always”, the tracking link keeps updating when the app is in the background or the screen is off; if you don’t, positions are sent only while the app is open. Sharing stops when you mark the stop arrived, when the visit is finished or canceled, when you or a manager stop sharing, when you start your next trip, or two hours after it started. The stored position is cleared when sharing stops, and the ended trip is deleted after 30 days. We don’t receive your location outside the On My Way tap and an open trip.
Camera and photos: only when you choose to take or attach a photo, such as before, during and after photos of a job, reference photos, a photo in a message to a customer, a team member’s photo, or your shop logo. Only the photos you take or pick are uploaded; the app does not read the rest of your photo library.
Microphone: only while you talk to the voice assistant, Ember, meaning while you hold the talk button, while hands-free is turned on, or while you dictate into Ember’s message box. The audio is sent to us and on to OpenAI to be transcribed, and OpenAI also turns the assistant’s replies into speech. We keep the text of what you said as part of the assistant conversation, not the recording.
Push notifications: if you allow them, the app gives us a push token for your device. We send notifications about your shop’s work (the title, text, and what the app needs to open the right screen) through Expo’s push service, which hands them to Apple or Google to deliver. You can turn them off for a device in the app’s notification settings or in your phone’s settings.
Maps: maps in the app are Google Maps. Drive times and routes are worked out with Google from stop addresses and, during On My Way, your shared position.
Card payments: a shop charges its customers on a Stripe card reader that connects to Stripe over the internet. Card details go from the reader to Stripe and never pass through the app or our servers.
The phone app contains no advertising or analytics SDKs, and it does not track you across other companies’ apps or websites.

Automatically

Authentication cookies (Supabase) and an “active workspace” cookie (df_active_tenant) that tracks which shop your URL is scoped to.
IP address and user-agent for every request, used for rate limiting, abuse detection, and security.
Powered by DETAILFORGE link: when you follow the Powered by DETAILFORGE link on a shop’s page, the link names that shop and the kind of page (for example booking or quote), so we can tell which shop sent you. We don’t add it to an account you create. As part of the page address, it shows up in the page visit counts our hosting provider (Vercel Analytics) keeps for us.
Activity and approximate location: while you are signed in and have DETAILFORGE open, in a visible browser tab or with the phone app on screen, it tells us about once a minute that you are there. We keep the time you were last active and the approximate city, region and country of your connection, worked out from your IP address by our hosting provider (Vercel), with a map point at the centre of that city. This is never your device’s GPS. We keep one record per person: each update replaces the last, so there is no history. Our staff see it, with your name, email and shop, in our admin tools, and your shop’s Team page shows when each teammate was last active. It is not collected for customers or for visitors who aren’t signed in.
Performance and error telemetry (page load timings, JavaScript exceptions) via Sentry, anonymous unless an error captures identifying context.

3. How we use your information

We process personal information for the following purposes, under the legal bases noted (relevant for visitors in the European Economic Area, United Kingdom, and Switzerland):

Provide the Service: render configurators, compute quotes, route AI assistant traffic, send transactional emails. Legal basis: performance of a contract.
Bill paying shops via Stripe. Legal basis: performance of a contract.
Connect a shop’s Square account, only when the shop chooses to: record a Square payment on the job whose number the shop wrote in the payment’s note or order, never matched by a name or an amount; keep the shop’s Square bookings on its calendar, linking a booking to one of the shop’s existing customers only when the email or US phone number is exactly the same, and otherwise putting Square’s name and contact in the appointment’s notes (a booking never makes a new customer); make Square payment links for the shop’s jobs; and, when the shop asks, bring its Square customers and catalog into Import data, where nothing is added until the shop chooses to add it. Ember reads the catalog, through our AI model provider, to set up the shop’s services; the customers are not sent to it. Legal basis: performance of a contract.
Work out a US shop’s local sales tax rate from the shop’s own address. Legal basis: performance of a contract.
Improve product quality: aggregate usage metrics without individual identification. Legal basis: legitimate interest.
Fix, train and improve the AI assistant: from 2026-10-22, reviewing records of individual assistant conversations to find answers that went wrong and correct them, and from 2026-11-13, also using them to train, test and improve the DETAILFORGE assistant, as described in Section 5. Legal basis: legitimate interest.
Know which shops are active and support them: our team sees when each signed-in person last used DETAILFORGE and the city of their connection. Legal basis: legitimate interest.
Security, fraud prevention, and abuse detection: rate limit, log suspicious activity, investigate incidents. Legal basis: legitimate interest.
Legal compliance: tax records, statutory retention, response to lawful requests. Legal basis: legal obligation.
Communications with shop accounts regarding billing, service changes, or security. Legal basis: legitimate interest / performance of a contract.

We do not sell personal information, we do not engage in cross-context behavioral advertising, and we do not use personal information for any purpose materially different from the ones above without further notice.

4. How we share information

We share personal information only with the categories below, and only to the extent necessary for the listed purpose.

Subprocessors

Third parties that process personal information on our behalf under contract:

Supabase (US): database, authentication, file storage.
Vercel (US): application hosting and edge networking.
Cloudflare R2 (US): vehicle assets, customer-uploaded reference photos, job and message photos (including those taken in the phone app), AI-generated images.
Stripe (US): payment processing for paid plans, and for the payments a shop takes from its customers, online and on Stripe card readers.
Resend (US): email delivery: our own emails (sign-in codes, invites, billing), a shop’s emails to its customers about their work (quotes, receipts, invoices, reminders, job updates), and a shop’s campaigns and other promotional emails, which go out from a separate marketing sender.
Twilio (US): text messages between a shop and its customers, such as quote, invoice and document links, booking confirmations and reminders, On My Way and tracking-link texts, the shop’s automated follow-ups and campaigns, the one text a shop can send back to a caller it missed, and two-way texting in which customers reply to the shop. Also phone calls to a shop’s DETAILFORGE number, when the shop has one, and the voicemail a caller leaves when the shop’s AI phone line can’t take the call: Twilio records it, turns it into text, and keeps the recording (see Section 2).
Sentry (US): error monitoring, when configured for the deployment.
OpenAI (US): the AI assistant for shop and customer conversations, including spoken requests to the voice assistant, AI-generated images of the configured build, and the automated quality check on each image.
Upstash (US): Redis for distributed rate limiting, when configured.
Expo (US): push notification delivery to the phone app, using your device’s push token.
Google (US): Google Maps in the phone app, and drive times and routes between stops, including from a technician’s shared position during On My Way.
OpenStreetMap Nominatim (UK): address suggestions while an address is typed, and finding where service addresses are for the map of a technician’s stops and a shop’s service area. Lookups come from our servers and carry only the address text, the shop’s country, and an area around the shop, never a name, email, or phone number.
Zip.Tax (US): the local sales tax rate for a US shop’s own address, for shops outside Washington and California. We send only the shop’s street, city, state and ZIP, at sign-up, when the shop saves a new address, and once a month. Never a customer’s address, name, email or phone.
Square (US): only for a shop that chooses to connect its own Square account. We read the shop’s payments, bookings and locations and, when the shop asks, its customers and catalog, and we ask Square to make payment links for the shop’s jobs. A payment link carries the job number and the amount, never the customer’s name, email or phone. We never write bookings or customers to Square. Square works for the shop under the shop’s own agreement with Square (see Section 2).

Other recipients

Other shops or customers: only when a shop chooses to share a quote with a customer via a share link, invites a teammate to its workspace, or sends a customer a tracking link by text or email with On My Way, which shows that customer the technician’s position and arrival time until sharing stops.
Law enforcement or regulators: when we’re legally required to disclose information, and only to the extent required.
Successor entities: in connection with a merger, acquisition, or sale of assets, subject to standard confidentiality and notification protections.
Professional advisors: accountants, attorneys, auditors who are themselves under a duty of confidentiality.

Access by DETAILFORGE staff

DETAILFORGE staff may access a shop’s account and its content to provide support the shop asks for, fix problems, and keep the Service secure. Access is limited to those purposes. To work inside a shop, a staff member joins its team as a manager for a length they choose (from an hour up to a month, or until they leave). When that time is up, their access ends and they are removed from the team. One exception: when our founder joins a shop this way, the website shows them the shop with an owner’s access for the visit. That includes the owner-only settings, such as billing, setting up payments, the websites that can show the chat, and closing the shop. Their team record stays a manager, so they are never treated as the shop’s owner for anything else, such as who gets the shop’s email. Each join, change and leave is recorded in the shop’s Activity log, which the shop’s owners and managers can see in Settings.

5. AI processing

When you use the AI assistant or AI image-generation features, the relevant input, meaning your typed prompt or the audio of a spoken request, current selections, vehicle metadata, and any reference photos you upload, is sent to the model provider for processing.

OpenAI is the only AI model provider we use. Per OpenAI’s current API terms, inputs are not retained to train its general-purpose models.
AI outputs are best-effort. They’re intended as preview and pricing guidance; the shop’s final pricing and work scope is what governs the engagement.
We do not make decisions about you using solely automated processing that produces legal or similarly significant effects on you.

Assistant conversation records

From 2026-10-22, we keep a record of each conversation with the AI assistant, for every shop: Ember in the web app and the phone app, a shop’s website chat and car builder chat, and calls answered by a shop’s AI phone line. Until then we keep these records only for our own demonstration shop.

What a record holds: what was typed or said (spoken words as text, never the audio; a voicemail is not part of these records, see Section 2), the assistant’s reply, the steps it took to answer, and whether the answer worked. A record of Ember is tied to the shop and to the staff member who used it; it also holds what was on screen (the page, and the job or customer open) and what each step found, which can include customer names and details Ember looked up. A record of a customer chat or call is tied to the shop and to a visitor or call ID, never a phone number or email; email addresses, phone numbers, vehicle identification numbers and payment details are removed before it is saved, and names and street addresses can remain.
Why: to find answers that went wrong and fix the assistant and, from 2026-11-13, to train, test and improve the DETAILFORGE assistant. Records are never sold, never used for advertising, and never sent to OpenAI to train its models.
Who can read them: DetailForge staff working on the assistant. They are not shown to other shops.
How long: from 2026-11-13, up to 2 years, then deleted automatically; before that date, 90 days. We may delete them sooner.
When an account or customer is deleted: deleting a shop deletes its records at once (our own test shops excepted). Deleting your account deletes the shops you are the only owner of, with their records; in a shop that stays, your Ember records stay until they are deleted as above. Records are not linked to customer records, so deleting a customer record does not remove that customer’s conversations.
How you are told: the customer chats say so under the message box, and the shop’s AI phone line says the call is transcribed when it answers.

6. Cookies and similar technologies

We use a small number of strictly necessary cookies. We do not use tracking, advertising, or analytics cookies.

Supabase auth cookies: keep you signed in across requests.
df_active_tenant: remembers which shop URL you’re currently working in.

You can control cookies via your browser settings. Disabling our essential cookies will sign you out and break shop-scoped routes.

7. Text messaging (SMS) program

DETAILFORGE sends text messages on behalf of the shops that use it, to those shops’ customers. This section is our messaging program disclosure.

Program: a shop uses DETAILFORGE to text you about the work you asked it for, such as links to your quotes, invoices, waivers, change orders and other documents, booking confirmations and reminders, deposit and pickup notices, waitlist openings, On My Way texts and tracking links, messages the shop’s staff write to you, and replies when you text the shop. If the shop turns it on, it also sends one text, in the shop’s words, when you call the shop’s own DETAILFORGE texting number and nobody answers: never to a number that opted out of that shop’s or all DETAILFORGE texts, only between 8am and 9pm on the shop’s clock, no more than once every 4 hours, and not if you texted the shop in the last 4 hours. Calling the shop is not agreeing to any other texts. DETAILFORGE sends a shop’s campaign texts, and its automated follow-ups that count as promotional (review requests, rebook reminders, aftercare texts, quote follow-ups, and any step the shop marks as promotional), only to customers who have separately agreed to receive marketing texts (see below), and only once our carrier registration covers marketing texts. The shop decides which texts to send and when, and is responsible for having your consent to text you. DETAILFORGE does not send marketing texts of its own to a shop’s customers.
How you opt in: you agree with the shop that it may text you about your quote, booking or job. Every public form a shop uses on DETAILFORGE (quote request, car builder, booking and chat booking) has an optional “OK to text me” box that is never ticked for you. Sending a form without ticking it is not agreeing to texts. If you are new to the shop and leave it unticked, the shop does not text you until you agree: by ticking the box on a later form, by texting START or texting the shop’s number, or by telling the shop in person or by phone, which the shop then records. That includes the one text a shop can send back to a missed call. If you give your number to a shop another way, such as in person or over the phone, the shop is responsible for getting your agreement, and DETAILFORGE’s send-quote-by-text step asks the shop to confirm that you agreed. Marketing texts need a separate agreement, and new agreements can be given only by you: by replying START or, once our carrier registration covers marketing texts, by ticking the unchecked box on the shop’s booking form or quote page. Agreeing to marketing texts is never a condition of a booking or a quote. Agreeing to texts about your quote or job is not agreeing to marketing texts. We never buy or rent phone numbers, and a phone number a shop brings in from its own customer list carries no agreement to marketing texts.
Message frequency: message frequency varies. Texts about your quotes, bookings and jobs depend on your interaction with the shop. Marketing texts, if you agreed to them, depend on how often the shop sends campaigns and promotional follow-ups.
Cost: message and data rates may apply, depending on your mobile carrier and plan.
Help and opt out: reply HELP to any message for help, or STOP at any time to cancel (UNSUBSCRIBE, CANCEL, END and QUIT also work, sent as the whole message). After you reply STOP you will receive one confirmation. A STOP sent to the shared DETAILFORGE number applies to your number across all shops; a STOP sent to a shop’s own number applies to that shop. Within that scope you will receive no further messages, including marketing texts, and any agreement to marketing texts is withdrawn. The opt-out is recorded immediately. You can also ask the shop to stop texting you, and it can record your opt-out. Reply START to receive texts again. Replying START or UNSTOP, even if you had not opted out, counts as agreeing to texts, including marketing texts: sent to the shared DETAILFORGE number, it covers every shop that has your number; sent to a shop’s own number, it covers that shop.
What we collect: the mobile number you give the shop, your consent status for texts about your work and for marketing texts (including when and how you gave or withdrew it), the texts exchanged between you and the shop, and any STOP / START / HELP replies. For missed-call texts, also the record of the call described in Section 2.
How we use it: to send the texts the shop sends you through DETAILFORGE; to deliver your replies to the shop; to show the conversation to the shop’s staff and, when they ask, to the shop’s AI assistant Ember, which processes it with our AI model provider (see Section 5); to check your consent before each campaign text or automated promotional follow-up; and to honor opt-outs.
Sharing: your mobile number is shared with our SMS carrier (Twilio, US) only to deliver the message. We do not sell or share mobile phone numbers or SMS consent information with third parties or affiliates for their marketing or promotional purposes.

8. Data retention

Active accounts: data is retained for as long as the account is active.
Closed accounts: shop content is removed within 30 days of account deletion, except where retention is required by tax, audit, or legal rules.
Customer (lead) records inside a shop: retained as part of the shop’s own data. Deletion of an individual customer record by the shop propagates immediately to our systems, except the missed-call text records described next.
Billing records: retained for 7 years for tax and audit compliance.
Backups: encrypted snapshots may persist for up to 90 days beyond a primary deletion, then are purged on schedule.
Security logs: IP addresses and request metadata retained 90 days for abuse detection, then deleted or aggregated.
Missed-call text records: the number that called, when, and whether a text went, deleted after 90 days. Deleting a customer record does not remove them.
Assistant conversation records: from 2026-11-13, up to 2 years, then deleted automatically; before that date, 90 days. We may delete them sooner. Deleting a customer record does not remove them (see Section 5).
Square: a shop can disconnect Square in Settings at any time. We then stop reading from Square and ask Square to cancel DETAILFORGE’s access to the account. What was already brought in (payments recorded on jobs, appointments from Square bookings, and customers and services the shop added from Import data) stays as part of the shop’s data until the shop deletes it or its account is deleted. Turning Square bookings off stops us reading them; appointments already brought in stay.
Last-seen time and connection city: one record per person, replaced each time you use DETAILFORGE, deleted with your account.

9. Your privacy rights

Rights available to all users (where applicable law applies)

Access: sign in to view everything we have associated with your account.
Correction: edit your name and phone at any time from Account on the web or More → Settings → Profile in the phone app, your shop’s business profile from the shop’s Settings, and its catalog from Catalog.
Deletion: delete your account from Account on the web or More → Settings → Profile → Delete account in the phone app. This deletes your sign-in and every shop you are the only owner of; shops you share with another owner stay. A shop’s owner can also archive or delete just that shop on the web from Settings → Close or delete shop. We’ll remove your content within 30 days, subject to the retention rules above. The steps, and what is kept, are on our account deletion page, which needs no sign-in.
Portability: a shop’s owners and managers can export customer lists, jobs, payments and revenue as CSV files from Reports, on the web or in the phone app.
Withdraw consent: where we rely on consent, you can withdraw it at any time without affecting prior processing.

Additional rights under GDPR / UK GDPR

If you’re in the EEA, United Kingdom, or Switzerland, you also have the right to:

Restrict or object to processing where we rely on legitimate interest.
Lodge a complaint with your local data protection supervisory authority.

Additional rights under CCPA / CPRA (California residents)

California residents have the right to:

Know: request a copy of the personal information we’ve collected about you and the categories we’ve disclosed.
Delete: request deletion of personal information, subject to legal exemptions.
Correct: request correction of inaccurate personal information.
Limit use of sensitive personal information: to the extent we collect any (we do not currently use sensitive personal information for inferring characteristics).
Opt out of sale or sharing: we do not sell or share personal information for cross-context behavioral advertising, so there is nothing to opt out of.
Non-discrimination: we will not deny service, charge different prices, or provide a different level of service because you exercised any right above.

To exercise any right, email hello@glodusk.com. We’ll respond within the timeframe required by applicable law (45 days for most CCPA requests, one month for most GDPR requests). We may need to verify your identity before fulfilling a request.

10. International data transfers

Our primary processing happens in the United States. Our subprocessors may operate globally. Where we transfer personal information out of the EEA, United Kingdom, or Switzerland to a country that does not have an adequacy decision, we rely on the European Commission’s Standard Contractual Clauses (and the UK International Data Transfer Addendum where relevant), or another lawful transfer mechanism, to protect your information.

11. Data security

We use TLS encryption in transit, encrypted database storage at rest, signed webhooks, per-shop row-level security in Postgres, and encrypted secrets management. Access to production systems is limited to personnel with a need-to-know basis and protected by strong authentication. We don’t currently claim a specific attestation such as SOC 2; work toward formal certification is part of the Enterprise track.

12. Data breach notification

If we become aware of a personal data breach likely to result in a risk to your rights and freedoms, we’ll notify the relevant supervisory authority and affected users without undue delay, in line with applicable law (within 72 hours under GDPR where required).

13. Children’s privacy

DETAILFORGE is a business-to-business product intended for commercial users. We do not knowingly collect personal information from anyone under the age of 16. If you believe a child’s information has been provided to us, email hello@glodusk.com and we’ll delete it.

14. Changes to this policy

We’ll update this Policy when the service changes, the law changes, or our subprocessor list changes. We announce material changes inside DetailForge at least 14 days before they take effect: signed-in users see a banner and can read and agree to the updated version right away, and from the day it takes effect they are asked to agree to it in a pop-up before they keep using DetailForge. The “Last updated” date at the top of this page reflects the most recent revision.

15. Contact us

Privacy questions, access or deletion requests, or anything else related to this Policy: hello@glodusk.com. For general support, hello@glodusk.com.