Privacy Policy

1. Who operates runClear

runClear is developed and operated by getClear Digital, a sole proprietorship based in Winnipeg, Manitoba, Canada. In this policy, “runClear,” “we,” “us,” and “our” refer to getClear Digital in its operation of the runClear service.

Organizations that use runClear generally decide why and how their customer and prospect information is processed. For that information, the organization is the controller or responsible business and getClear Digital processes the information to provide runClear.

2. Information we collect

Account and organization information

We collect information used to create and secure accounts, including names, email addresses, authentication information, organization membership, roles, team assignments, and account preferences.

Business and customer records

Organizations may enter contacts, companies, deals, tasks, notes, quotes, orders, invoices, inventory, services, files, consent records, and related activity history. This may include names, email addresses, phone numbers, company information, communications, and other details supplied by a customer or prospect. The organization using runClear is responsible for having an appropriate basis to collect and use this information.

Communications

When communications features are enabled, we may process email addresses, phone numbers, message content, message status, delivery events, timestamps, participants, and customer-consent or opt-out records so the organization can communicate with its customers.

Technical information

We process security and operational information such as IP address, browser type, device information, session timestamps, authentication events, application logs, and diagnostic data.

3. Meta, Facebook Messenger, and Lead Ads

An authorized organization administrator may connect Facebook Pages through Meta and select which Pages and products runClear may use. We receive Page identifiers, Page names, granted permissions, connection status, and Page access credentials. Page credentials are received server-side and encrypted before storage. runClear never receives or stores the administrator's Meta password.

Messenger

When Messenger is enabled for a Page, runClear may receive and process Page-scoped sender identifiers, message text and supported attachments, timestamps, message and delivery identifiers, referral information, and related conversation history. An organization may assign a chatbot to the Page so it can prepare and send replies through that Page. Conversation content and relevant chatbot instructions or knowledge may be sent to the artificial-intelligence provider selected for that chatbot.

Lead Ads

When Lead Ads is enabled, runClear receives lead identifiers and retrieves information submitted through the organization's Facebook instant forms. This may include a person's name, email address, phone number, company, form answers, form and Page identifiers, submission time, and available ad or campaign identifiers and names. runClear uses this information to create or update CRM records and route the lead to the pipeline configured for that form or Page.

The organization can disable Messenger or Lead Ads, disconnect its Meta connection, or change its routing configuration in runClear. Disconnecting Meta removes stored Page access credentials and stops future access, but it does not automatically delete customer, deal, or conversation records already imported into runClear.

4. Google Business Profile and Google API Data

The Google Business Profile integration is upcoming and is not yet available. The following describes its planned operation, separate from Google sign-in. An authorized organization administrator may connect a Google Business Profile through Google OAuth. runClear may access Business Profile accounts and locations that the authenticated Google user is authorized to manage.

We may retrieve review data, including reviewer display information provided by Google, review text, star ratings, review timestamps, average rating, and total review count. The initial integration will be read-only and will not create, edit, or automatically reply to reviews.

Google Business Profile data will be used only to provide the user-facing integration requested by the organization. This includes displaying authorized review data inside runClear and, when enabled by the merchant, on websites controlled by that merchant through a runClear-managed review widget or data endpoint, subject to Google's applicable policies. This feature will not provide third parties with indirect programmatic access to Google Business Profile APIs.

We may temporarily cache limited Google Business Profile data to operate the integration, keep the widget responsive, and synchronize changes. Review changes may be synchronized using Google Business Profile notifications, with periodic reconciliation. Temporary cached Google API content will be stored securely, retained for no more than 30 calendar days or any shorter applicable Google retention period, and deleted when that period ends.

When this integration becomes available, OAuth access and refresh tokens will be processed server-side and encrypted before storage. They will not be exposed through public widgets, data endpoints, or application logs.

Users will be able to disconnect the Google Business Profile integration from runClear. When this integration becomes available, disconnecting it will stop future Google API access and remove stored Google OAuth credentials. Temporary cached Google Business Profile data will be deleted according to Google's applicable retention requirements.

We do not sell Google user data, use it for advertising or credit decisions, or provide third parties with indirect programmatic access to Google Business Profile APIs. Google API data may only be transferred as necessary to provide the requested runClear functionality, for security purposes, to comply with applicable law, or otherwise as permitted by Google's API Services User Data Policy.

runClear's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

5. How we use information

• Provide, maintain, personalize, and secure runClear.
• Organize customer, sales, inventory, and fulfillment records.
• Receive leads and route them into configured sales pipelines.
• Send requested transactional and customer communications.
• Operate configured chatbots and communications integrations.
• Enforce organization permissions and maintain audit history.
• Process subscriptions, usage charges, and account administration.
• Diagnose problems, prevent abuse, and improve the service.
• Comply with legal obligations and valid requests.

6. Service providers and integrations

We use service providers to operate runClear. Depending on the features an organization enables, these providers may process the information needed to supply their service:

• Vercel for web hosting and request handling.
• Convex for backend infrastructure, authentication, and data storage.
• Meta for Facebook Page, Messenger, and Lead Ads integrations.
• OpenAI, Anthropic, or xAI for configured chatbot features.
• Resend for configured email delivery and receiving.
• Twilio for configured SMS and voice communications.
• Polar for subscriptions, billing, and payment administration.
• Google or GitHub when a user chooses the corresponding sign-in method.
• Google Business Profile for the upcoming organization-authorized accounts, locations, and read-only review integration, separate from Google sign-in.

We do not sell personal information or customer business data, and we do not share it with third parties for their independent advertising.

7. Cookies and local storage

runClear uses essential cookies and browser storage to maintain signed-in sessions, protect accounts, remember interface preferences, and support invitation and organization flows. The marketing site does not require advertising cookies to function.

8. Retention, disconnection, and deletion

We retain account and organization data while the account is active and as reasonably needed to provide the service, maintain security and audit records, resolve disputes, meet legal requirements, and complete billing. Retention periods may vary by record type and enabled integration.

Authorized organization users may update or remove many records directly. Disconnecting an integration stops future collection from that integration but does not automatically delete records previously added to the CRM. Account, integration, or Meta-data deletion requests can be made using our data deletion instructions.

When the upcoming Google Business Profile integration becomes available, disconnecting it will stop future Google API access and remove stored Google OAuth access and refresh tokens. Temporary cached Google Business Profile data will be deleted according to Google's applicable retention requirements, including the maximum 30-calendar-day content retention period. The general retention of CRM records does not extend retention of temporary Google API content.

9. Security

We use reasonable administrative, technical, and organizational safeguards, including encrypted connections, access controls, secret protection, organization isolation, and audit records. Meta Page access credentials and other supported integration secrets are encrypted before storage. No online service can guarantee absolute security.

When the upcoming Google Business Profile integration becomes available, its Google OAuth access and refresh tokens will be processed server-side, encrypted before storage, and protected as integration secrets. They will not be exposed through public widgets, data endpoints, or application logs.

10. Your choices and rights

Depending on where you live, you may have rights to access, correct, export, or request deletion of personal information. You may also withdraw consent where consent is the basis for processing. Contact us using the address below. We may verify your identity and authority before fulfilling a request.

11. International processing

Service providers may process information outside Manitoba or Canada. Information processed in another jurisdiction may be subject to that jurisdiction's laws.

12. Children

runClear is a business service and is not directed to children under 13. We do not knowingly collect personal information directly from children.

13. Changes and contact

We may update this policy as runClear changes. The date above identifies the latest version. Questions and privacy requests may be sent to getClear Digital at team@getclear.digital.