RCONS

Data Processing Agreement

Version 2026-11-21. Effective 21 November 2026.

RCONS | Outsourcing agreement under Rule X of the Implementing Rules of the Data Privacy Act of 2012

Every RCONS customer and pilot user accepts or signs this Agreement before real project data that names individuals is loaded.

This Agreement is between the customer that accepts it when signing up for RCONS, or signs it with an Order Form or Pilot Agreement ("Customer"), and Robles Technologies Corp., with office at 27 T. Santiago St., Canumay West, Valenzuela City 1443 ("RTC").

1. Scope and precedence

1.1 This Agreement applies whenever RTC processes personal data for the Customer in providing RCONS ("Service") under the RCONS Terms of Service or an RCONS Pilot Agreement ("Main Agreement").

1.2 On the processing of personal data, this Agreement prevails over the Main Agreement.

1.3 Terms defined in the Data Privacy Act of 2012 (Republic Act No. 10173), its Implementing Rules and National Privacy Commission issuances ("Privacy Laws") have the same meaning here.

2. Roles

2.1 The Customer is the personal information controller. RTC is the personal information processor.

2.2 RTC is a controller, not a processor, for its own account, billing and security log data. RTC's Privacy Notice covers that data.

2.3 Annex 1 describes the subject matter, duration, nature and purpose of the processing, the types of personal data, and the categories of data subjects.

3. Instructions

3.1 RTC will process Customer personal data only on the Customer's documented instructions. The Main Agreement, this Agreement, and the Customer's configuration and use of the Service are those instructions.

3.2 RTC will not use Customer personal data for its own purposes, sell it, or disclose it, except as this Agreement allows or the law requires.

3.3 RTC will tell the Customer promptly if it believes an instruction breaks the Privacy Laws. RTC may pause that instruction until the Customer confirms or changes it.

3.4 If a law or lawful order requires RTC to disclose Customer personal data, RTC will notify the Customer before disclosing, unless the law forbids notice.

4. Customer obligations

4.1 The Customer confirms that it has a lawful basis for the personal data it puts into the Service, and that it has given its data subjects the information the Privacy Laws require.

4.2 The Customer is responsible for the accuracy of the data, for the roles and access it grants to its users and outside collaborators, and for its own registration and compliance with the National Privacy Commission.

4.3 The Customer will not put into the Service government ID numbers, health records, biometric data or other categories that Annex 1 does not cover without RTC's written agreement.

5. People who handle the data

5.1 RTC will limit access to Customer personal data to personnel who need it to provide the Service.

5.2 RTC will bind those personnel by written confidentiality obligations that continue after their engagement ends, and will train them in privacy and security.

5.3 RTC has designated Kyan Lumanog as its Data Protection Officer, reachable at [email protected].

6. Security

6.1 RTC will implement and maintain the organizational, physical and technical measures in Annex 2, which are designed to meet the requirements of the Privacy Laws, including NPC Circular No. 2023-06.

6.2 RTC may update those measures, provided the overall level of protection does not go down.

7. Sub-processors

7.1 The Customer authorizes RTC to use the sub-processors listed in Annex 3.

7.2 RTC will give at least 30 days' notice before adding or replacing a sub-processor. The Customer may object on reasonable data protection grounds within 15 days. If the parties cannot resolve the objection, the Customer may terminate the Service and receive a pro-rated refund of prepaid fees.

7.3 RTC will bind each sub-processor by written contract to data protection obligations no less protective than this Agreement. RTC remains responsible for its sub-processors.

8. Location of processing

8.1 Customer personal data is hosted in the locations stated in Annex 3.

8.2 Where a location is outside the Philippines, RTC will ensure the recipient is bound by contractual protections comparable to the Privacy Laws. The parties acknowledge that the Customer remains accountable for the data under Section 21 of the Data Privacy Act.

9. Requests from data subjects

9.1 If a data subject contacts RTC about Customer personal data, RTC will refer the person to the Customer and tell the Customer within 5 business days. RTC will not respond on the merits unless the Customer instructs it to.

9.2 RTC will provide reasonable help, including through product functions, so that the Customer can answer requests for access, correction, erasure, blocking, objection and portability.

10. Personal data breach

10.1 RTC will notify the Customer without undue delay, and in any case within 24 hours, after RTC knows or reasonably believes that a personal data breach affecting Customer personal data has occurred.

10.2 The notice will go to the Customer's administrator and privacy contact. It will describe, as far as known, the nature of the breach, the data and people likely affected, the measures taken, and a contact at RTC. RTC will send updates as it learns more.

10.3 RTC will contain and investigate the breach, and will give the Customer the information it reasonably needs to notify the National Privacy Commission and affected data subjects within the legal period.

10.4 The Customer decides whether and how to notify regulators and data subjects. RTC will not make public statements naming the Customer without its consent, unless the law requires.

10.5 A notice under this clause is not an admission of fault.

11. Help with compliance

RTC will give reasonable help with the Customer's privacy impact assessments and with inquiries from the National Privacy Commission that concern the Service. Help beyond 8 hours in a year may be charged at RTC's standard rates, unless the need arises from RTC's breach.

12. Information and audit

12.1 On request, and no more than once a year, RTC will give the Customer a written summary of its security measures and any independent assessment reports it holds.

12.2 If that information is not enough to show compliance, or after a personal data breach, the Customer may audit RTC's relevant controls on 30 days' notice, during business hours, at its own cost, under confidentiality, and without access to other customers' data.

13. Return and deletion

13.1 When the Main Agreement ends, the Customer may export its personal data for 30 days.

13.2 RTC will then delete Customer personal data from active systems within 30 days and from backups within 90 days. RTC will confirm deletion in writing on request.

13.3 RTC may keep data that the law requires it to keep. It will keep that data confidential and will not process it for any other purpose.

14. Liability and term

14.1 Each party's liability under this Agreement is subject to the limits in the Main Agreement.

14.2 This Agreement lasts as long as RTC holds Customer personal data.

14.3 Philippine law governs this Agreement. Disputes follow the dispute clause of the Main Agreement.

15. Acceptance

The Customer accepts this Agreement electronically when it ticks the acceptance box at sign-up, or by signing an Order Form or Pilot Agreement that includes it. For acceptance at sign-up, RCONS records who accepted, when, and which version.

Annex 1: Details of processing

  • Item
    Subject matter
    Detail
    Construction project coordination and records
  • Item
    Duration
    Detail
    Term of the Main Agreement plus the deletion period
  • Item
    Nature and purpose
    Detail
    Hosting, storage, display to project users, reporting, support
  • Item
    Data subjects
    Detail
    Customer's staff, subcontractor and consultant personnel, other people named or shown in project records
  • Item
    Personal information
    Detail
    Name, role, company, contact details, task and log entries, comments and approvals, photos that show people, user log-in data
  • Item
    Sensitive personal information
    Detail
    None expected
  • Item
    Not in scope
    Detail
    Government ID numbers, health records, biometric data, payroll data

Annex 2: Security measures

This annex separates the measures in place today, checked on 21 November 2026, from those RTC is still putting in place.

  • Area
    Governance
    In place today
    A named Data Protection Officer (clause 5.3)
    Being put in place
    A privacy impact assessment for RCONS. A yearly policy review.
  • Area
    Access
    In place today
    A unique account for every user. Role-based access. Two-factor sign-in available to every user. The application reaches the database through its own login, limited to RCONS's data.
    Being put in place
    Two-factor sign-in on every RTC administrative account. Personal accounts in place of shared provider administrator log-ins. An access review every quarter, the first by 28 February 2027.
  • Area
    Encryption
    In place today
    Encryption in transit (TLS 1.2 or higher) between users and the application, and from the application to the database service. The database encrypted at rest by Supabase (AES-256). Uploaded files encrypted by RCONS (AES-256-GCM).
    Being put in place
    Encrypted backups, when backups start
  • Area
    Separation
    In place today
    Each customer's data kept apart by the application. Development and testing run apart from production, with no Customer personal data.
    Being put in place
    A written test of the separation between customers
  • Area
    Logging
    In place today
    An append-only audit log of sign-ins, failed sign-ins, role changes and administrative actions, kept with the customer's data
    Being put in place
    Alerts on unusual sign-in activity and on privilege changes
  • Area
    Resilience
    In place today
    None yet
    Being put in place
    Daily backups of the production database, a condition for opening customer accounts. A restore tested at least twice a year.
  • Area
    Development
    In place today
    Every change goes through a pull request before release
    Being put in place
    A second reviewer for every change. Dependency and vulnerability scanning. Fixes within set timelines.
  • Area
    Incidents
    In place today
    The 24-hour customer notice in clause 10
    Being put in place
    A written incident response procedure and a breach log
  • Area
    People
    In place today
    Access limited to personnel who need it (clause 5.1)
    Being put in place
    Written confidentiality undertakings. Training at onboarding and every year. Access removed on exit.
  • Area
    Vendors
    In place today
    Supabase and DigitalOcean assessed, and their data processing terms reviewed
    Being put in place
    Resend and Salesforce assessed. A record of the data processing terms accepted with each provider.
  • Area
    Physical
    In place today
    Data centres run by the providers. Supabase holds SOC 2 Type 2 and ISO 27001. DigitalOcean holds SOC 2 Type II, and its Singapore data centre lists ISO 27001. These are the providers' certifications, not RTC's.

Annex 3: Sub-processors and locations

  • Sub-processor
    Supabase Pte. Ltd., hosted on Amazon Web Services
    Service
    Database and sign-in. Storage of screenshots attached to support requests.
    Personal data
    All Customer personal data held in RCONS records, user accounts, support screenshots
    Location
    Singapore (AWS ap-southeast-1)
    Data processing terms
    Supabase's data processing addendum, part of its terms of service
  • Sub-processor
    DigitalOcean, LLC, with its listed sub-processors
    Service
    Application hosting. Storage of uploaded files and photos.
    Personal data
    Customer personal data passing through the application. Uploaded files and photos, stored encrypted on the application's server.
    Location
    Singapore (SGP1)
    Data processing terms
    DigitalOcean's data processing agreement, an addendum to its terms of service
  • Sub-processor
    Resend (Plus Five Five, Inc.)
    Service
    Sending emails from RCONS
    Personal data
    Names, email addresses, email content
    Location
    Tokyo, Japan (AWS ap-northeast-1)
    Data processing terms
    Resend's data processing addendum, part of its terms of service
  • Sub-processor
    Salesforce, Inc.
    Service
    Support cases from Contact Support
    Personal data
    Names, email addresses, company, the content of support requests
    Location
    To be confirmed. RTC will update this annex once it is.
    Data processing terms
    Salesforce's data processing addendum to its main services agreement