How DomestiCare handles personal, operational, and security data.

This Privacy Policy explains what information moves through DomestiCare, how it supports applicant workflows, why certain records are tightly controlled, and what handling expectations apply to personal and operational data.

Read the policy Sensitive record rules

Role-based access: Personal and operational data is exposed according to permissions, workflow assignments, and approved responsibilities.

Proportionate use: The system is meant to retrieve and process only the records needed for the current recruitment, support, or reporting task.

Secure report flow: Sensitive report and export actions may require password re-verification, audit logging, and controlled distribution practices.

Accountability: Security events, system logs, and review trails help investigate misuse, resolve incidents, and support compliance obligations.

Data stewardship

Privacy here means workflow discipline, not just hidden text.

DomestiCare moves information through recruitment, training, counseling, notifications, reports, and security review. The policy below is written around that lived system behavior.

The privacy scope includes account details, profile and document records, workflow status data, and communication history needed to deliver DomestiCare services.

Quick navigation

Need help?

April 7, 2026

Privacy and security concerns may be escalated through the DomestiCare administrator or the published contact channels below.

Long-form privacy notice

A data policy built around the actual DomestiCare workflow.

This is not limited to registration details. It covers workflow records, schedule data, counseling and training context, notifications, report configuration choices, and security logs that help keep the platform accountable.

1. Introduction

This Privacy Policy explains how DomestiCare collects, uses, stores, secures, and shares personal data across its applicant-facing mobile experience, Admin Portal, and related operational services.

It is written to reflect the actual system modules found in the project, including account management, job applications, documents, training, counseling, notifications, reports, archives, and security logs. DomestiCare aims to process data consistently with legitimate operational needs and the data-protection framework that applies in the Philippines.

Applies to applicant, staff, partner, support, and administrative interactions with the platform.
Covers both directly submitted records and platform-generated operational logs.

2. Information We Collect

Depending on your role and how you use the platform, DomestiCare may process account identifiers, contact details, profile information, education and skills data, work history, job applications, uploaded documents, training activity, counseling-related records, schedule details, notifications, and report configuration choices.

The system may also process technical and security-oriented information such as timestamps, IP addresses, device or browser details, login activity, verification outcomes, and audit logs needed to protect the platform and investigate misuse.

Account and identity data such as name, email address, role, and credentials-related metadata.
Applicant and workflow data such as applications, stage status, documents, training, counseling, and deployment context.
Technical and audit data needed for reliability, fraud prevention, and security monitoring.

3. How Data Reaches DomestiCare

Data may come directly from applicants, administrators, recruiters, coordinators, counselors, company partners, or technical users who enter, upload, review, or update records inside the platform.

Additional data may be generated by the system itself through scheduling actions, notifications, recommendation workflows, chatbot interactions, report requests, and routine platform security logging.

Direct submissions from forms, registrations, uploads, and workflow actions.
Operational updates entered by staff and approved partner users.
Automated records created by the system for notifications, recommendations, reports, and security events.

4. How We Use Personal Data

DomestiCare uses personal and operational data to create accounts, authenticate access, support recruitment and application workflows, coordinate documents and stage reviews, manage training and counseling operations, send notifications, generate analytics, and maintain service continuity.

Data may also be used to improve platform quality, support recommendation and chatbot features, detect misuse, troubleshoot incidents, enforce permissions, and document legitimate compliance or audit activity.

Account provisioning, authentication, and session security.
Application processing, stage management, document review, and deployment-related coordination.
Training, counseling, scheduling, notifications, and analytics.
Recommendation support, chatbot assistance, abuse prevention, and incident handling.

6. Sensitive Records, Reports, and Internal Access

Some DomestiCare records are more sensitive than others, especially when they involve medical status, visa processing, deployment readiness, counseling notes, internal analytics, or consolidated report outputs. Access to these records is restricted by role, workflow scope, and additional security controls.

When a user requests a sensitive report or export, the platform may require password re-verification, policy acknowledgment, and security logging so that aggregated personal and operational data is not disclosed casually or outside approved channels.

High-sensitivity records are protected by least-privilege access and workflow-specific visibility.
Reports and exports may include multiple data categories in one output, so retrieval is governed more strictly than routine on-screen viewing.
Approved users should retrieve only the sections, date range, and format necessary for the current task.

Controlled visibility

Medical, visa, deployment, counseling, and analytics records can expose multiple sensitive categories at once.

Verification before export

When a user requests a report, DomestiCare may process identity, role, report type, selected sections, filters, export format, timestamps, IP address, and device or browser details to confirm authorization, secure data retrieval, investigate incidents, and maintain audit trails under applicable data-protection obligations.

Secure handling

Downloaded files and exports should stay inside approved devices, storage, and reporting channels.

7. Retention and Disposal

DomestiCare keeps personal and operational records only for as long as they are needed for legitimate service delivery, workflow continuity, security review, compliance needs, lawful record-keeping, or approved organizational retention practices.

When records are no longer needed, they should be archived, restricted, deleted, or otherwise handled according to the applicable retention schedule, workflow rules, and secure disposal practices.

Retention periods may vary depending on the record type and operational purpose.
Temporary files, exports, and downloaded copies should not be retained longer than necessary.

8. Security Measures and Incident Response

DomestiCare uses role-based permissions, authentication controls, verification steps, secure session handling, audit-oriented logs, and administrative review processes to reduce unauthorized access and support accountability.

No digital system is completely risk-free. Users are expected to protect their devices, avoid sharing credentials, use approved channels for sensitive files, and report suspicious activity, accidental disclosure, or system misuse immediately.

Authentication and re-verification for high-risk actions.
Logging and audit trails for report access, system events, and security review.
Shared responsibility between the platform team and every authorized user.

9. Rights, Questions, and User Requests

Individuals may have rights under applicable data-protection law, including rights related to access, correction, and fair or lawful processing of their personal information. DomestiCare expects concerns about privacy, accuracy, or access scope to be raised through approved support or administrative channels.

Requests may require identity confirmation and may be reviewed in light of platform security, workflow dependencies, legal obligations, and the rights of other data subjects or authorized users.

Ask for clarification when you are unsure why a record is being processed.
Request correction when personal data appears inaccurate or outdated.
Escalate privacy concerns through approved support, administrative, or designated contact channels.

10. Policy Updates and Contact

DomestiCare may revise this Privacy Policy as the platform grows, workflows change, or legal and security obligations evolve. The latest published version should be treated as the controlling reference for current platform practice.

For privacy-related questions, policy concerns, or security escalation, contact the DomestiCare administrator or mesacharlesluigi@gmail.com.

Check the latest published version for the current policy date and wording.
Escalate urgent incidents quickly when they involve unauthorized access, disclosure, or device compromise.

Privacy rights and expectations

Access and correction

Users may request review or correction of inaccurate personal information through approved support or administrative channels.

Security concerns

Lost devices, suspicious activity, and accidental disclosure should be reported immediately so the platform team can respond.

Processing questions

Questions about why a record is collected or how it is used should be escalated to the designated administrator or privacy contact.

Policy updates

Legal and operational notices may change as the platform evolves, and published policy updates become the governing reference.

Questions about platform rules, user responsibilities, or service boundaries should also be reviewed together with the Terms and Conditions so the legal and operational expectations stay aligned.

Open Terms and Conditions