Data Processing Agreement (DPA)

Data Processing Agreement (DPA)

Version 1.0 · November 16, 2026

Standard data-processing terms for PEER365 Self Service and Managed Services. This DPA takes effect through express incorporation or signature as described below. Engagement-specific processing, vendor and transfer details must be confirmed before applicable processing begins.

Privacy Policy · Terms of Service · Cookie Policy

1. Parties, scope and acceptance

This Data Processing Agreement (“DPA”), version 1.0 dated November 16, 2026, is offered by PEER365, LLC (“PEER365”) to the business identified in an accepted service order (“Customer”). It supplements the parties’ service agreement only when expressly incorporated into an accepted order, electronic agreement or separately signed DPA. Posting this document, browsing the website or making an inquiry does not alone execute a DPA or amend an existing agreement. The service order identifies the Customer, authorized contact and services. Before processing begins, the parties must confirm the processing particulars, approved subprocessors, applicable security arrangements and any required international-transfer terms in writing.

2. Roles and definitions

“Customer Personal Data” means personal data PEER365 processes on Customer’s behalf to provide the agreed services. Customer acts as controller/business and PEER365 as processor/service provider where those roles apply. If Customer is itself a processor, it must hold the controller’s authorization and pass down lawful instructions; PEER365 acts as its subprocessor. Applicable Data Protection Law means privacy and data-protection laws applicable to the particular processing, including the GDPR, UK GDPR and applicable US state laws where relevant. This DPA does not declare that every such law applies to every Customer. PEER365’s independent account administration, billing, security and business-contact processing is addressed in its Privacy Policy; that distinction does not permit repurposing Customer Personal Data.

3. Documented instructions and permitted purposes

PEER365 will process Customer Personal Data only on Customer’s documented lawful instructions to deliver the selected platform or managed services, including authorized website analysis, SEO/AEO/GEO optimization, content preparation and publication, campaign administration, reporting, support and security. Instructions comprise the accepted service scope, approved connection permissions, recorded configuration choices and subsequent written directions. PEER365 will not process data for incompatible purposes. If law requires other processing, PEER365 will notify Customer before processing unless legally prohibited. PEER365 will promptly inform Customer if it believes an instruction infringes applicable data-protection law and may suspend that instruction while the parties resolve it.

4. Customer responsibilities and service modes

Customer determines lawful purposes, legal bases, required notices and consents, and the accuracy and relevance of supplied data. Customer must authorize its connected accounts and ensure its instructions and disclosures are lawful. For Self Service, PEER365 performs the agreed initial setup and handover; Customer’s team controls subsequent platform use and approvals. For Managed Services, PEER365 operates agreed workflows within Customer’s instructions. Automation settings do not remove either party’s data-protection obligations. Customer must minimize data in prompts and content, use supported access permissions rather than shared passwords, and authorize publication separately. Content intentionally published becomes public; that authorization does not authorize publication of unrelated personal data.

5. Confidentiality and personnel

PEER365 will restrict access to authorized personnel who need it for the services, ensure they are bound by confidentiality obligations or an appropriate statutory duty, and provide instructions appropriate to their responsibilities. Confidentiality obligations continue after access or services end. PEER365 will maintain appropriate access-removal procedures for personnel no longer requiring access.

6. Security and processing safeguards

PEER365 will implement and maintain technical and organizational measures appropriate to processing risks and applicable law, including Article 32 where applicable. The engagement’s security schedule must describe the measures actually applicable to its systems: access controls and least privilege; authentication and credential handling; protection of data in transit and at rest appropriate to risk; vulnerability and update management; logging and incident response; backup, restoration and continuity arrangements; secure deletion; and periodic evaluation of effectiveness. Measures will reflect the nature, scope, context and purposes of processing, available technology and risks to individuals. No certification, specific hosting region, universal encryption coverage or recovery deadline is represented by this page. Customer may request the applicable security information before authorizing processing; unsupported requirements must be resolved before data is supplied.

7. AI tools and public content

Customer Personal Data may be supplied to AI services only when necessary for an instructed task and through approved processing arrangements. PEER365 will minimize inputs, limit access and configure available retention and training controls according to the agreed scope. PEER365 will not use Customer Personal Data to train general-purpose AI models for its own purposes or authorize a provider to do so without a separate lawful written arrangement. This is a restriction on permitted processing, not a representation that every vendor currently offers suitable terms. Where a provider’s terms or controls cannot meet the agreed restrictions, that provider must not receive the affected Customer Personal Data. AI outputs require appropriate factual, confidentiality and publication review. Special-category data, health records, children’s data, government identifiers, payment-card data and authentication secrets must not be placed in ordinary prompts or forms; any necessary restricted-data processing requires a separate written assessment and authorization first.

8. Subprocessors and connected services

PEER365 may appoint subprocessors only with Customer’s prior specific or general written authorization. Before processing, PEER365 will provide the applicable register stating each subprocessor’s legal identity, function, processing location and relevant data categories, including infrastructure, support and AI providers actually used for that engagement. A category list alone does not establish authorization. Under general authorization, PEER365 will give at least 30 days’ advance written notice of intended additions or replacements and allow objections on reasonable data-protection grounds before the change. The parties will seek an alternative; if unresolved, the affected processing will not move to the disputed provider and the affected service may be ended under the agreement. PEER365 will impose equivalent applicable data-protection obligations by written contract and remains responsible for its subprocessors’ performance of those obligations as required by law. Customer-controlled advertising, analytics and other platforms may act independently under their own terms; their actual role must be assessed rather than assumed. No unverified vendor list is incorporated by this page.

9. International transfers

Customer authorizes processing only in the locations documented for the engagement. PEER365 will not make a restricted international transfer without Customer’s documented instructions and a valid mechanism required by applicable law. Where needed, the parties will execute the appropriate EU Standard Contractual Clauses, UK Addendum or IDTA, complete required annexes and assessments, and agree supplementary safeguards before the transfer. This DPA does not itself execute those instruments or claim that PEER365 or any provider holds a Data Privacy Framework certification. If lawful safeguards are unavailable, the affected transfer must not proceed.

10. Personal-data incidents

PEER365 will notify Customer without undue delay after becoming aware of a personal-data breach affecting Customer Personal Data. It will provide available information on the nature of the breach, affected categories and approximate numbers where known, likely consequences, mitigation and a contact for follow-up; updates may be supplied in phases without delaying initial notice. PEER365 will take reasonable containment and remediation steps, preserve relevant evidence and assist Customer with legally required notifications. Customer determines notices to individuals and regulators unless law requires PEER365 to act. Notification does not require a final investigation or an admission of liability.

11. Individual requests and compliance assistance

PEER365 will promptly relay requests concerning Customer Personal Data to Customer and will not respond substantively except on instructions or as required by law. Taking account of the nature of processing and information available, PEER365 will assist Customer through appropriate measures with access, correction, deletion, portability, restriction, objection and other applicable rights, security obligations, breach notifications, data-protection impact assessments and regulator consultations. Assistance must allow Customer to meet applicable legal deadlines. Any charges for additional assistance must be agreed and must not prevent legally required cooperation or correction of PEER365’s own breach.

12. Information, audits and records

PEER365 will make available information necessary to demonstrate compliance with this DPA and applicable processor obligations and allow and contribute to audits and inspections by Customer or its qualified auditor. The parties may coordinate reasonable notice, confidentiality, scope and methods to protect other customers and avoid unnecessary disruption, without preventing legally required audits or urgent investigation of a material incident. Documentation may satisfy a request where adequate; it does not replace a legally necessary inspection. PEER365 will maintain processing records required by applicable law and cooperate with competent supervisory authorities.

13. Return, deletion and retention

At the end of the relevant processing, PEER365 will, at Customer’s choice, return or securely delete Customer Personal Data and delete existing copies unless applicable law requires retention. The engagement must document export formats, request procedures, active-system deletion timing and backup-expiry periods before processing starts. Pending deletion, retained copies remain protected, restricted to permitted retention purposes and unavailable for ordinary use. Backups must be put beyond ordinary use and deleted on the documented cycle; restored data must remain subject to deletion instructions. PEER365 will provide confirmation on reasonable request. Cancellation does not itself erase Customer-controlled websites or publicly published work. Customer can instruct removal of personal data within PEER365’s control; copies held independently by search engines or other third parties require separate handling. Independent billing or legal records remain subject to their own lawful retention requirements.

14. US service-provider and contractor terms

Where applicable US law treats PEER365 as a service provider, contractor or processor, Customer discloses Customer Personal Data only for the specific service purposes in section 3 and the accepted processing schedule. PEER365 will not sell or share that data as defined by applicable law, retain, use or disclose it outside those purposes or the direct business relationship except as law permits, or combine it with personal information from other customers or its own interactions except as legally permitted for the instructed services. PEER365 will provide the level of privacy protection required by applicable law, comply with applicable restrictions, and notify Customer if it can no longer meet them. Customer may take reasonable steps to verify compliant use and stop and remediate unauthorized use. Where legally required, PEER365 certifies that it understands and will comply with these restrictions. Customer-authorized advertising activity that cannot meet service-provider restrictions requires a separate lawful role and arrangement before disclosure.

15. Order of precedence, changes and contact

For Customer Personal Data, this DPA prevails over conflicting general service terms; mandatory law and executed transfer clauses prevail where required. Commercial liability provisions in the accepted agreement apply only to the extent lawful and do not remove statutory rights or direct responsibilities. This DPA creates no new liability cap or waiver. Material changes to an accepted DPA require agreement or another legally valid amendment process; a website edit alone does not retroactively alter it. Contact PEER365, LLC at mark@peer365.com, subject “DPA / Data Protection,” or write to 507 Rosewood Dr, Shenandoah, TX 77381; telephone (832) 713-6365.

Schedule A — Processing particulars

Subject matter: the Customer website, connected business accounts and selected software or managed marketing services identified in the order. Duration: the agreed service term and documented return/deletion period. Operations: authorized collection, access, organization, analysis, generation, storage, retrieval, alteration, disclosure by approved publication, reporting, export and deletion. Individuals: Customer personnel, business contacts, prospects, customers, website visitors and reviewers, only as relevant to the instructed service. Data: business contact details, supplied communications, authorized website content, account identifiers, campaign and search-performance information, and online/device identifiers where lawfully enabled. Sensitive or restricted data is excluded unless separately agreed. Customer rights and obligations: sections 3, 4 and 9–13. The order and written schedule must narrow these categories to actual processing and identify the Customer and authorized contacts.

Schedule B — Required engagement confirmations

Before Customer Personal Data is processed, record: (1) approved subprocessor legal entities, purposes and locations; (2) security measures applicable to the service and parties’ responsibilities; (3) retention, export, deletion and backup periods; (4) authorized AI providers and training/retention restrictions; (5) any international-transfer instruments and completed annexes; and (6) incident and privacy contacts. Obtain the completed schedule from PEER365 before sharing restricted data or authorizing a transfer that requires additional safeguards. Publication of this standard DPA does not establish completion of these engagement-specific confirmations.