Data Processing Agreement
Outsourcing agreement under Rule X of the Implementing Rules of the Data Privacy Act of 2012
Robles Technologies Corp. | RTC Payroll
Version 2026-11-21. Effective 21 November 2026.
Every customer and every pilot user accepts this Agreement before real personal data enters the product, by clicking to accept it at sign-up or by signing it with an Order Form.
Between the business that accepts this Agreement at sign-up or signs it below ("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 RTC Payroll ("Services") under the Terms of Service or a 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 Services 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 Services, 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 for its own registration and compliance with the National Privacy Commission.
4.3 The Customer will not put into the Services categories of personal data that Annex 1 does not cover without telling RTC first.
4.4 Clock-in photos are optional and off by default. The Customer decides whether to turn them on for each pay group. Before doing so, the Customer will confirm that they are necessary and proportionate, complete its own privacy impact assessment, inform the affected workers, and provide another way to record time for a worker who cannot reasonably use them. When an employee clocks in from the employee portal, the portal asks the employee's phone for its location at that moment only, and the employee can refuse and still clock in. The Customer will tell its workers about this. The Services do not capture biometric data.
5. People who handle the data
5.1 RTC will limit access to Customer personal data to personnel who need it to provide the Services.
5.2 RTC will bind those personnel by written confidentiality obligations that continue after their engagement ends, and give them privacy and security training. As of the version date above, the written undertakings and the first training are still being put in place (Annex 2).
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.
6.3 RTC will not use photo or location data for any purpose other than the Customer's timekeeping. RTC does not offer biometric capture, and will not add it without first updating this Agreement.
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 affected 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 Services. 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.
Annex 1: Details of processing
| Item | Detail |
|---|---|
| Subject matter | Payroll, timekeeping, leave and related HR administration |
| Duration | Term of the Main Agreement plus the deletion period |
| Nature and purpose | Hosting, storage, calculation, report and payslip generation, support |
| Data subjects | Customer's employees and workers, and Customer's HR and payroll users |
| Personal information | Name, contact details, position, deployment, schedules, time records, leave, loans and cash advances, user log-in data, photos of paper attendance logbooks where the Customer uploads them |
| Sensitive personal information | TIN, SSS, PhilHealth and Pag-IBIG numbers, pay and tax data, date of birth, civil status where entered, bank or e-wallet account details |
| Captured at clock-in | Photo at clock-in, only where the Customer turns it on for a pay group. Location at clock-in from the employee portal, where the employee's phone allows it. |
| Not in scope | Health records. Biometric data. Location at any time other than clock-in. |
Annex 2: Security measures
RTC maintains the measures described in its Information Security Policy. The first table lists the measures in place on the version date. The second lists measures that are planned and not yet in place. RTC will update this annex as each one is put in place.
In place
| Area | Measure |
|---|---|
| Governance | A named Data Protection Officer. A written Information Security Policy. |
| Access | Unique accounts and role-based access in the product. Office roles and managers must use two-factor sign-in by default. RTC's support console needs a time-limited, logged access grant before RTC staff can see a customer's unmasked data. |
| Encryption | Encryption in transit (TLS 1.2 or higher) on connections to the application and to the database service. Encryption at rest for databases and backups, provided by the hosting provider. Government identifiers and bank and e-wallet account numbers are also encrypted in the database, with the key held in Supabase Vault, and shown masked by role. |
| Separation | Each customer's data is separated in the database by row-level security. Development runs on separate local environments with demo data, not on production. |
| Logging | An append-only audit log of changes, including changes to pay data, kept in the database for the life of the account. Sign-in logs kept by the sign-in provider for its standard log period. |
| Resilience | Daily backups of the database, each kept for 7 days. Stored files, such as photos and documents, are not in these backups. |
| Development | Changes go through pull requests and automated tests before release. |
| Incidents | A written breach response procedure in the Information Security Policy, with customer notice within 24 hours (clause 10). |
| Vendors | Supabase and DigitalOcean were reviewed before use. Their data processing terms are part of the terms RTC accepted. |
Planned, not yet in place
| Area | Measure |
|---|---|
| Governance | A privacy impact assessment for the product. A yearly policy review. |
| Access | Two-factor sign-in confirmed on every RTC staff account for hosting, source control and email. Every staff access to customer data tied to a support ticket. A quarterly review of privileged access. |
| Logging and monitoring | Sign-in and audit logs kept for 12 months. Alerts for unusual sign-in activity and privilege changes. |
| Resilience | A restore from backup tested twice a year. |
| Development | A second reviewer on every change. Dependency scanning on every build, and patches within set timelines. A yearly independent penetration test. |
| Incidents | A breach runbook and a breach log. |
| People | Written confidentiality undertakings, onboarding and yearly training, and access removed when someone leaves. |
| Vendors | Review of the data processing terms of Resend, Salesforce and Microsoft. |
Annex 3: Sub-processors and locations
| Sub-processor | Service | Personal data | Location | Data processing terms |
|---|---|---|---|---|
| Supabase Pte. Ltd., hosted on Amazon Web Services | Database, sign-in and file storage | All Customer personal data | Singapore (AWS ap-southeast-1) | Part of Supabase's terms of service |
| DigitalOcean, LLC, with its listed sub-processors | Application hosting | Customer personal data passing through the application. None stored at rest. | Singapore (SGP1) | Part of DigitalOcean's terms of service |
| Resend, Inc. | Sending the application's emails from payroll.roblestech.net | Names, email addresses and email content | Tokyo, Japan (AWS ap-northeast-1) | Being reviewed |
| Salesforce, Inc. | RTC's support case records | What the Customer's users write in Contact Support requests, with their name, email and company, and a link to any screenshot that stops working after 30 days | Not yet confirmed | Being reviewed |
| Microsoft Corporation (Microsoft 365) | RTC's own mailbox for support@, signups@ and [email protected] | What the Customer's users include in emails to those addresses, and copies of their Contact Support requests | Not yet confirmed | Being reviewed |
Not in use. Reading photographed paper logbooks with an AI service is switched off. Before switching it on, RTC will add the provider (Anthropic, PBC) to this annex and give the notice in clause 7.2.
Signatures
For a Customer that signs this Agreement instead of accepting it at sign-up.
| Customer | Robles Technologies Corp. | |
|---|---|---|
| Signature | ||
| Name | Kenneth Robles | |
| Title | Chief Executive Officer | |
| Date |
© 2026 Robles Technologies Corp. All rights reserved.
RTC Payroll™ is a trademark of Robles Technologies Corp.