DCarePro Privacy Policy
Last updated: November 16, 2026
- We only keep the data each daycare enters to run its business, and the data families enter in the parents' portal.
- We don't sell data, use it for advertising or share it with other daycares.
- DCarePro doesn't process payments or store card or bank account numbers.
- Children's data belongs to each daycare and is never used to train AI models.
1. Who we are
DCarePro is a management system for home daycares, operated by DTV Services (Dickson Terrero).
- Website: https://dcarepro.com/ (each daycare's account runs at
dcare.dtv-services.com/<daycare>) - Contact and support: support@dcarepro.com
- Support inside the system: Settings → DCarePro → Support
Each daycare that uses DCarePro decides what data it enters and what it uses it for. For the information about children and families, the daycare is responsible for that data and DCarePro processes it on the daycare's behalf.
2. What data we collect
| Type | What it includes |
|---|---|
| Accounts | Name, e-mail or mobile number, and role of the owner, staff and parents who have access. Passwords are handled by our sign-in provider (Google Firebase); DCarePro never sees or stores them. |
| Children and families | What the daycare enters: children's names, date of birth, schedule and rates; parents' and guardians' contact details; and, if the daycare records them, allergies, pediatrician, authorized pick-up people, photos and documents. |
| Attendance | Arrival and departure times, who marked them and how (staff, QR or parent's phone), absences and their reason. |
| Billing and payments | Invoices by family, recorded payments and balances. Families pay by Zelle, cash, check or other means outside the system. |
| Staff | Employee details the daycare enters: certifications, time clock, payroll and loans. |
| Expenses and accounting | Date, vendor, total and photo of receipts; books and bank reconciliations. |
| Menus and meals | CACFP menus and what each child ate. |
| Demo requests | Name, e-mail, phone and daycare name of whoever fills out the "Request a demo" form. |
| Technical data | An activity log (who did what and when), the date of last access, and, if a person turns on notifications, the address their browser gives us to send them. |
We don't collect card numbers, bank accounts or family location history.
3. Parents' portal
Families invited by their daycare can use the portal at dcare.dtv-services.com/<daycare>/portal. There they can:
- Mark arrival and departure by scanning the daycare's QR code. To confirm they are at the daycare, the phone shares its location only at that moment and only if the parent allows it. We compare it with the daycare's address and keep the distance in meters, not the coordinates.
- Review and update their children's information; the daycare reviews each change.
- Report that a child won't come, with a reason and an optional document (for example, a medical note) that is saved in the child's file.
- Exchange messages with the daycare's owners and office.
- See the menu and what their own children ate. Parents never see other children's names.
- Receive notifications on their phone, only if they turn them on. They can turn them off at any time.
Parents without e-mail sign in with their mobile number: Google Firebase sends them a one-time code by SMS.
4. AI assistant (Muse) and receipt reading
Muse
The owner can connect DCarePro with Muse, Meta's personal assistant, to keep her books by chatting in Spanish.
- Each daycare has its own endpoint and its own OAuth connection (
https://dcare.dtv-services.com/<slug>/mcp). The credentials are kept in that daycare's space and don't work for any other daycare. - The owner decides what the assistant can see and do in Settings → AI assistant. Without that permission it can't write anything.
- The assistant does not receive medical notes, custody restrictions, photos, documents, phone numbers or addresses.
- Nothing is recorded without confirmation: before saving an expense, a payment, a void or a new category, the assistant shows the exact summary and only records it when the owner confirms. Sensitive operations use a one-time code that expires in 30 minutes.
- What the owner writes or sends to the assistant (for example, a receipt photo) is used only to do what she asked. What she says in Muse is also governed by Meta's privacy policy.
Receipt reading
When the owner uploads a receipt photo, DCarePro sends it to OpenAI to read the date, vendor and total. OpenAI processes it through its API and, under its API terms, does not use it to train models.
5. How we use data
- To run the daycare: attendance, billing, payments, staff, expenses and menus.
- To send what the daycare or family asks for: invitations, invoices, receipts, reminders and notifications.
- To answer the support tickets the owner opens.
- To keep the system secure and backed up.
We don't sell personal data. We don't use it for advertising. We don't share it with other daycares.
6. Children's data
The system keeps data about minors because the daycare needs it to care for them. This data:
- Belongs to each daycare and never leaves its own space (a separate schema per daycare in the database).
- Is entered by the daycare or by the child's parents, never by the children.
- Is never used for advertising or to train AI models.
- The daycare owner is responsible for having the families' permission to record their children's data.
- Demo or review accounts (for example, for Meta) use only fictional data, never real names of children or families.
7. Who we share data with
We don't share personal data with third parties for commercial purposes. Only these providers take part, and only to provide the service:
| Provider | What for |
|---|---|
| Google (Firebase and Cloud Storage) | Sign-in, SMS codes for parents, and storage of photos and documents. |
| Resend | Sending e-mails (invitations, invoices, receipts, reminders). |
| OpenAI | Reading the receipts the owner uploads. |
| Phone push services (Apple, Google, Microsoft, Mozilla) | Delivering notifications to people who turned them on. They receive the title and a short text of the notice. |
| Meta (Muse) | Only if the owner connects it, and only what she allows. |
| Liquid Web (United States) | The server where the system and its database run. |
We also share data with authorities only when a law requires it.
8. Security and backups
- Each daycare's data is isolated in its own database schema (multi-tenant PostgreSQL).
- The connection is encrypted (HTTPS).
- Each person sees only the sections of their role; parents see only their own family.
- An activity log records who changed what and when.
- A full backup every night, encrypted before it leaves the server and kept off it. The key that opens it is kept off the servers and is only used to restore; per-daycare restore has been tested in practice.
- Operator access: DTV Services has no user account in any daycare and never knows its users' passwords (the owner creates hers from a link only she receives). As server administrator it can technically reach the database, and it commits to not looking at a daycare's data unless the daycare asks or authorizes it, it is needed to restore the service or handle a security problem, or a court order or law requires it; in the last two cases it tells the daycare what was done and why.
- If someone accesses a daycare's data without authorization, we notify the daycare within 72 hours of confirming it.
9. How long we keep data
We keep the data while the daycare's account is active and up to 12 months after it is closed, so the daycare can recover or export it. After that we delete it, unless a law requires keeping accounting or tax records longer. Copies in backups are erased as those backups rotate out.
Demo requests that never become a daycare are deleted within 12 months.
10. Your rights
The daycare owner can ask at any time to see, correct, export or delete her account and her daycare's data. Parents can see and correct their children's information from the portal; for anything else, they should contact their daycare, which decides on that data, or write to us.
Write to support@dcarepro.com. We will answer within 30 days.
11. Changes to this policy
If we change this policy, we will publish the new version on this same page with its update date. We will announce important changes inside the system.
12. Contact
For any question about this policy or your data, write to support@dcarepro.com.