Legal
Privacy policy
Last updated July 26, 2026
Seminar Engine is a seminar marketing and operations platform built and operated by Boydston Marketing. This policy explains how we handle information across Seminar Engine’s public website, client application, seminar experiences, and optional Google and Meta advertising integrations.
1. Scope and roles
This policy applies when you visit SeminarEngine.com, create or use a Seminar Engine account, connect an advertising account, register for or operate a seminar hosted through the service, or otherwise communicate with us.
For client account and product data, Boydston Marketing operates Seminar Engine and determines how account, security, and service-administration information is handled. For seminar registrant and practice data, the client practice or organization generally determines the purpose of processing and Seminar Engine processes the information to provide the requested service. A client’s registration experience may include additional client-specific privacy notices.
2. Information we collect
Information you provide
We may receive your name, email address, phone number, organization, account role, support messages, audit-request details, seminar registration information, attendance, preferences, and other information you choose to provide. Audit requests completed on Boydston Marketing’s website are also governed by its posted privacy policy.
Account and service information
We process account identifiers, tenant membership, authentication and session information, configuration choices, seminar and campaign settings, activity logs, support history, and records needed to operate, secure, and audit the service.
Advertising connection information
If an authorized user connects Google or Meta, we receive the authorization grant and the advertising assets available to that user. Depending on the provider and features selected, this can include provider user and account identifiers, manager or business information, ad-account and pixel names and IDs, currency, time zone, granted permissions, conversion actions and tag details, token-expiration information, and campaign, ad set, ad, impression, click, and spend data.
Attribution and seminar performance information
When enabled by a client, we may process landing-page and referral information, UTM values, advertising click identifiers, visitor and session identifiers, browser and device information, consent status, registrations, attendance, consultation or other configured milestones, campaign performance, and delivery diagnostics. Seminar Engine’s restricted-data mode is enabled by default and is designed to keep contact data, seminar topic and venue details, outcome labels, and conversion values out of provider payloads unless separately permitted and enabled.
Website and technical information
Hosting, security, and analytics systems may process IP address, browser type, device type, referring page, pages viewed, timestamps, cookies or similar identifiers, and request logs. We use this information to operate, protect, troubleshoot, and understand the website and service.
3. How we use information
- Provide, configure, support, and secure Seminar Engine.
- Authenticate users and enforce tenant and account permissions.
- Operate registrations, reminders, check-in, reporting, and follow-up.
- Connect the advertising account and assets an authorized user selects.
- Import permitted campaign performance and spend information.
- Send user-enabled, consent-appropriate measurement events to the selected provider.
- Diagnose failures, prevent abuse, maintain audit records, and meet legal obligations.
- Respond to inquiries and improve user-facing service functionality.
4. Google user data
Seminar Engine requests the Google Ads scopehttps://www.googleapis.com/auth/adwords and the Google Data Manager scope https://www.googleapis.com/auth/datamanager. These permissions are used only to provide the connected-account features the authorized user selects: discovering accessible Google Ads manager and advertiser accounts, reading account and campaign performance, listing and mapping conversion actions, importing spend, and sending configured measurement events through Google’s APIs.
We store the selected Google customer and manager identifiers, account display information, granted scopes, conversion mappings and tag details, connection and validation timestamps, and an encrypted OAuth refresh token. Google credentials are not exposed through client-facing APIs. We use Google user data only to provide or improve these user-facing integration features and related security and support.
We do not sell Google user data, use it for personalized or retargeted advertising, provide it to data brokers or information resellers, use it to determine creditworthiness or eligibility, or use it to train generalized artificial-intelligence or machine-learning models.
Seminar Engine’s use and transfer to any other app of information received from Google APIs will adhere to theGoogle API Services User Data Policy, including its Limited Use requirements.
5. Meta Platform Data
Seminar Engine uses Facebook Login for Business and requestsads_read, business_management, andads_management. These permissions are used only to identify the businesses, ad accounts, and pixels available to the authorized user; let that user select the correct customer-owned assets; import advertising performance and spend; validate the connection; and send configured measurement events through Meta’s APIs.
We may store the app-scoped provider user identifier, selected business, ad-account, and pixel identifiers and names, granted permissions, connection and validation timestamps, token expiration, campaign performance, and an encrypted access token. We do not sell or license Meta Platform Data, use it to build unrelated profiles, make eligibility decisions, conduct surveillance, or process it for purposes unrelated to the connected Seminar Engine features.
6. How information is shared
We may disclose information only as reasonably necessary:
- To Google or Meta when an authorized user connects a provider or enables a provider feature.
- To the client organization and its authorized users within the service.
- To hosting, database, security, communications, scheduling, analytics, and support providers acting for us under appropriate obligations.
- When required by law, legal process, or a valid request, or when necessary to protect users, the service, or others.
- In connection with a merger, financing, acquisition, reorganization, or sale of assets, subject to applicable confidentiality and notice requirements.
We do not sell personal information or connected Google or Meta data. We do not share connected-provider data with third parties for their own advertising purposes.
7. Cookies and advertising measurement
The public marketing site uses technical systems needed to deliver and protect the site. Client seminar pages may use first-party storage and, when configured and permitted, Google or Meta measurement technology. Provider measurement is disabled by default per client, signed builder previews do not load advertising tags, and consent requirements can prevent a registration event from being sent to a provider.
8. Security
We use administrative, technical, and organizational safeguards designed to protect information. OAuth state, pending credentials, and provider credentials are handled server-side; credentials are encrypted at rest; connection sessions are time-limited and single-use; provider tokens are excluded from connection audit logs and browser responses; and access is restricted by account and tenant permissions. No security method is perfect, and we cannot guarantee absolute security.
9. Retention, disconnecting, and deletion
We retain information for as long as reasonably necessary to provide the service, maintain security and auditability, comply with our agreements and legal obligations, and resolve disputes. Retention varies by data type, client configuration, and applicable requirements. When information is no longer needed, we delete or de-identify it, subject to limited backup, security, fraud-prevention, legal, and accounting retention.
OAuth connection records are short-lived and single-use. Durable Google and Meta credentials are retained only while the applicable connection remains active. Disconnecting a provider in Seminar Engine removes the saved credential and disables future provider activity for that client connection. Because one provider authorization may support more than one client connection, disconnecting Seminar Engine does not necessarily revoke the user’s entire provider-level grant.
You may separately revoke Seminar Engine in your Google Account or Facebook settings. To request deletion of connected-provider or other account data, follow our data deletion instructions or emailmail@boydstonmarketing.com. We may verify your identity and authority before acting. We will respond within the period required by applicable law or platform policy and will explain if limited information must be retained.
10. Your choices and privacy rights
Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or obtain a copy of certain personal information. You may also withdraw consent where processing relies on consent. Submit a request through our data deletion page or the contact information below. If your request concerns data controlled by a client practice, we may direct or forward the request to that organization.
11. Sensitive information and children
Advertising-provider connections are not intended to transmit medical records or protected health information to Google or Meta. Clients are responsible for configuring their seminars, notices, consent, and provider use appropriately. Seminar Engine is not directed to children under 18, and we do not knowingly offer accounts to them.
12. International processing
Seminar Engine is operated in the United States. Information may be processed in the United States and other locations where our service providers operate, subject to applicable safeguards and law.
13. Changes to this policy
We may update this policy as the service or legal requirements change. We will post the updated policy here, change the “Last updated” date, and provide additional notice when required. Material changes to how connected Google or Meta data is used will be reflected before the changed practice begins.
14. Contact
Boydston Marketing
4091 Foothill Drive, Provo, UT 84604
mail@boydstonmarketing.com
(559) 261-5054