Privacy Policy

This Privacy Policy explains how Apexcm LLC, doing business as ApexCM ("ApexCM," "we," "us," or "our"), collects, uses, discloses, stores, retains, and otherwise processes personal information in connection with the ApexCM Services.

This Privacy Policy applies to information processed through:

• https://apexcm.pro;
• ApexCM applications;
• ApexCM customer portals;
• subcontractor/vendor portals;
• account and workspace functionality;
• ApexCM AI functionality;
• payment-related features;
• communications;
• backups;
• integrations; and
• related ApexCM services.

Please read this Policy carefully.

1. WHO WE ARE

Apexcm LLC

Doing business as ApexCM

3501 Coxcomb Mews

Woodbridge, Virginia 22193

United States

Privacy Email: privacy@apexcm.pro

Legal Email: Said@apexcm.pro

Support Email: Support@Apexcm.pro

Website: https://apexcm.pro

2. SCOPE OF THIS PRIVACY POLICY

This Policy applies to personal information ApexCM processes in connection with the Services.

ApexCM is used by businesses that may upload information concerning their:

• employees;
• workers;
• subcontractors;
• vendors;
• customers;
• project participants; and
• other individuals.

Depending on context, the ApexCM customer may determine the purposes for which such information is processed.

Accordingly, ApexCM may act as:

• an independent business/controller for certain account, billing, security, operational, and legal purposes; and
• a service provider/processor for information ApexCM processes on behalf of a business customer.

If your information was submitted by your employer, contractor, service provider, or another ApexCM customer, that organization may be the appropriate entity to contact first regarding certain privacy rights.

3. PERSONAL INFORMATION WE COLLECT

The categories of information ApexCM processes depend on how the Services are used.

4. ACCOUNT INFORMATION

We may process:

• full name;
• display name;
• email address;
• telephone number;
• job title;
• profile photograph;
• workspace role;
• account role;
• membership status;
• account preferences;
• authentication information; and
• associated account identifiers.

Passwords are handled through supported authentication infrastructure.

ApexCM application code does not intentionally store passwords in plaintext.

5. WORKSPACE AND BUSINESS INFORMATION

ApexCM may process:

• business/company name;
• logo;
• company address;
• telephone number;
• email address;
• website;
• tax identification information;
• industry;
• currency;
• owner information;
• workspace membership;
• roles;
• permissions;
• payment configuration; and
• other business settings.

6. CUSTOMER INFORMATION

ApexCM users may enter information concerning their own customers, including:

• name;
• email;
• telephone number;
• address;
• company;
• project information;
• notes;
• estimates;
• invoices;
• payment requests;
• change orders;
• customer messages;
• approvals;
• typed signatures;
• payment status;
• transaction records; and
• associated project information.

7. PROJECT INFORMATION

ApexCM may process:

• project name;
• client/customer information;
• project address;
• project type;
• project manager;
• project dates;
• budget;
• cost codes;
• project status;
• documents;
• project members;
• assignments;
• tasks;
• labor records;
• change orders;
• payment records; and
• related business data.

8. RECEIPTS AND EXPENSES

ApexCM may process uploaded or manually entered receipt information including:

• receipt photographs;
• PDFs;
• vendor name;
• vendor address;
• vendor telephone number;
• receipt number;
• purchase date;
• payment-method description;
• purchase-order number;
• job number;
• order number;
• account number;
• customer code;
• customer name;
• product descriptions;
• line items;
• subtotal;
• discounts;
• taxes;
• tips;
• shipping;
• total;
• barcodes;
• categories;
• cost codes;
• project association; and
• approval history.

9. WORKER AND EMPLOYMENT-RELATED INFORMATION

Authorized organizations may use ApexCM to process worker, employee, or subcontractor information, potentially including:

• first name;
• last name;
• employee identifier;
• email;
• telephone number;
• physical address;
• date of birth;
• hire date;
• role;
• trade;
• pay rate;
• skills;
• certifications;
• employment history;
• emergency-contact information;
• bank name;
• masked account information;
• payment preferences;
• timesheets;
• hours;
• labor costs;
• approval records;
• contracts; and
• onboarding documentation.

Onboarding documents may include items such as:

• W-9 forms;
• identification documents;
• certificates of insurance; and
• other worker or subcontractor records.

ApexCM customers are responsible for having an appropriate lawful basis and authority to process this information.

10. PAYMENT AND BILLING INFORMATION

ApexCM uses payment providers such as Stripe for applicable payment functionality.

Stripe may collect:

• payment-card information;
• billing information;
• banking information; and
• related payment credentials

directly through Stripe-managed interfaces.

ApexCM does not intentionally store complete credit-card or debit-card numbers in the ApexCM application database.

ApexCM may retain:

• Stripe customer identifiers;
• subscription identifiers;
• checkout/session identifiers;
• transaction identifiers;
• payment links;
• amounts;
• payment status;
• transaction dates;
• plan information;
• masked bank information;
• payment method information; and
• related transaction records.

11. ALTERNATIVE PAYMENT INFORMATION

Where users or customers use supported non-card payment workflows, ApexCM may process:

• check images;
• payment-proof screenshots;
• Zelle-related confirmation information;
• cash pickup information;
• manual payment references;
• Venmo/PayPal or other method descriptions where configured; and
• related transaction information.

12. ELECTRONIC SIGNATURE AND APPROVAL INFORMATION

When a customer signs or approves a record, ApexCM may process:

• typed signature;
• customer name;
• approval/rejection status;
• timestamp;
• IP address;
• device/browser information;
• comments;
• portal token information; and
• audit records.

This information is used to document activity and support transaction/audit records.

13. COMMUNICATIONS

ApexCM may process communications including:

• estimate clarification messages;
• project comments;
• approval notes;
• rejection reasons;
• customer messages;
• attachments;
• transactional email content;
• SMS content;
• notification information; and
• related communication metadata.

14. FILES AND DOCUMENTS

ApexCM users may upload files including:

• receipt images;
• receipt PDFs;
• project files;
• photographs;
• floor plans;
• drawings;
• scope documents;
• check images;
• payment proof;
• worker documentation;
• insurance documents;
• W-9 forms;
• ID documents;
• subcontractor invoices;
• estimate attachments;
• change-order attachments;
• profile photographs; and
• other business records.

Users should upload only information reasonably necessary for legitimate use of the Services.

15. AI INPUT AND OUTPUT

When users request AI-powered features, ApexCM may process information such as:

• receipt images;
• floor-plan images;
• project descriptions;
• estimate descriptions;
• pricing context;
• user prompts;
• structured project information; and
• AI-generated results.

Relevant information may be transmitted through supported AI infrastructure to AI providers necessary to provide the requested function.

16. LOCATION-RELATED INFORMATION

ApexCM does not currently operate as a continuous GPS-tracking service.

ApexCM may process location-related information such as:

• business addresses;
• worker addresses;
• customer addresses;
• project addresses;
• ZIP codes;
• cities;
• states;
• counties;
• regional pricing markets; and
• address search queries.

Address autocomplete may involve Google Places.

17. USAGE AND ACTIVITY INFORMATION

ApexCM may process:

• receipts processed;
• estimates processed;
• invoices processed;
• usage counters;
• subscription usage;
• audit logs;
• user actions;
• timestamps;
• record history;
• approval activity;
• notification activity; and
• similar operational information.

18. DEVICE AND TECHNICAL INFORMATION

Depending on feature usage, ApexCM or infrastructure providers may process technical information such as:

• IP address;
• browser information;
• device information;
• authentication/session information;
• security information;
• error information;
• request information; and
• similar operational data.

ApexCM specifically records certain IP/device information when customers take significant approval or signature actions.

19. USER PREFERENCES

ApexCM may process preferences such as:

• theme;
• accent color;
• language;
• currency;
• timezone;
• font size;
• default pages;
• navigation preferences; and
• similar interface settings.

The application may support languages including English, Spanish, and Arabic.

20. SEARCH INFORMATION

Current audited functionality does not intentionally persist ordinary in-app search/filter history as a server-side personal profile.

This may change if future functionality is introduced.

21. COOKIES AND LOCAL STORAGE

ApexCM uses technologies necessary to provide functionality and remember preferences.

These may include:

Authentication/session technology

Authentication infrastructure may use cookies, local storage, tokens, or similar technologies necessary to keep users signed in and secure sessions.

Sidebar preference cookie

A cookie may remember whether navigation is expanded or collapsed.

Local storage

Local storage may be used for information such as:

• theme;
• accent settings;
• native-application detection; and
• dismissed floor-plan-job preferences.

22. ADVERTISING AND MARKETING TRACKING

Based on ApexCM's current audited configuration:

• no third-party advertising network was identified;
• no advertising pixel was identified;
• no Google Analytics integration was identified in active application code; and
• ApexCM does not currently use the audited application for behavioral advertising.

If those practices change, this Policy and applicable consent/opt-out mechanisms will be updated.

23. PLATFORM-LEVEL ANALYTICS

Base44 or other infrastructure providers may process operational or platform-level information necessary to:

• host the Services;
• secure the platform;
• diagnose errors;
• measure system use;
• maintain infrastructure; or
• improve platform operation.

Such processing may be governed in part by the relevant provider's terms and privacy practices.

24. HOW WE COLLECT INFORMATION

ApexCM may collect information:

• directly from users;
• from workspace administrators;
• from invited users;
• from customers using portal links;
• from subcontractors/vendors;
• through uploaded files;
• automatically through technical infrastructure;
• through payment processors;
• through authentication providers;
• through integrated services; and
• from organizations using ApexCM.

25. PURPOSES FOR WHICH WE USE INFORMATION

ApexCM may use personal information to:

1. provide the Services;
2. create accounts;
3. authenticate users;
4. manage sessions;
5. administer workspaces;
6. administer permissions;
7. process receipts;
8. perform OCR;
9. categorize expenses;
10. manage projects;
11. manage customers;
12. manage workers;
13. process timesheets;
14. generate reports;
15. prepare estimates;
16. deliver estimates;
17. enable customer approvals;
18. process change orders;
19. generate invoices;
20. facilitate payment requests;
21. facilitate payments;
22. process subscriptions;
23. perform floor-plan analysis;
24. provide AI functionality;
25. send transactional email;
26. send requested transactional SMS;
27. provide customer/vendor portals;
28. facilitate accounting integrations;
29. maintain audit records;
30. prevent fraud;
31. protect accounts;
32. secure the Services;
33. enforce Terms;
34. investigate misuse;
35. provide customer support;
36. diagnose errors;
37. maintain backups;
38. restore data where requested;
39. comply with law;
40. respond to legal process;
41. establish or defend legal claims; and
42. improve and administer the Services.

26. LEGAL BASES FOR PROCESSING

Where European or similar privacy laws require a legal basis, ApexCM may rely on:

• performance of a contract;
• legitimate interests;
• legal obligations;
• consent;
• protection of legal rights; or
• another lawful basis permitted by applicable law.

Where ApexCM processes information solely on behalf of a business customer, that customer may be responsible for determining the applicable legal basis.

27. BASE44

ApexCM is built using Base44 infrastructure.

Base44 may provide functions including:

• hosting;
• backend infrastructure;
• authentication;
• database services;
• file storage;
• application functionality;
• AI gateway functionality;
• communications capabilities; and
• related platform services.

Accordingly, Base44 may process information necessary to support ApexCM.

28. STRIPE

ApexCM uses Stripe for payment-related functionality.

Stripe may process:

• customer information;
• billing details;
• payment-card information;
• bank/payment information;
• payment amounts;
• transaction metadata; and
• related information.

ApexCM generally stores payment identifiers rather than complete payment-card information.

29. RESEND

ApexCM may use Resend to deliver transactional email.

Resend may process:

• recipient email address;
• subject;
• email body;
• attachments; and
• delivery information.

30. TWILIO

Where SMS functionality is used, ApexCM may use Twilio.

Twilio may process:

• recipient telephone number;
• message content;
• delivery information; and
• technical metadata.

31. GOOGLE PLACES

ApexCM may use Google Places for address autocomplete.

Google may receive:

• address-query text;
• place identifiers; and
• associated technical information.

32. AI PROVIDERS

AI features may involve third-party AI providers through Base44-supported infrastructure.

Relevant images, text, prompts, and contextual data may be processed to perform:

• OCR;
• categorization;
• floor-plan analysis;
• takeoff analysis;
• estimate generation; and
• related AI functions.

33. SOCIAL AUTHENTICATION PROVIDERS

Where enabled, authentication may use providers such as:

• Apple;
• Google;
• Microsoft; and
• GitHub.

Those providers may process information according to their own privacy practices.

34. GOOGLE FONTS AND WEB RESOURCES

Web resources such as Google Fonts may receive ordinary technical request information, including an IP address, when a browser retrieves a resource.

35. ACCOUNTING INTEGRATIONS

A workspace may configure an external accounting integration.

If configured, information transmitted may include relevant:

• workspace data;
• projects;
• client information;
• worker information;
• names;
• emails;
• roles;
• pay rates;
• labor records; and
• related synchronization data.

ApexCM transmits such information only when the relevant integration is configured and used.

36. DISCLOSURE TO OTHER WORKSPACE USERS

Information may be visible to authorized users in the same workspace according to access controls.

Depending on role, this may include:

• projects;
• customers;
• receipts;
• expenses;
• estimates;
• worker information;
• timesheets;
• documents;
• payments;
• messages; and
• other workspace records.

Workspace owners are responsible for assigning appropriate roles.

37. DISCLOSURE TO EXTERNAL CUSTOMERS

ApexCM may disclose records to customers through secure or tokenized portal links.

A customer may receive access to records intended for that customer, including:

• estimates;
• invoices;
• payment requests;
• change orders;
• attachments;
• messages; and
• related transaction information.

38. SERVICE PROVIDERS

We may disclose personal information to service providers performing functions on our behalf, including providers supporting:

• infrastructure;
• hosting;
• database services;
• storage;
• security;
• authentication;
• payments;
• email;
• SMS;
• AI;
• address lookup;
• support;
• analytics;
• backup;
• accounting integrations; and
• related technology.

Service-provider access is intended to be limited to what is reasonably necessary for their functions.

39. BUSINESS TRANSFERS

If Apexcm LLC becomes involved in a:

• merger;
• acquisition;
• financing;
• reorganization;
• bankruptcy;
• sale of assets; or
• similar transaction,

information may be disclosed or transferred as part of that transaction, subject to applicable law.

40. LEGAL DISCLOSURES

ApexCM may preserve or disclose information where reasonably necessary to:

• comply with law;
• respond to lawful legal process;
• comply with court orders;
• respond to valid governmental requests;
• investigate fraud;
• protect ApexCM;
• protect users;
• protect third parties;
• enforce contracts;
• defend legal claims;
• prevent security threats; or
• address serious harm.

41. SALE OF PERSONAL INFORMATION

ApexCM does not currently sell personal information for monetary consideration.

Because privacy laws may define "sale" or "sharing" differently, ApexCM will evaluate and update disclosures if future business practices change.

42. TARGETED ADVERTISING

ApexCM does not currently use the audited application for third-party behavioral or targeted advertising.

If ApexCM introduces such functionality, we will update this Policy and implement legally required choices before or when required.

43. DATA SECURITY

ApexCM uses reasonable administrative, technical, and organizational safeguards designed to protect information.

Current architecture may include:

• Base44-managed authentication;
• role-based permissions;
• workspace-scoped authorization;
• row-level security;
• server-side access checks;
• private file storage by default;
• signed file URLs;
• HTTPS/TLS;
• token expiration;
• restricted administrative functionality;
• server-side secret management;
• audit logging; and
• payment processing through Stripe.

44. NO GUARANTEE OF SECURITY

No online system is completely secure.

ApexCM cannot guarantee that:

• unauthorized access will never occur;
• data will never be lost;
• systems will never be compromised;
• third-party providers will never experience incidents; or
• backups will always be recoverable.

Users are responsible for securing their credentials, devices, personnel, workspace access, exports, and backups.

45. BACKUPS

ApexCM may provide backup/export functionality.

A backup may contain personal information and business information present in supported data at the time the backup is created.

Depending on the feature, backups may include categories of information such as:

• projects;
• receipts;
• expenses;
• workers;
• customers;
• contracts;
• change orders;
• invoices;
• payments;
• tasks;
• documents;
• audit records;
• comments;
• notifications;
• roles; and
• other supported database information.

ApexCM does not represent that literally every binary file, attachment, or future data type is included unless technically supported and confirmed.

46. ENCRYPTED BACKUPS

Where supported backup functionality uses customer-controlled encryption:

• the customer selects or controls the passphrase;
• ApexCM does not store the customer's backup encryption passphrase;
• ApexCM cannot retrieve a lost passphrase; and
• loss of the passphrase may make the backup impossible to decrypt or restore.

47. CUSTOMER-CONTROLLED BACKUPS

When a backup is downloaded or exported into customer control, the customer becomes responsible for:

• storage;
• security;
• encryption;
• access controls;
• confidentiality;
• loss prevention;
• legal compliance; and
• authorized disclosure.

48. THIRD-PARTY STORAGE

Where a customer stores an ApexCM backup using customer-connected third-party storage, the customer is responsible for:

• the third-party account;
• access;
• permissions;
• capacity;
• credentials;
• provider security; and
• provider availability.

The independent provider's privacy policy applies to its processing.

49. DATA RETENTION

ApexCM retains information for periods reasonably necessary for the purposes described in this Policy.

Following account deletion or termination, ApexCM may retain information for up to one year where reasonably necessary for:

• backups;
• recovery;
• security;
• fraud prevention;
• legal compliance;
• financial recordkeeping;
• dispute resolution;
• enforcing agreements;
• maintaining business continuity; and
• protecting legal rights.

This one-year period is ApexCM's current provisional retention framework and may be refined as formal retention procedures develop.

50. EXCEPTIONS TO THE RETENTION PERIOD

Information may be retained for longer than one year where:

• applicable law requires or permits longer retention;
• a legal hold applies;
• litigation or a dispute is pending;
• necessary financial records must be preserved;
• fraud/security investigations remain active;
• contractual obligations require retention;
• information remains in backups awaiting normal expiration; or
• a service provider lawfully retains data according to its own requirements.

Information may also be deleted earlier where appropriate.

51. ACCOUNT DELETION

Users may use supported account-deletion functionality.

Deletion may depend on workspace ownership.

For example:

• a sole workspace owner may need to transfer ownership or delete the workspace;
• data may remain where ownership is transferred;
• business records may remain in a shared workspace after an individual leaves;
• identity references may be anonymized where supported; and
• customer-facing links associated with deleted records may stop working.

52. THIRD-PARTY RETENTION

Some service providers maintain data according to their own lawful retention obligations.

For example, payment processors may retain transaction records to comply with:

• financial regulations;
• fraud-prevention requirements;
• payment-network obligations;
• tax requirements; or
• legal obligations.

ApexCM cannot require an independent provider to delete records that it must lawfully retain.

53. PRIVACY RIGHTS

Depending on applicable law, individuals may have rights to:

• request access;
• obtain information about processing;
• correct information;
• delete information;
• obtain a portable copy;
• restrict processing;
• object to certain processing;
• withdraw consent;
• opt out of certain sales;
• opt out of certain sharing;
• opt out of targeted advertising;
• appeal certain privacy-request decisions; and
• lodge complaints with regulators.

Rights vary by jurisdiction and may be subject to exceptions.

54. SUBMITTING A PRIVACY REQUEST

Privacy requests may be sent to:

privacy@apexcm.pro

Please include sufficient information to identify the applicable account or relationship.

ApexCM may request additional information reasonably necessary to verify identity and protect information against unauthorized disclosure.

55. AUTHORIZED AGENTS

Where applicable law permits an authorized agent to submit a privacy request, ApexCM may request evidence of the agent's authority and may independently verify the identity of the individual concerned.

56. REQUESTS INVOLVING CUSTOMER-CONTROLLED DATA

If ApexCM processes information on behalf of a business customer, ApexCM may direct a privacy request to that customer.

ApexCM may assist customers with legally required requests where appropriate.

57. CALIFORNIA PRIVACY DISCLOSURES

Where applicable California privacy law applies, ApexCM may process categories such as:

• identifiers;
• customer-record information;
• commercial information;
• internet/network activity;
• professional/employment information;
• location/address information;
• sensitive personal information contained in worker or uploaded records; and
• inferences or AI-generated information depending on use.

Qualifying California residents may have rights provided by applicable law.

ApexCM does not currently represent that it sells personal information for monetary consideration.

58. SENSITIVE PERSONAL INFORMATION

Certain ApexCM customers may upload information potentially treated as sensitive under applicable law, including:

• worker identification documents;
• tax documents;
• payment-related information;
• date of birth;
• employee information;
• authentication-related information; and
• other sensitive material.

ApexCM customers are responsible for limiting collection and access to information reasonably necessary for legitimate purposes.

59. VIRGINIA AND OTHER U.S. STATES

Residents of Virginia and other U.S. states may have privacy rights where applicable state law applies and applicable thresholds are met.

Rights may include:

• access;
• correction;
• deletion;
• portability;
• opt-out rights; and
• appeals.

ApexCM will process legally applicable requests in accordance with governing law.

60. APPEALS

Where applicable law provides a right to appeal a privacy-request decision, an appeal may be submitted to:

privacy@apexcm.pro

Please identify the original request and explain the basis for the appeal.

61. EEA AND UK USERS

Where the GDPR or UK GDPR applies, individuals may have rights such as:

• access;
• rectification;
• erasure;
• restriction;
• portability;
• objection;
• withdrawal of consent; and
• complaint to an applicable supervisory authority.

These rights are subject to applicable law.

62. INTERNATIONAL TRANSFERS

ApexCM and its service providers may process information in the United States and other jurisdictions.

If information is transferred from a jurisdiction restricting international transfers, ApexCM will use an appropriate mechanism where required by applicable law.

Users should understand that laws in destination jurisdictions may differ from laws in their home jurisdiction.

63. CHILDREN

ApexCM is intended for adults and business use.

Users must be at least 18 years old to create or use an ApexCM account.

ApexCM is not directed to children under 18.

If ApexCM learns that a child has created an account contrary to these Terms, ApexCM may take appropriate action.

64. TRANSACTIONAL EMAIL

ApexCM may send transactional emails such as:

• account invitations;
• verification communications;
• password-reset messages;
• estimates;
• invoices;
• change orders;
• payment communications;
• clarification messages;
• reports;
• security communications; and
• service notices.

These communications are generally necessary or related to requested platform functionality.

65. MARKETING EMAIL

The current audited application does not operate a marketing-email campaign.

If ApexCM begins sending marketing communications, appropriate notice and opt-out mechanisms will be implemented as required.

66. SMS COMMUNICATIONS

Where enabled, ApexCM may send transactional SMS communications concerning:

• estimates;
• change orders;
• payments;
• portal links; and
• related service activity.

Current audited functionality does not include recurring marketing SMS campaigns.

If marketing SMS is introduced, ApexCM will implement legally required consent and opt-out procedures.

67. CUSTOMER RESPONSIBILITY FOR CONTACT INFORMATION

Businesses using ApexCM are responsible for ensuring that they have appropriate rights or authority to enter customer contact information and request communications.

ApexCM relies on those businesses to provide lawful instructions concerning their customers.

68. AUTOMATED PROCESSING

AI and automated functionality may be used to:

• recognize receipt information;
• categorize expenses;
• analyze floor plans;
• identify project information;
• generate takeoff information; and
• assist with estimate generation.

Automated output may be inaccurate.

Users are responsible for human review.

69. NO AUTOMATED HIGH-IMPACT DECISIONS INTENDED

ApexCM does not intend its AI features, standing alone, to make legally binding determinations concerning matters such as:

• employment eligibility;
• credit;
• insurance;
• housing;
• criminal justice;
• healthcare; or
• other similarly significant rights.

Customers must not use ApexCM AI output unlawfully.

70. THIRD-PARTY WEBSITES

The Services may contain links to third-party sites or services.

ApexCM is not responsible for independent third-party privacy practices.

You should review their privacy policies before providing information.

71. DATA ACCURACY

ApexCM relies substantially on information submitted by users and customers.

Users are responsible for ensuring that submitted records are accurate and appropriately updated.

ApexCM does not independently verify every:

• receipt;
• worker record;
• customer record;
• estimate;
• address;
• invoice;
• floor plan;
• payment record; or
• uploaded document.

72. SECURITY INCIDENTS

If ApexCM becomes aware of a security incident affecting personal information, ApexCM will investigate and provide notices where required by applicable law.

The existence of this provision does not constitute a guarantee that security incidents will never occur.

73. DO NOT TRACK AND PREFERENCE SIGNALS

There is no universally applicable standard for all browser "Do Not Track" signals.

Where applicable law requires recognition of a legally recognized opt-out preference signal, ApexCM will address the signal as required.

74. CHANGES TO THIS PRIVACY POLICY

ApexCM may update this Privacy Policy to reflect changes in:

• law;
• Services;
• features;
• service providers;
• security;
• integrations;
• AI functionality;
• business practices; or
• data practices.

A revised Policy will display an updated effective date.

Where legally required, ApexCM will provide additional notice or obtain consent.

75. CONTACT

For privacy questions or requests:

Apexcm LLC

d/b/a ApexCM

3501 Coxcomb Mews

Woodbridge, VA 22193

United States

Privacy Email: privacy@apexcm.pro

For legal matters:

Said@apexcm.pro

For support:

Support@Apexcm.pro

Website:

https://apexcm.pro

76. CONTACTING A REGULATOR

Where applicable law gives you the right to complain to a privacy or data-protection authority, you may exercise that right.

We encourage you to contact us at privacy@apexcm.pro first so that we can attempt to address the issue.

77. FINAL PRIVACY NOTICE

By using ApexCM, you acknowledge that personal information will be processed as described in this Privacy Policy, subject to your applicable legal rights.

END OF PRIVACY POLICY