ApexPoster Legal

Data Processing Agreement

Version 1.0 — July 2026

This Data Processing Agreement (“DPA”) forms part of the ApexPoster Terms of Service (the “Agreement”) between Apex Technology Group, Inc. (“Apex,” “Processor”) and the customer that accepted them (“Customer,” “Controller”). It governs Apex's processing of Personal Data on Customer's behalf in connection with the ApexPoster services (the “Services”).

This DPA applies automatically where Customer is subject to the GDPR, the UK GDPR, the Swiss FADP, the CCPA as amended, or a comparable data protection law. Customer may also request a countersigned copy by emailing support@apexposter.net. Where this DPA conflicts with the Agreement, this DPA controls as to the processing of Personal Data.

In plain terms. You decide what goes on your screens and who can see your dashboard. We store it, deliver it, and keep it secure — and we don't do anything else with it. If a regulator or an individual comes to you about content on your screens, that's yours to answer, and we'll help.

1. Definitions

2. Roles of the Parties

Customer is the Controller and Apex is the Processor with respect to Customer Personal Data. Customer determines the purposes and means of processing; Apex processes only as described in this DPA and on Customer's documented instructions.

Apex acts as an independent Controller for a limited set of data that it determines the purposes of itself — account registration and identity, billing and tax records, security and abuse-prevention logs, support correspondence, and aggregate service metrics. That processing is governed by the ApexPoster Privacy Policy, not by this DPA.

Under the CCPA, Apex is a “service provider.” Apex does not sell or share Personal Data, does not retain, use, or disclose it for any purpose other than performing the Services specified in the Agreement, and does not combine it with Personal Data received from other sources except as permitted for a service provider. Apex certifies that it understands and will comply with these restrictions.

3. Customer's Responsibilities

Customer is responsible for, and warrants that:

Prohibited categories. Customer must not upload to the Services any payment card data, government identification numbers, financial account numbers, health or medical records, biometric identifiers, or precise geolocation of individuals. The Services are not designed or assessed for these categories, and Apex has no obligation or liability with respect to them.

4. Apex's Processing Obligations

Apex will:

5. Subprocessors

Customer provides general authorization for Apex to engage Subprocessors. The Subprocessors engaged as of the version date of this DPA are listed in Annex III.

Apex will impose on each Subprocessor, by written contract, data protection obligations no less protective than those in this DPA, and remains fully liable to Customer for its Subprocessors' performance.

Apex will give Customer at least thirty (30) days' notice before engaging a new Subprocessor that processes Customer Personal Data, by email to the account's notification address. Customer may object on reasonable data protection grounds within that period. If the parties cannot resolve the objection, Customer may terminate the affected Services and receive a pro-rata refund of prepaid fees for the terminated portion of the subscription term, as its sole and exclusive remedy.

6. Security

Apex will implement appropriate technical and organizational measures to ensure a level of security appropriate to the risk, taking into account the state of the art, the costs of implementation, and the nature, scope, context, and purposes of processing. The measures in place as of the version date of this DPA are described in Annex II.

Apex may update those measures over time, provided it does not materially decrease the overall level of security.

7. Personal Data Breach

Apex will notify Customer without undue delay, and in any event within seventy-two (72) hours, after becoming aware of a Personal Data Breach affecting Customer Personal Data. The notification will describe, to the extent known: the nature of the breach and the categories and approximate number of Data Subjects and records affected; the likely consequences; and the measures taken or proposed to address it and mitigate its effects. Where the information is not all available at once, Apex will provide it in phases as it is obtained.

Apex will provide reasonable assistance to Customer in meeting Customer's own notification obligations to Supervisory Authorities and Data Subjects. Apex's notification is not an acknowledgment of fault or liability.

8. Assistance to Customer

Taking into account the nature of the processing, Apex will:

9. Audit

Apex will make available to Customer the information reasonably necessary to demonstrate compliance with this DPA, and will respond to reasonable written security questionnaires no more than once in any twelve-month period.

Where Data Protection Laws require an on-site audit and the information provided is not sufficient, Customer may audit Apex's compliance, subject to: reasonable prior written notice of at least thirty (30) days; no more than once in any twelve-month period, except where required by a Supervisory Authority or following a Personal Data Breach; conduct during business hours without unreasonable disruption; the auditor being bound by confidentiality and not being a competitor of Apex; scope limited to systems and records relevant to Customer Personal Data and excluding other customers' data; and Customer bearing its own and Apex's reasonable costs.

10. International Transfers

Apex processes Customer Personal Data in the United States. Customer authorizes this transfer.

Where Customer Personal Data is transferred from the European Economic Area, the United Kingdom, or Switzerland to a country without an adequacy decision, the SCCs are incorporated into this DPA by reference and apply as follows:

For UK transfers, the UK Addendum applies to the SCCs, with Tables 1 to 3 populated by the Annexes to this DPA, and Table 4 specifying that neither party may terminate under Section 19 of the Addendum. For Swiss transfers, references to the GDPR are read as references to the FADP, the competent authority is the Swiss Federal Data Protection and Information Commissioner, and “member state” is read to include Switzerland.

11. Deletion and Return

Customer may access, export, and delete Customer Personal Data throughout the term of the Agreement using the functionality of the Services.

On termination or expiry of the Agreement, Apex will delete Customer Personal Data within thirty (30) days, except to the extent it is required to retain it by law. Where Apex retains data under that exception, this DPA continues to apply to it. Backups are overwritten on a rolling basis in the ordinary course. Content already cached on Customer's own devices is outside Apex's control and is Customer's responsibility to remove.

12. Liability

Each party's liability arising out of or related to this DPA is subject to the limitations and exclusions of liability set out in the Agreement. Nothing in this DPA limits a Data Subject's rights under Data Protection Laws or either party's liability to a Supervisory Authority.

13. Term and General

This DPA takes effect when Customer accepts the Agreement and continues until Apex has ceased all processing of Customer Personal Data. Provisions that by their nature should survive will survive.

Apex may update this DPA where required by a change in Data Protection Laws, in a Supervisory Authority decision, or in the SCCs themselves, and will give Customer reasonable notice of any material change. Except as stated in Section 2, and other than as to the processing of Personal Data, the Agreement remains unchanged and in full force.

Annex I — Details of Processing

A. List of Parties

Data exporter (Controller): the Customer identified in the ApexPoster account, at the contact details held on that account. Its activities relevant to the transfer are its use of a digital signage service to display content on screens it operates.

Data importer (Processor): Apex Technology Group, Inc., a Delaware corporation. Contact: support@apexposter.net. Its activities relevant to the transfer are the provision of the ApexPoster hosted digital signage service.

B. Description of Transfer

ItemDetail
Categories of Data Subjects Customer's Authorized Users (employees, contractors, agents who access the dashboard); individuals whose Personal Data Customer chooses to include in Customer Content or account configuration — for example staff appearing in displayed media, or people named on displayed notices
Categories of Personal Data Authorized User email addresses, names, account roles and permissions, and notification addresses; any Personal Data contained within media, playlists, layouts, screen names, tags, or feeds that Customer uploads or configures
Sensitive data None. Customer is prohibited from uploading special-category data under Section 3 of this DPA. No sensitive data is knowingly processed and no additional restrictions apply because none is contemplated
Frequency of transfer Continuous, for the duration of the Agreement
Nature of processing Collection, storage, organization, format conversion and thumbnail generation, transmission to Customer's paired display devices, retrieval, backup, and deletion
Purpose of processing Providing the ApexPoster hosted digital signage service to Customer under the Agreement, including hosting the dashboard, storing media, and distributing content to Customer's screens
Duration of processing The term of the Agreement, plus up to 30 days for deletion as set out in Section 11
Subprocessor processing As set out in Annex III, for the duration of the Agreement

C. Competent Supervisory Authority

The supervisory authority of the EEA member state in which the data exporter is established, or where the exporter is not established in the EEA, the authority of the member state in which its EU representative is established or in which the relevant Data Subjects are located.

Annex II — Technical and Organizational Measures

MeasureImplementation
Encryption in transit All dashboard, API, and player traffic is served over HTTPS with a valid certificate. Player applications require a valid certificate to connect
Encryption at rest Media storage and database volumes rely on the encryption-at-rest facilities of the underlying cloud provider
Authentication Dashboard identity is delegated to a dedicated identity provider. Apex does not store, receive, or have access to user passwords. Access is granted on presentation of a validated signed token
Device authentication Each display device holds a unique opaque identifier and a secret token issued at registration, and can retrieve content only for the account it is paired to
Access control Multi-tenant isolation enforced at the data layer by account scope; role-based permissions within an account; internal administrative access limited to personnel who require it
Pseudonymization Devices are identified by opaque generated identifiers not derived from and not linked to any individual
Payment data Payment card data is collected and held entirely by a PCI-DSS compliant payment processor and never transits or rests on Apex systems
Logging and auditability Server and application logging; an append-only audit record of billing-affecting events that no application endpoint may modify or delete
Availability and resilience Content is cached on display devices so screens continue playing during a loss of connectivity. Automated monitoring alerts on screens that stop reporting
Backup and recovery Regular backups of database and media storage, retained on a rolling basis
Deletion Operator-initiated account deletion removes database records, stored media and derivatives, and the sign-in identity, in a defined order that cancels any active subscription first and aborts if that step fails
Personnel Personnel with access to Personal Data are bound by confidentiality obligations
Subprocessor governance Written contracts imposing equivalent obligations; Apex remains liable for Subprocessor performance
Incident response Defined process for identifying, escalating, and notifying Personal Data Breaches within the timeframe in Section 7

Annex III — Subprocessors

SubprocessorPurposeData processedLocation
Google LLC (Firebase Authentication) Identity and authentication for the dashboard Authorized User email addresses, credentials, authentication events United States
Stripe, Inc. Payment processing, invoicing, tax, billing portal Billing contact name, email, address, payment method, subscription records United States
Amazon Web Services, Inc. Hosting, object storage for media, transactional email delivery All service data at rest and in transit, including Customer Content and outbound email United States
MongoDB, Inc. Database for account, screen, playlist, and media metadata Account and configuration records, including Authorized User details United States

This list is current as of the version date above. Changes are notified in accordance with Section 5.