Privacy Policy

DialogMaker is operated by DialogMaker. This draft uses "DialogMaker", "we", "us", and "our" to refer to that operator. It should be reviewed before publication with final company details and jurisdiction.

1. What this policy covers

DialogMaker provides software for creating conversational forms, collecting visitor responses, saving contact history, and helping teams follow up. This policy explains how we handle personal data from account users, workspace members, site visitors, people who submit a DialogMaker workflow, and people who contact us for support or sales.

Customers who publish workflows decide what their workflows ask, where they are embedded, who receives submissions, and how the resulting data is used. Those customers are responsible for giving their own visitors any privacy notice, consent request, or legal basis required for their use case.

2. Information we collect

• Account and workspace data, such as names, email addresses, passwords or authentication identifiers, roles, workspace settings, notification preferences, and usage limits.
• Billing data, such as plan, subscription status, invoices, tax or billing details, and payment events. Card details are handled by Stripe, not stored directly by DialogMaker.
• Workflow and form content created by customers, including questions, branching rules, embeds, templates, branding settings, and internal notes.
• Visitor submissions and contact data collected through customer workflows, such as answers, contact fields, files, tags, activity history, timestamps, and technical delivery metadata.
• Integration data, including provider names, connection settings, tokens, API keys, calendar identifiers, event configuration, and data sent to or received from connected services.
• Website, device, log, cookie, and analytics data, such as IP address, browser, pages viewed, referrer, approximate location, session events, error logs, and security events.
• Support and communications data, including messages, attachments, feedback, call notes, and other information you provide when contacting us.

3. How we use information

We use personal data to create and secure accounts, provide workspaces, publish workflows, process submissions, send notifications, provide support, measure usage, process billing through Stripe, improve the product, prevent abuse, comply with law, and enforce our agreements.

We do not sell workflow submissions or visitor contact data. We do not use customer workflow submissions for advertising.

4. Customer data and visitor submissions

When a visitor submits information through a customer workflow, DialogMaker generally processes that information on behalf of the customer who created the workflow. The customer controls the workflow's questions, purpose, recipients, integrations, and retention choices.

If your privacy request is about answers you submitted to a DialogMaker workflow, contact the business or person who published that workflow first. We may help them respond when our contract or applicable law requires it.

5. BYOK integrations and third-party services

DialogMaker is designed for customer-controlled integrations. When you connect a third-party service, you are responsible for having permission to use that service and for choosing what workflow data is sent to it. Credentials, tokens, or API keys you provide are used to operate the integration you enable and should be stored in encrypted form where the product supports credential storage.

Data sent to services such as calendar tools, scheduling products, email systems, CRMs, analytics tools, or webhooks is governed by your configuration and by those providers' own terms and privacy policies.

6. Google Calendar OAuth, if enabled

If Google Calendar OAuth is enabled and you connect a Google account, DialogMaker may request access needed to list writable calendars, check availability, and create booking events configured by your workflows. We use Google Calendar data only to provide the calendar functionality you enable.

DialogMaker's use and transfer of information received from Google APIs will follow the Google API Services User Data Policy, including the Limited Use requirements where applicable.

7. Cookies and analytics

We may use cookies, local storage, session storage, and similar technologies to keep users signed in, remember preferences, protect the service, measure performance, understand product usage, and troubleshoot errors. Customer workflows may also use browser storage to remember a visitor or resume an experience when the workflow owner enables that behavior.

You can control cookies through your browser settings, but some account, security, and workflow features may not work without them.

8. Sharing and subprocessors

We share information with service providers that help us operate DialogMaker, such as hosting, database, storage, email delivery, monitoring, analytics, customer support, security, and payment processing providers. Stripe processes payments and related billing information.

We may also disclose information when required by law, to protect the rights and safety of users or the public, to prevent abuse, in connection with a business transaction, or with your direction through integrations and workflow configuration.

9. Retention and deletion

We keep account and workspace data while the account is active and as long as needed to provide the service, comply with law, resolve disputes, enforce agreements, maintain security, and preserve billing records. Customer workflow submissions are retained according to workspace settings, plan limits, customer instructions, and operational backup cycles.

When an account, workspace, workflow, or submission is deleted, active copies are deleted or anonymized within a reasonable period unless we must retain them for legal, security, billing, abuse-prevention, or dispute reasons. Residual copies may remain in backups until those backups expire.

10. Security

We use administrative, technical, and organizational measures intended to protect personal data, including access controls, encryption where appropriate, monitoring, and backups. No internet service can guarantee perfect security, and customers are responsible for account access, passwords, member permissions, workflow configuration, and connected third-party accounts.

11. International transfers

DialogMaker and its service providers may process information in countries other than where you live. Where required, we use appropriate safeguards for international transfers, such as contractual protections or other mechanisms recognized by applicable law.

12. Your rights and choices

Depending on where you live, you may have rights to access, correct, delete, export, restrict, or object to certain processing of your personal data, and to withdraw consent where processing is based on consent. To make a request, contact privacy@dialogmaker.com.

If your request concerns data collected by a customer's workflow, please contact that customer first because they usually decide how that data is handled.

13. Children's data

DialogMaker is not intended for children. Customers must not use workflows to knowingly collect personal data from children unless they have the permissions and notices required by applicable law.

14. Changes to this policy

We may update this policy as DialogMaker changes. When changes are material, we will take reasonable steps to notify account users, such as updating this page, emailing account owners, or showing an in-product notice.