DMCRM PRIVACY POLICY
Effective Date: August 6th, 2026
Last Updated: August 6th, 2026
1. INTRODUCTION
Giske Business Network LLC, a Washington limited liability company (“Company,” “DMCRM,” “we,” “us,” or “our”), respects your privacy.
This Privacy Policy explains how we collect, use, disclose, store, and protect personal information when you:
Visit dmcrm.app or another website operated by us.
Create or use a DMCRM Account.
Install or use the DMCRM Chrome extension.
Purchase or manage a DMCRM Subscription.
Submit a form.
Download a resource.
Join a waitlist.
Book a call.
Apply to an affiliate, beta, or other program.
Contact customer support.
Provide feedback.
Otherwise communicate or interact with us.
This Policy also explains the important distinction between:
Information DMCRM maintains about its own Users, customers, leads, and website visitors; and
Messenger-derived and CRM information stored locally through the DMCRM Chrome extension.
The current V1 Chrome extension stores Messenger-derived and CRM information locally in the User’s Chrome extension storage. That information does not leave the User’s device.
Please review this Privacy Policy together with the DMCRM Terms of Service and the disclosure shown within the extension before first use.
2. COMPANY INFORMATION
DMCRM is operated by:
Giske Business Network LLC
1630 2nd Ave W
Seattle, Washington 98119
United States
Privacy contact: [email protected]
DMCRM has not appointed a separate privacy officer or data protection officer. Privacy questions and requests should be directed to the email address above.
3. SCOPE
This Privacy Policy applies to information processed through:
The DMCRM website.
The DMCRM Chrome extension.
DMCRM Accounts.
Subscription and billing systems.
Forms, funnels, landing pages, and checkout pages.
Customer-support systems.
Marketing and advertising systems.
Beta-testing and feedback programs.
Affiliate applications and programs.
Other business interactions with DMCRM.
This Policy does not control the independent privacy practices of third-party services such as:
Facebook.
Messenger.
Instagram.
Meta.
Google.
Google Chrome.
The Chrome Web Store.
Stripe.
Supabase.
GoHighLevel.
Freshdesk.
OpenAI or other AI tools.
Those providers maintain their own terms and privacy policies.
DMCRM is an independent software product. It is not affiliated with, endorsed by, sponsored by, administered by, or officially associated with Meta, Facebook, Messenger, Instagram, Google, or Google Chrome unless expressly stated otherwise.
4. THE CHROME EXTENSION’S PURPOSE
The DMCRM Chrome extension provides customer relationship management and follow-up organization tools on supported Facebook and Messenger pages.
Its current functions allow Users to:
Tag selected Messenger contacts.
Organize tagged contacts.
Add notes.
Assign pipeline stages.
Create tasks and follow-up dates.
Assign priority levels.
Add contact details.
Create and use message templates.
Export and import locally stored CRM information.
The current extension does not automatically send messages, automate replies, bulk-message contacts, or post content on a User’s behalf.
5. INFORMATION READ WHEN A USER TAGS A CONTACT
The current DMCRM Chrome extension does not automatically scan or save every contact displayed in a Messenger inbox.
DMCRM reads and saves supported contact information only when the User actively applies a DMCRM tag to that contact.
When a User tags a contact, the extension may read and save:
The contact’s Facebook profile name.
The contact’s Facebook profile link.
The Messenger thread or conversation link.
Relative “last active” information displayed by Facebook or Messenger.
The DMCRM tag selected by the User.
This information is used to identify the tagged contact and provide DMCRM’s organizational and follow-up functionality.
6. INFORMATION DMCRM DOES NOT READ FROM MESSENGER
The current extension does not read or collect:
Full Messenger message content.
Message preview text.
Facebook profile photographs.
Facebook user identification numbers.
Whether a message is read or unread.
Group names.
Community names.
Facebook passwords.
Facebook login credentials.
Facebook authentication cookies.
Facebook authentication tokens.
DMCRM does not read the content of Messenger conversations.
The current extension also does not:
Automatically scan an entire inbox.
Automatically import all Messenger contacts.
Automatically collect entire conversations.
Automatically classify contacts.
Automatically tag contacts.
7. INFORMATION USERS MANUALLY ENTER
Users may manually add information such as:
Tags.
Contact notes.
Pipeline assignments.
Pipeline stages.
Tasks.
Follow-up dates.
Priority levels.
Email addresses.
Telephone numbers.
Message templates.
Notes entered on contact cards.
DMCRM does not currently provide custom fields.
The User controls this information. DMCRM does not automatically change or delete User-entered CRM records.
Future software updates may change how information is displayed, organized, migrated, or made available under a particular Plan. DMCRM will not intentionally delete stored CRM information without notice except where deletion results from:
The User’s action.
Uninstallation of the extension.
Account closure.
A security requirement.
A legal requirement.
Another circumstance described in the Terms of Service.
8. LOCAL STORAGE OF CRM INFORMATION
8.1 Local-only storage
The current extension stores CRM and Messenger-derived information only in chrome.storage.local.
Locally stored information may include:
Tagged contact names.
Facebook profile links.
Messenger thread links.
Relative last-active information.
Tags.
Notes.
Pipelines and stages.
Tasks.
Follow-up dates.
Priority levels.
Manually entered email addresses.
Manually entered telephone numbers.
Message templates.
Other User-entered CRM records.
This information does not leave the User’s device.
It is not currently transmitted to:
DMCRM personnel.
Supabase.
Stripe.
Google Drive.
Google Analytics.
GoHighLevel.
Meta.
Freshdesk.
OpenAI or other AI tools.
Another external provider.
8.2 No additional local encryption
Locally stored CRM information is maintained as plain JSON in Chrome local extension storage.
DMCRM does not currently apply separate record-level encryption to that locally stored information.
Its protection therefore depends in part on:
The security of the User’s device.
The security of the User’s operating system.
The security of the User’s Chrome profile.
Device passwords and screen locks.
Access to the User’s browser profile.
The User’s security practices.
Anyone with access to an unlocked device or Chrome profile may potentially access locally stored DMCRM information.
Users should:
Protect devices with a password or other access control.
Use screen locks.
Avoid using DMCRM on public or untrusted computers.
Avoid sharing Chrome profiles with unauthorized people.
Remove access for former employees, contractors, or assistants.
Protect exported files.
Maintain appropriate independent backups.
9. LOCAL BACKUP, EXPORT, AND IMPORT
The current version does not provide cloud backup.
DMCRM currently supports local JSON export and import.
Users may export their locally stored CRM information as a JSON file. CSV export may be introduced later.
Exported files:
Download directly to the User’s device.
Are not automatically transmitted to DMCRM.
May contain personal information about the User’s contacts.
Must be stored and protected by the User.
Users should not share exported files with unauthorized persons.
DMCRM cannot recover a local backup file that is lost, deleted, corrupted, or not created.
10. UNINSTALLING THE EXTENSION
Uninstalling the DMCRM Chrome extension removes its locally stored information from Chrome.
Users who want to preserve their CRM information must export a local backup before uninstalling the extension.
Because DMCRM does not receive a copy of locally stored CRM data, DMCRM cannot recover that information after it has been deleted or removed.
11. NO AUTOMATED MESSAGING
The current extension does not:
Automatically send Messenger messages.
Automatically reply to messages.
Bulk-message contacts.
Post content on the User’s behalf.
Automatically initiate conversations.
Circumvent messaging limits or platform enforcement.
DMCRM helps Users organize contacts and follow-ups. The User remains responsible for deciding:
Who to contact.
Whether the User has authority or permission to contact that person.
What message to send.
When to send it.
Whether the communication complies with law.
Whether the communication complies with applicable platform policies.
12. FACEBOOK ACCOUNT ACCESS
DMCRM does not collect, access, or store:
Facebook passwords.
Facebook login credentials.
Facebook authentication cookies.
Facebook authentication tokens.
The extension works only while the User is already logged into Facebook through Chrome.
DMCRM does not independently log into the User’s Facebook Account.
13. CHROME PERMISSIONS AND HOST ACCESS
The current V1 extension requests the Chrome storage permission.
It also uses host access for:
*.supabase.co
Content scripts operate only on the supported Facebook and Messenger hosts.
Supabase access is used for authentication and purchase or entitlement verification.
The current extension does not request:
Clipboard permission.
Notifications permission.
Downloads permission.
Tabs permission.
Chrome identity or Google-login permission.
Scripting permission.
DMCRM does not use its permissions or host access to:
Monitor unrelated websites.
Monitor unrelated browser tabs.
Collect general browsing history.
Collect search history.
Read Messenger message content.
Collect Facebook credentials.
Build advertising profiles from Messenger or CRM data.
Download or execute remotely hosted extension code.
The final Chrome Web Store declarations should match the production manifest.json.
14. NO REMOTELY HOSTED EXECUTABLE CODE
DMCRM does not download or execute JavaScript or other executable extension logic from a remote server.
The extension’s executable code is included within the extension package submitted to the Chrome Web Store.
DMCRM may connect to Supabase for authentication and entitlement data. Those connections are for data exchange and are not used to download or execute new extension code.
15. INFORMATION THAT LEAVES THE DEVICE
Only limited Account information currently leaves the device through the extension:
The User’s login email is sent to Supabase Auth.
The User’s DMCRM Account ID is sent to the applicable entitlement function to verify purchases and access rights.
The following do not leave the device:
Messenger contacts.
Tagged contact names.
Facebook profile links associated with tagged contacts.
Messenger thread links.
Relative last-active information.
Tags.
Notes.
Messages.
Pipelines.
Tasks.
Follow-up information.
Priority information.
Contact email addresses entered by the User.
Contact telephone numbers entered by the User.
Message templates.
Other locally stored CRM records.
16. DMCRM ACCOUNT INFORMATION
Separate from locally stored CRM information, DMCRM may maintain information needed to create and administer a DMCRM Account, including:
Name.
Email address.
DMCRM Account ID.
Subscription status.
Free or Pro Plan status.
Stripe customer or transaction identifiers.
Limited Account-creation and authentication information.
Limited login or session information.
Billing and transaction information.
Support history.
Account preferences.
Other information voluntarily provided to DMCRM.
Internet Protocol address, browser, device, operating-system, or security information may also be automatically processed by authentication, hosting, payment, website, or security providers.
DMCRM uses passwordless authentication through email and a six-digit one-time passcode provided through Supabase.
DMCRM does not maintain a traditional User-created password for this login process.
17. SUPABASE
DMCRM uses Supabase for:
Passwordless email authentication.
Sending or validating six-digit one-time passcodes.
Subscription and entitlement verification.
Account access control.
Connections to Supabase use secure HTTPS connections.
The extension does not send the following to Supabase:
Messenger contacts.
Messenger messages.
Tags.
Notes.
Pipelines.
Tasks.
Follow-up information.
Other locally stored CRM records.
Facebook passwords.
Facebook authentication cookies.
Facebook authentication tokens.
18. PAYMENT INFORMATION
DMCRM uses Stripe or another authorized payment processor to process payments.
DMCRM does not receive or store complete payment-card numbers where Stripe collects and processes that information directly.
DMCRM may receive limited transaction information, including:
Payment status.
Subscription status.
Stripe customer identifiers.
Transaction identifiers.
Card type.
Card expiration information.
Billing contact information.
Refund information.
Chargeback or payment-dispute information.
Stripe independently processes payment information under its own terms and privacy practices.
19. INFORMATION COLLECTED FROM LEADS AND NON-CUSTOMERS
DMCRM may collect information from people who are not currently paying customers, including:
Website leads.
People who request free resources.
Waitlist members.
People who book calls.
Affiliate applicants.
Beta testers.
People who submit feedback.
People who contact support before creating an Account.
People who express interest in a purchase or Subscription.
Information voluntarily submitted may include:
Name.
Email address.
Telephone number.
Business or company name.
Website address.
Social media profile.
Form responses.
Call-booking details.
Affiliate application information.
Beta-testing feedback.
Support messages.
Purchase or Subscription interest.
Other information voluntarily submitted.
DMCRM may use this information to:
Respond to requests.
Provide requested resources.
Schedule calls.
Evaluate applications.
Conduct beta testing.
Provide customer support.
Send permitted marketing communications.
Administer sales and customer relationships.
Improve DMCRM.
Maintain business records.
20. WEBSITE ANALYTICS
20.1 Google Analytics
DMCRM may use Google Analytics on its website to understand website traffic and usage.
Depending on configuration, Google Analytics may process information such as:
Pages visited.
Website sessions.
Engagement activity.
Traffic sources.
Referral sources.
Approximate location.
Browser information.
Device information.
Operating-system information.
Cookie or device identifiers.
Other general website-usage information.
DMCRM does not intentionally send Messenger information or locally stored CRM information to Google Analytics.
DMCRM does not intentionally send names, email addresses, telephone numbers, or other directly identifying CRM information to Google Analytics.
20.2 Meta Pixel
DMCRM may use Meta Pixel on its website for:
Website analytics.
Advertising measurement.
Conversion measurement.
Retargeting.
Audience creation.
Measuring visits, leads, registrations, checkouts, or purchases.
Depending on configuration, Meta may receive:
Pages visited.
Website URLs.
Browser information.
Device information.
Internet Protocol address information.
Meta cookie or advertising identifiers.
Referral information.
Website actions.
Conversion events.
Registration, checkout, or purchase events.
Purchase value or currency information.
Hashed identifiers used for audience matching.
DMCRM does not provide locally stored Messenger or CRM data to Meta for advertising.
21. COOKIES AND SIMILAR TECHNOLOGIES
The DMCRM website and its providers may use:
Cookies.
Pixels.
Tags.
Local storage.
Similar technologies.
These technologies may support:
Website operation.
Analytics.
Advertising.
Conversion measurement.
Security.
Preferences.
Marketing attribution.
Users may be able to control certain technologies through:
Browser settings.
Google advertising settings.
Meta advertising settings.
Recognized browser-based privacy signals.
Other provider tools.
Blocking cookies or similar technologies may affect website functionality or reduce the accuracy of analytics and advertising measurement.
22. MARKETING COMMUNICATIONS
DMCRM may use contact information supplied by:
DMCRM Users.
Customers.
Leads.
Free-resource subscribers.
People who submit forms.
People who join related opt-in lists.
People who previously opted into related Company marketing, including GroupFunnels or other Company-operated lists.
DMCRM does not use purchased cold-email lists or lists collected without an opt-in or other lawful source.
Marketing emails may be sent through GoHighLevel or another provider.
Marketing emails include an unsubscribe method where required.
A person may unsubscribe from marketing emails without losing access to DMCRM.
Unsubscribing from marketing does not prevent DMCRM from sending necessary communications concerning:
Login codes.
Account administration.
Billing.
Subscription status.
Security.
Support.
Material product changes.
Changes to legal terms.
Other non-marketing matters.
23. META CUSTOM AUDIENCES AND TARGETED ADVERTISING
DMCRM may upload email addresses or similar identifiers associated with its own:
Leads.
Customers.
Subscribers.
Prior opt-in business lists.
to Meta for:
Custom Audiences.
Retargeting.
Audience matching.
Advertising measurement.
Related advertising purposes.
DMCRM does not use locally stored Messenger or CRM information to create advertising audiences.
DMCRM does not sell personal information for money.
Certain laws may define some advertising-related disclosures as “sharing,” targeted advertising, or cross-context behavioral advertising even where no money is exchanged.
Where applicable law provides such a right, a person may request to opt out of qualifying advertising-related sharing by contacting:
DMCRM will honor recognized browser-based opt-out preference signals, such as Global Privacy Control, where legally required and technically applicable.
24. CUSTOMER SUPPORT, FEEDBACK, AND AI TOOLS
24.1 Support and feedback
When a person submits:
A support ticket.
Product feedback.
A beta-testing comment.
A survey response.
A business communication.
A feature request.
Another voluntary submission.
DMCRM may process that information to:
Respond to the person.
Diagnose issues.
Maintain support history.
Improve DMCRM.
Train support personnel.
Investigate bugs.
Prevent fraud or abuse.
Address security issues.
Resolve contractual or legal matters.
Freshdesk or another support provider may receive the email address and information included in a support request.
24.2 OpenAI or other AI tools
DMCRM may use OpenAI or other AI tools to:
Review support tickets.
Summarize support requests.
Assist with support responses.
Review feedback.
Summarize beta-testing comments.
Organize business communications.
Assist with internal operations.
AI-assisted processing is part of DMCRM’s normal support and operational process. DMCRM does not offer a separate opt-out from this processing.
Users should not include unnecessary sensitive information in support tickets, feedback, or other communications.
OpenAI or other AI tools do not automatically:
Access the DMCRM Chrome extension.
Access Messenger information.
Access locally stored CRM records.
Access Facebook credentials.
Make decisions concerning Account approval or denial.
Messenger or CRM information would be processed by an AI tool only if a User voluntarily included it in a support ticket, feedback submission, or other direct communication to DMCRM.
DMCRM does not use Messenger data or locally stored CRM records to train AI models.
Where reasonably available through provider settings, DMCRM will configure AI providers so support tickets, feedback, and related communications are not used to train public or third-party AI models.
25. CURRENT ABSENCE OF IN-EXTENSION ANALYTICS
The current V1 Chrome extension does not contain an in-extension analytics or telemetry system.
It does not automatically transmit:
Buttons clicked.
Screens opened.
Feature-usage events.
Time spent in the extension.
Crash reports.
Error logs.
Console logs.
Screenshots.
Messenger-page information.
CRM record information.
If DMCRM later introduces in-extension analytics, it will update:
This Privacy Policy.
Applicable Chrome Web Store disclosures.
Applicable in-product notices.
DMCRM will provide any required disclosure or consent before introducing a material new data practice.
26. CURRENT ABSENCE OF CLOUD BACKUP
The current V1 Chrome extension does not provide cloud backup or cloud synchronization of locally stored CRM information.
There is no cloud copy of the User’s contacts, tags, notes, messages, pipelines, tasks, or other locally stored CRM records.
If DMCRM later introduces cloud backup or synchronization, it will update:
This Privacy Policy.
Applicable Terms.
Chrome Web Store privacy declarations.
In-extension disclosures.
DMCRM will obtain any affirmative consent required before locally stored CRM information is uploaded.
27. SERVICE PROVIDERS
DMCRM may use service providers including:
Supabase for authentication and entitlement verification.
Stripe for payment processing.
GoHighLevel for forms, funnels, marketing emails, customer records, and business operations.
Google for website analytics and internal business records.
Meta for website analytics, advertising, conversion measurement, and Custom Audiences.
Freshdesk for customer support.
OpenAI or other AI tools for support, feedback, and operational assistance.
Google Drive and GoHighLevel may contain DMCRM’s own customer and lead information, such as:
Names.
Email addresses.
Purchases.
Subscription status.
Customer or lead history.
They do not currently receive locally stored Messenger contacts or CRM records from the extension.
DMCRM may add, replace, or remove providers as its business and technology evolve.
Material changes to how personal information is collected, used, or shared will be reflected in this Policy and, where required, through an in-product notice or renewed consent process.
28. HUMAN ACCESS TO INFORMATION
DMCRM’s own customer and business records may be accessed only when reasonably necessary by authorized:
Owners.
Assistants.
Support personnel.
Developers.
Advertising or marketing contractors.
Accountants.
Legal advisers.
Service providers.
Access may be permitted for:
Account administration.
Customer support.
Billing.
Security.
Fraud prevention.
Product maintenance.
Marketing.
Legal compliance.
Accounting.
Business operations.
Locally stored Messenger and CRM information is not accessible to DMCRM personnel because it remains on the User’s device.
29. HOW DMCRM USES PERSONAL INFORMATION
DMCRM may use personal information to:
Create and administer Accounts.
Send one-time login codes.
Verify purchases and subscription status.
Process payments.
Provide Free and paid features.
Respond to support requests.
Communicate with Users.
Send requested resources.
Schedule calls.
Evaluate affiliate or beta applications.
Maintain customer and lead records.
Send permitted marketing communications.
Conduct advertising and retargeting.
Measure website activity and conversions.
Maintain and improve DMCRM.
Protect Accounts and systems.
Prevent fraud and abuse.
Enforce agreements.
Maintain tax, accounting, and transaction records.
Comply with legal obligations.
Establish, exercise, or defend legal claims.
Perform other purposes disclosed when information is collected.
30. LEGAL BASES FOR PROCESSING
Where applicable law requires a legal basis, DMCRM may rely on:
Contractual necessity
To:
Create and administer Accounts.
Authenticate Users.
Verify purchases and Subscriptions.
Process transactions.
Provide the Service.
Provide customer support.
Enforce the Terms of Service.
Legitimate interests
To:
Maintain and improve DMCRM.
Secure Accounts and systems.
Prevent fraud and abuse.
Maintain business records.
Communicate with Users.
Understand website performance.
Operate and develop the business.
Consent
Where applicable, DMCRM may rely on consent for:
Marketing communications.
Meta Custom Audiences and qualifying advertising activities.
Testimonials or recordings.
Material new Chrome extension data practices.
Other activities for which consent is requested.
Legal obligations
To:
Maintain billing, transaction, tax, and accounting records.
Respond to lawful requests.
Comply with applicable law.
Protect legal rights.
Meet regulatory obligations.
31. CHROME WEB STORE LIMITED USE COMMITMENT
DMCRM’s use of information obtained through Chrome extension permissions will comply with the Chrome Web Store User Data Policy, including applicable Limited Use requirements.
Information obtained through Chrome extension access will be used only as necessary to:
Provide the extension’s disclosed user-facing functionality.
Maintain and support that functionality.
Secure the extension and User Accounts.
Prevent fraud and abuse.
Troubleshoot the extension.
Comply with applicable law.
DMCRM does not use or transfer information obtained through Chrome extension access for:
Personalized or interest-based advertising.
Retargeting.
Sale to advertising platforms.
Sale to data brokers.
Sale to information resellers.
Creditworthiness determinations.
Lending decisions.
Unrelated marketing.
Unrelated profiling.
Any purpose unrelated to the extension’s disclosed functionality.
These restrictions apply to Messenger-derived and locally stored CRM information.
They do not prevent DMCRM from using its own separately collected customer or lead information for the marketing and advertising activities described elsewhere in this Policy.
32. IN-EXTENSION DISCLOSURE AND CONSENT
Before V1 begins reading or storing supported Facebook or Messenger contact information, DMCRM will present a clear in-extension notice explaining:
What information the extension reads.
When that information is read.
That message content is not read.
That CRM information is stored locally in Chrome.
That CRM information does not currently leave the device.
Where the User can review this Privacy Policy and the Terms of Service.
The User will be required to take an affirmative action, such as clicking “Agree and Continue,” before the applicable data handling begins.
The User’s choice may be remembered so the notice does not appear during every use.
DMCRM will provide a new notice and request renewed consent where required before materially changing:
What information the extension reads.
What information it stores.
What information it transmits.
How extension information is used.
The parties receiving extension information.
33. SECURITY
DMCRM uses reasonable administrative, technical, and organizational measures appropriate to the information and Services involved.
Current measures include:
Secure HTTPS connections.
Passwordless email authentication.
Six-digit one-time login codes.
Access controls for Company customer records.
Need-to-know access restrictions.
Use of established service providers.
Procedures for responding to suspicious activity and security incidents.
Locally stored CRM information is not additionally encrypted by DMCRM.
No transmission, storage system, device, browser extension, or security procedure can be guaranteed to be completely secure.
Users remain responsible for:
Securing their devices.
Securing their Chrome profiles.
Protecting access to their email.
Using screen locks.
Avoiding public or shared computers.
Protecting exported backup files.
Promptly reporting suspected unauthorized access.
Exporting data before uninstalling the extension.
34. SECURITY INCIDENTS
If DMCRM becomes aware of a suspected security incident, it may:
Investigate the incident.
Contain the incident.
Restrict affected access.
Reset sessions or authentication.
Take systems or features offline.
Work with service providers or security professionals.
Protect affected Accounts and systems.
Preserve relevant records.
Notify affected persons where required by law.
Notify regulators or authorities where legally required.
DMCRM does not promise notice for every minor error or technical issue that does not constitute a legally reportable security incident.
35. DATA RETENTION
DMCRM retains personal information only for as long as reasonably necessary to:
Provide the Service.
Maintain Accounts.
Process billing.
Provide support.
Maintain support history.
Conduct business operations.
Send permitted marketing communications.
Protect security.
Prevent fraud and abuse.
Improve DMCRM.
Comply with tax, accounting, and legal obligations.
Resolve disputes.
Enforce agreements.
Establish, exercise, or defend legal claims.
Certain records may be retained for longer periods, including:
Billing and transaction records.
Refund and chargeback records.
Tax and accounting records.
Consent records.
Support tickets.
AI-assisted support summaries.
Security records.
Fraud-prevention records.
Legal notices.
Contract records.
Locally stored CRM information remains on the User’s device until the User:
Deletes it.
Clears extension storage.
Uninstalls the extension.
Takes another action that removes it.
DMCRM cannot retain a copy of local CRM information that was never transmitted to it.
36. ACCOUNT DELETION AND MARKETING OPT-OUTS
36.1 Account deletion
A User may delete or request deletion of their DMCRM Account by contacting:
Account deletion may delete:
The User’s DMCRM Account.
Account access.
Authentication and entitlement access associated with the Account.
Account deletion does not necessarily delete:
Support tickets.
Billing records.
Transaction records.
Tax records.
Accounting records.
Fraud-prevention records.
Security records.
Legal records.
Marketing records.
Other records reasonably needed for the purposes described in this Policy.
36.2 Local CRM deletion
Users may delete:
Individual contacts.
Individual CRM records.
All locally stored CRM information.
Users control local deletion through the extension and their Chrome environment.
36.3 Marketing opt-outs
Deleting a DMCRM Account does not automatically unsubscribe a person from marketing communications.
A person who does not want marketing emails must:
Use the unsubscribe link.
Contact DMCRM with a marketing opt-out request.
Use another applicable opt-out method.
Removal from Meta Custom Audiences or similar advertising systems may require:
A targeted-advertising opt-out.
A qualifying privacy request.
A recognized browser-based opt-out signal.
Another method required by applicable law.
Where applicable law requires broader deletion or opt-out rights, DMCRM will honor those rights.
37. PRIVACY RIGHTS
Depending on applicable law, a person may have the right to request:
Access to personal information.
Confirmation that personal information is being processed.
Correction of inaccurate information.
Deletion of eligible information.
A copy or export of eligible information.
Restriction of certain processing.
Objection to certain processing.
Withdrawal of consent where processing is based on consent.
Opt-out from marketing communications.
Opt-out from certain targeted advertising.
Opt-out from certain advertising-related sharing.
Appeal of a denied privacy request.
Other rights provided by applicable law.
Requests may be sent to:
DMCRM may verify the requester’s identity or authority before completing a request.
Verification may include:
Confirming access to the Account email.
Confirming Account information.
Confirming transaction or Subscription details.
Confirming authority to act for a business.
Confirming authority to act for another person.
Requesting other information reasonably necessary to prevent unauthorized disclosure or deletion.
Some information may be exempt from a request or retained where necessary for:
Billing.
Tax.
Accounting.
Security.
Fraud prevention.
Legal compliance.
Establishing, exercising, or defending claims.
Enforcing agreements.
Other lawful purposes.
38. CALIFORNIA PRIVACY RIGHTS
This Section applies only to the extent California privacy law applies to DMCRM and the relevant personal information.
California residents may have rights to:
Know the categories of personal information collected.
Know the sources of personal information.
Know the purposes for collection or use.
Know the categories of parties receiving information.
Access specific pieces of personal information.
Correct inaccurate personal information.
Delete eligible personal information.
Opt out of the sale of personal information.
Opt out of certain sharing for cross-context behavioral advertising.
Receive equal service without unlawful discrimination for exercising privacy rights.
DMCRM does not sell personal information for money.
DMCRM may disclose DMCRM customer or lead identifiers to Meta for Custom Audiences, retargeting, and related advertising. This may be considered “sharing” under certain California privacy requirements.
Locally stored Messenger and CRM information is not used for this advertising activity.
California requests may be sent to:
Where applicable and technically recognized, DMCRM will honor opt-out preference signals such as Global Privacy Control.
DMCRM may verify a request before completing it.
An authorized agent may submit a request where permitted by law, but DMCRM may require proof of authority and verification of the affected person.
DMCRM will not unlawfully discriminate against a person for exercising an applicable privacy right.
39. PRIVACY REQUEST APPEALS
Where applicable law provides an appeal right, a person whose privacy request is denied may appeal by:
Replying to the denial notice; or
Emailing [email protected].
The appeal should identify:
The original request.
The date of the decision.
The reason the decision should be reconsidered.
Any additional relevant information.
40. CHILDREN’S PRIVACY
DMCRM is intended only for adults who are at least eighteen years old.
DMCRM does not knowingly collect personal information from children.
Users must not use DMCRM to enter or maintain information about minors.
A parent or guardian who believes a child has submitted information to DMCRM may contact:
41. SENSITIVE PERSONAL INFORMATION
DMCRM does not intentionally request or collect sensitive personal information such as:
Social Security numbers.
Government identification numbers.
Bank-account credentials.
Complete payment-card information.
Medical or health information.
Biometric information.
Information about children.
Passwords for third-party Accounts.
Other highly sensitive or specially regulated information.
Users should not enter such information into:
DMCRM contact records.
Notes.
Support tickets.
Feedback forms.
Beta-testing submissions.
Other communications.
42. INTERNATIONAL PROCESSING
DMCRM is based in the United States.
Personal information may be processed or stored in:
The United States.
Other countries where DMCRM’s providers operate.
Those countries may have privacy laws that differ from the laws in the person’s place of residence.
DMCRM relies on the privacy, security, contractual, and legal commitments applicable to its providers.
Where required by applicable law, DMCRM may use appropriate mechanisms for international transfers.
43. AUTOMATED DECISION-MAKING
DMCRM currently provides tools through which Users manually assign:
Tags.
Pipeline stages.
Priorities.
Tasks.
Follow-up dates.
Other contact classifications.
The User chooses and enters this information.
DMCRM does not currently make automated decisions about contacts that:
Determine whether a person receives a service.
Determine whether a person receives credit.
Determine legal rights.
Automatically approve or reject a person.
Create similarly significant effects without human involvement.
44. BUSINESS TRANSFERS
DMCRM may be involved in:
A merger.
An acquisition.
A financing.
A reorganization.
A sale of assets.
A sale or transfer of DMCRM.
Another business transaction.
Information may be reviewed or transferred as part of such a transaction where permitted by law.
Assignment of the Terms of Service does not independently authorize transfer of Chrome extension User Data where Chrome Web Store policy or applicable law requires separate consent.
DMCRM will obtain prior consent before transferring Chrome extension User Data in connection with a business transaction where such consent is required.
45. LEGAL DISCLOSURES
DMCRM may disclose personal information where reasonably necessary to:
Comply with applicable law.
Respond to valid legal process.
Respond to a court order, subpoena, warrant, or governmental request.
Protect DMCRM’s rights.
Protect Users or third parties.
Investigate fraud, abuse, or security incidents.
Enforce the Terms of Service.
Establish, exercise, or defend legal claims.
Prevent serious harm.
DMCRM may challenge a request it reasonably believes is unlawful, invalid, or overbroad.
46. CHANGES TO THIS PRIVACY POLICY
DMCRM may update this Privacy Policy to reflect:
Changes to DMCRM.
New features.
New providers.
Changes to data practices.
Security developments.
Legal or regulatory requirements.
Corrections or clarifications.
Other business or operational changes.
The updated Policy will identify its effective or last-updated date.
DMCRM may provide notice of material changes through:
Email.
dmcrm.app.
The DMCRM Account or dashboard.
The Chrome extension.
An in-product notice.
Another reasonable method.
A material new Chrome extension data practice will not be implemented solely by updating this Policy or relying on continued use.
Before materially changing what the extension reads, stores, transmits, or how extension information is used, DMCRM will provide any required in-product disclosure and obtain any required affirmative consent.
47. CONTACT US
Questions, privacy requests, deletion requests, correction requests, access requests, advertising opt-outs, and appeals may be sent to:
Giske Business Network LLC
1630 2nd Ave W
Seattle, Washington 98119
United States
Email: [email protected]
Please include enough information for DMCRM to identify and evaluate the request.
Do not send:
Account passwords.
Complete payment-card numbers.
Social Security numbers.
Government identification numbers.
Unnecessary sensitive information.
through ordinary email.
Full terms and conditions can be found at dmcrm.app/terms
Affiliate terms and conditions can be found at dmcrm.app/affiliateterms
Main website can be found at dmcrm.app