DASHE · PRIVACY

Privacy policy

Effective date: November 6, 2026
Contact details updated: October 26, 2026

This policy explains how Dashe ("we", "us") handles information when you visit getdashe.com, use a Dashe account, enable SEO and publishing, or interact with a business through Dashe's chat, calls, mobile inbox or appointment booking.

When a business uses Dashe on its own website, that business controls its customer relationships, team access and use of the information it receives. Its own privacy notice also applies. Contact that business about information you give it, or contact Dashe using the details below if you need help directing a request.

Information we handle

• Accounts and workspaces: names, email addresses, password hashes, team roles, workspace settings, subscriptions and account-security records.
• Website conversations: messages and contact details you provide; the page, product, referral or campaign context shared with the widget; conversation activity; and information the website supplies to identify a visitor. Staff can see source labels for contact information.
• Appointments: customer name and email, optional phone and notes, selected product/page, assigned teammate, appointment time, location and booking or cancellation status.
• Business content and media: website and knowledge content, team profile images, uploaded video clips and links your business adds to the widget. Clips selected for visitors can be viewed and shared through their public media links; they are not private call recordings.
• Optional voice, video and screen sharing: the media you choose to share, transmitted to the other call participants. Dashe's current calling implementation does not record calls.
• Devices and technical information: session and browser identifiers, optional notification subscriptions, device/app information and service/security logs. Hosting and network providers receive information needed to deliver requests, which can include IP addresses.

We use this information to provide conversations and appointments, route work to a business's team, deliver notifications and account messages, manage subscriptions, protect the service and respond to support requests.

Optional SEO and publishing

SEO automation is optional and starts disabled. An authorized workspace owner or administrator selects the website, confirms business facts, chooses the work and spending limits, and enables automation. For WordPress websites, a separate WordPress administrator grant is required for editing or publication; installing the chat script does not grant that access. The WordPress administrator can revoke access locally. Websites hosted by Dashe may instead connect the built-in blog publisher. Author names, titles, biographies and optional photo URLs guide drafting; on the built-in blog, these details become public with published articles. Drafts remain private, and authorized administrators can withdraw published articles. Changing an author profile affects future publications; existing publications retain their saved byline.

The WordPress SEO connection also reports limited host diagnostics: PHP and WordPress versions, operating-system family, session-upload status, and cURL Brotli support/version. Dashe stores these fields and check timestamps to assess its runtime requirements and pause website writes when requirements are unmet or unverified. These diagnostics are not sent to writing or ranking providers. The connector does not send phpinfo, environment secrets or the full server configuration.

When enabled, Dashe stores public page content and metadata, confirmed business facts, selected public references, article drafts, publication schedules, selected author/category identifiers and names, and before/after change records. The configured writing provider, OpenAI or Anthropic, receives that editorial context. This workflow does not use private customer chats, sales records or calendar events. DataForSEO receives the selected search queries, prompts, domains and search markets to supply search, backlink and sampled AI observations.

Google Search Console is a separate, optional read-only authorization. We read verified property identifiers and access levels, then query the selected property's search dates, queries, pages, countries, devices, clicks, impressions, click-through rates and average positions. We store the returned performance observations and encrypted access/refresh tokens. Search Console data is used to display your performance; the current editorial workflow does not send those Google responses to writing providers.

Disconnecting Search Console in SEO settings deletes its active connection and stored tokens. You can also revoke its Google grant through your Google Account connections. Disconnecting WordPress stops new authorized requests, but a write already submitted may finish and need receipt reconciliation. Published articles and retained change/performance records are preserved; disconnecting does not delete website content. Contact us for deletion of retained SEO data. Backups follow the hosting service's retention lifecycle.

Google Calendar connections

Connecting Google Calendar is optional. Each teammate chooses their own Google account and grants permission through Google's consent screen. Dashe does not ask for or store your Google password.

• Calendar list: we read calendar identifiers, names, primary-calendar status and access roles so you can select calendars and a writable booking destination. A primary calendar identifier can include your email address.
• Availability: we request busy intervals from the calendars you select. When rescheduling, we may read event identifiers, start/end times, cancellation and availability status to exclude the appointment being moved without overlooking another conflict. These checks do not request the titles, descriptions, guests or locations of your other events. Responses are processed for availability and are not saved as an imported event history.
• Appointment events: we create, update and cancel events for appointments booked through Dashe on your selected destination calendar. An event can include the customer's name, email, optional phone and notes, product/page, appointment time and location. We may retrieve a Dashe-created event by its identifier to reconcile a delivery retry. Calendar sharing settings in Google determine who else can see events on that calendar.
• Connection storage: we retain your account/calendar identifiers, selected calendars, provider event identifiers and encrypted access/refresh tokens to keep the connection working when you are not signed in. Tokens are not sent to website visitors.

Visitors receive available booking times and their own booking details. They do not receive your calendar list, OAuth tokens or private event titles. Workspace teammates see the native appointments their role permits; each teammate manages their own calendar connection.

Google Calendar data is used to provide the availability and appointment features described here. It is not sold, used for advertising or credit decisions, sent to the chat AI provider, or used to train generalized AI models. Our use and transfer of Google API data follows the Google API Services User Data Policy, including its Limited Use requirements.

Human access to Google-derived data is limited to your affirmative agreement to view specific data, security investigation, legal requirements, or data aggregated for internal operations in accordance with applicable privacy laws. Service providers may process it only as needed for these calendar features and the permitted purposes in Google's policy. Any transfer connected with a business sale is subject to that policy, including prior user consent where it requires it.

Showroom customers, projects and selections

A workspace administrator can import public product information from a showroom website, with optional weekly refresh. Dashe stores product names, descriptions, identifiers, source URLs, published prices and availability for staff to review. Imports do not sign in to the website or access a private supplier account. Staff can use these products to generate quote PDFs containing customer details, line items, prices, taxes and terms. Saved PDF versions are retained with the customer project; refreshing products does not rewrite an issued quote. These imports and PDFs are not sent to an AI model.

When a business enables Sales, staff can keep customer contact details, project notes, assignments, next steps, quotes, photos, forwarded emails and product selections. Automatic capture of explicit booking/contact details is a separate business setting; chat capture also respects the installation's customer-recognition setting. Records supplied through a browser, an email or a shared link are not treated as verified identity. Staff confirm links between chats, visits and projects.

Staff approve follow-up emails to the recorded customer address after recording permission. Resend processes the message, delivery events and replies, including forwarded quote emails where configured. Customer responses and opt-outs stop pending project follow-ups. Appointment confirmations and optional reminders are separate service messages; the private appointment link lets the customer turn reminders off. We retain a hashed email suppression record to respect an opt-out even if the customer record is later removed.

Product selections are private until a salesperson publishes an expiring link. Anyone holding that link can view the selected products, respond and forward the link. It excludes customer contact details and internal project notes. Staff can revoke a link or publish a replacement. Uploaded files are stored in the application database and do not require access to a supplier catalogue; image uploads are resized and have metadata removed. Quote text extraction assists staff entry and is not sent to an AI model.

Sales records have separate retention from chat history. Administrators review inactive records and can export or permanently delete a customer's sales records, which revokes selection links and cancels queued follow-ups. This does not delete separately retained chat transcripts, browser profiles, appointment records, downloaded files or emails already delivered. Ask the business to handle these additional records where needed. Backup copies follow the hosting service's retention lifecycle.

Other providers and sharing

Dashe runs on Render infrastructure. Google Calendar, or Microsoft Calendar when configured and connected, handles the calendar actions you authorize. Resend delivers account, booking and business-notification emails. Appointment emails contain the native booking details and may be copied to the assigned teammate; private external-calendar events are not included.

Whop processes subscription and checkout information and supplies the marketing measurement script on getdashe.com. Google Calendar data is not passed to that marketing script. Our public website also loads fonts from Google Fonts.

If AI replies are configured and enabled, relevant recent conversation messages and the business's configured information may be sent to Anthropic to generate a reply. Google Calendar connections do not feed calendar data into that process. If mobile notifications are enabled, delivery uses the applicable browser push service or Expo, Apple and Google; notification payloads use routing identifiers and generic alerts rather than customer message text. Calls may use network discovery and configured relay services to connect participants. If a business embeds a video from another provider, such as Loom, that provider receives requests needed to show the video and its own privacy policy applies.

Information can also be disclosed when necessary to investigate abuse, protect users or comply with applicable law. Google-derived data remains subject to the more specific limits above. Providers may process information outside your country, including in the United States.

Wix chat connection

If a website uses the Dashe Wix app, Wix stores its public widget identifier, enabled state and optional returning-browser setting. When a site owner or an authorized Wix dashboard contributor opens the app settings, Dashe verifies the signed Wix installation and dashboard permission with Wix and uses a short-lived app access token to read or change that installation's embedded script. These credentials are used for the request and are not stored in Dashe's application database or browser storage. The app requests permission to manage its embedded script. Wix also includes a required permission to read basic site and business details and the site owner's login email; this integration does not call those information APIs. It does not request Wix contacts, orders, page editing or blog publishing access.

The chat script is categorized as functional in Wix's consent controls. The website operator must configure and test their consent banner. Chat sends the page context and visitor information described above. Returning-browser recognition is off by default. Disabling or removing the Wix app prevents future script loads subject to Wix publishing and caching behavior; reload a page after withdrawing consent to stop an already-running chat. Removal does not cancel a Dashe plan or delete conversations and profiles already held by Dashe; contact the business about those records.

Cookies and browser storage

Dashe uses session cookies to sign in staff, and browser storage for interface preferences and conversation continuity. Where returning-visitor recognition is enabled, a random identifier links visits within the same business and website origin. It does not recognize a person across devices or unrelated websites. Clearing site storage resets that browser's recognition; workspace administrators can forget a stored customer profile. Website operators can disable the recognition feature.

The public marketing site's Whop measurement may use its own identifiers. Browser privacy controls can limit cookies and storage, although some features may stop working.

Retention, disconnection and deletion

Conversation cleanup uses the configured retention period, normally 90 days after inactivity. Non-engaged browsing records normally expire after two inactive days. Remembered profiles with contact information expire after 365 inactive days, and anonymous profiles after two; profile retention is separate from transcript retention.

Calendar connection metadata and tokens remain while the connection exists. To disconnect in Dashe, finish or cancel upcoming appointments tied to that connection and synchronize pending changes, then use Calendar → My availability → Disconnect. Successful disconnection deletes that connection and its stored tokens from the active database. You can revoke Google's access grant at any time in your Google Account connections. Revoking access stops future authorized Google API access; it does not itself erase records already stored in Dashe or appointments already on your calendar.

Uploaded video clips remain until an authorized workspace administrator removes them; deleting a clip from Dashe cannot recall copies already downloaded by visitors. Native appointment records do not currently expire automatically with chat history, and cancelling an appointment does not delete its record. For deletion of stored appointments, account information or other retained data, contact the relevant business or the privacy contact below. We may need to verify the requester's identity and authority. Information required for legal, security or accounting purposes may need to be retained; backup copies follow the hosting service's retention lifecycle.

Protecting information

Dashe uses HTTPS for the website and external calendar API requests, workspace role checks, protected sessions and encrypted calendar OAuth tokens. Access is limited by workspace membership and role. These controls reduce risk but cannot guarantee that every system or transmission will be free of security incidents.

Your questions and choices

You can choose not to connect a calendar, revoke provider access, decline optional call or notification permissions, and contact us to request access, correction or deletion of information. For data a customer business collects through its Dashe installation, contact that business first. We will help identify the appropriate contact where needed.

Privacy contact: privacy@getdashe.com.

We will update this policy when our practices change and provide additional notice or request renewed consent when necessary for a change in how Google data is used.