RESILIENCE / H.O.M.E.

RESILIENCE H.O.M.E. — Data Processing Addendum (DPA)

1. Parties and roles

The Customer is the organization purchasing H.O.M.E., deciding which records to store, their lawful purposes and who may access them. To the extent the Customer determines processing purposes and means, it acts as the controller. RESILIENCE, the brand under which Alberto Antonio Del Paso Flores (RFC PAFA810117RT4) supplies the platform at https://crm.resilience.mx, acts as processor for personal data processed on the Customer's behalf within this Addendum.

RESILIENCE separately acts as a controller for its own account holder, billing, support and compliance records under the RESILIENCE Privacy Notice.

“Customer Data” means third-party personal information entered, connected or generated within the Customer's CRM on its instructions, excluding information RESILIENCE controls independently.

2. Subject matter and duration

Processing covers hosting, organization, retrieval, transmission and, where actually enabled, functional analysis of CRM contacts, lead pipelines, messaging, properties and developments, campaign reports, authorized integrations and QR/Walk-ins records within the subscribed plan.

Processing continues throughout the service relationship and for a justified post-termination period required to return, retain, block or erase data under documented instructions and law.

3. Documented instructions

RESILIENCE will process Customer Data only on documented Customer instructions communicated in this Addendum, the Terms, configuration by authorized users or valid Customer requests, unless law requires otherwise. It will notify the Customer where an instruction appears unlawful, when legally permitted.

RESILIENCE will not sell Customer contact databases, use Customer Data for its unrelated marketing or disclose Customer Data to other customer organizations. Third-party processing and automation must remain within authorized services. Exceptional employee access for support/security will be limited to what is necessary and protected by confidentiality controls.

4. Customer responsibilities

The Customer must collect and use personal information lawfully, provide relevant privacy notices and obtain applicable consent or other legal authority; determine purposes and retention periods; respond to data subject requests; and administer staff access and external integrations.

The Customer must separately assess any sensitive or children's data. H.O.M.E. is not intended for routine collection of such information. Specialized processing requires appropriate legal grounds and safeguards. The Customer must avoid unrestricted access grants.

5. Technical and organizational measures

RESILIENCE will apply appropriate measures for the contracted service and risks, including account authentication and organizational/role-based permissions, logical workspace segregation, secure transmission where applicable, restricted key management, controlled changes and privileged access, relevant audit logging, incident response and available recovery mechanisms.

Applicable safeguards will be described in the Security Schedule, reflecting the infrastructure used to provide the Service and the processing activities authorized by the Customer.

6. Authorized personnel and confidentiality

Access to Customer Data will be limited to personnel or contractors with a legitimate need for service operations, support or security and subject to confidentiality duties and proportionate privileges.

7. Subprocessors

The Customer authorizes only the subprocessors necessary for service delivery and documented in an updated contractual register. Potential categories include web functions/hosting (Vercel), database/authentication infrastructure (Supabase) and transactional communications where actually used. Payment handling through Stripe must be distinguished from vendors with access to customer CRM content.

A subprocessor schedule must identify the legal name, service, data categories, relevant country/region and international transfer mechanism as applicable. Integrations voluntarily connected by the Customer do not constitute blanket authorization for unrelated vendors. Material additions will be notified as required by law and contract.

8. International transfers

Cross-border processing must use applicable contractual safeguards and any legally required transfer basis or consent. Customers subject to the EU GDPR or another specific international framework may require supplementary terms, safeguards or appropriate transfer instruments before processing regulated data. This proposal does not replace those instruments.

9. Data subject rights and assistance

The Customer is responsible for determining responses to access, rectification, erasure, objection and other rights requests concerning Customer contacts. RESILIENCE will provide reasonable, technically available assistance to locate, export, correct or remove Customer Data upon authenticated documented instructions, without disclosing it to unauthorized parties. If RESILIENCE receives a request directly concerning Customer-controlled records, it will route or refer the request as appropriate rather than independently deciding the processing purpose.

10. Security incidents

For a confirmed incident affecting Customer Data, RESILIENCE will inform the Customer's designated contact without undue delay after obtaining sufficient information and provide reasonable details of the known nature, impact, mitigation and ongoing updates, consistent with applicable legal duties. The Customer makes controller notifications as required by law, with appropriate RESILIENCE assistance.

11. Return, export and erasure

Upon termination, the Customer may request return/export of Customer Data in reasonably accessible formats and deletion, except where legal retention or blocking is necessary. Requests are handled through available formats and procedures, subject to security, documented Customer instructions and legal retention obligations.

Canceling a plan, removing an item from the interface and permanently erasing backup copies are distinct operations.

12. Information and cooperation

RESILIENCE will provide reasonable information required to assess its compliance, subject to security and confidentiality measures protecting other customers. The parties will cooperate with legitimate legal requests. Material changes to processing or subprocessors will be communicated under the agreed method.

13. Precedence, effectiveness and contact

For Customer Data processing, this DPA controls in case of conflict with general SaaS Terms; otherwise the Terms and any individual CUSTOM order apply. Nothing excludes nonwaivable statutory rights.

Privacy assistance: support@resilience.mx. Contract matters: connect@resilience.mx.

Schedule A. Processing description

Schedule B. Subprocessors and security

RESILIENCE will provide information about providers actually involved in processing, their functions and applicable safeguards in accordance with this Addendum.

Back to H.O.M.E.

RESILIENCE Cloud