Privacy policy
What the public website processes, where data goes, and the choices you have.
1. Who operates this edition
Carefolio (家安簿) is the product available at mykinrecord.com. The legal operator and business contact details are listed below.
Product brand: Carefolio (MyKinRecord / 家安簿)
Legal operator: 马勇
Operating country or region: China
Support and privacy contact: support@mykinrecord.com
The public website runs on Alibaba Cloud in Hong Kong. The application server processes uploaded documents and stores account data there. Access from another country can involve cross-border transfers. Upload only records you are authorized to manage. External AI processing, when configured, requires separate consent as described below.
2. Information you choose to provide
We process your account name, email address, protected password credentials, session information, and the health-profile information you enter. Health data may include records, uploaded documents and images, extracted text, your corrections, medication schedules, appointment details, personal notes, and action history.
Family access also uses invited email addresses, roles, invitation tokens, and acceptance status. Provide another person’s information only when you have their permission or another valid authority to manage it.
3. How the information is used
Information is used to authenticate your account, organize records, extract text, show sources for review, save your corrections, maintain plans and appointment briefs, and enforce the sharing permissions you choose. It is also used to provide account export and deletion.
This edition has no advertising, session replay or cross-site behavioral analytics. When public traffic counting is enabled, only daily request totals for selected public marketing pages and the fictional demo, interface language and a fixed source category are stored on our server for up to 90 days. We do not store visitor IDs, IP addresses, complete referrer URLs, arbitrary query values, account activity or health records in these counts. Known bots and requests carrying Do Not Track or Global Privacy Control are excluded. Demo requests do not indicate task completion. Counts represent page requests, not unique people; unattributed visits may include AI referrals. It does not include a model-training pipeline, data-sale integration, or external AI service in its default record-processing flow.
4. Document recognition and optional AI
PDFs, images, text and supported DOCX documents first use extraction or OCR on this server. Local extraction is the default. If an OpenAI-compatible model is configured, each upload may separately opt in to AI structuring. The consent screen names the provider and model. Only extracted text and its page numbers are sent, not the original file. That text can contain names, dates of birth and health information. The provider processes the text under its own terms and retention practices; this application does not promise that providers retain nothing or never train on data.
Extracted information can be incomplete or wrong. Review dates, names, results, medication details, and schedules against the original. A language switch changes interface text and does not automatically translate clinical documents.
5. Storage and protection
Records and original files are stored on the server used to run this edition. Health-state records and uploaded files use AES-256-GCM encryption with a server-side key. Account names, emails, and access metadata are stored in the server database without that health-data encryption. Passwords are hashed with scrypt. Server-side access checks restrict profiles to authorized accounts.
Encryption at rest is not end-to-end encryption: the running server can decrypt data to provide the service, and the local key is kept in the private server data directory. Protect the server and key; a compromised host can expose data. Temporary plaintext files used for OCR are removed after the job. The public mykinrecord.com website uses HTTPS for transport protection. No system can guarantee absolute security.
6. Sharing with family
Profile administrators can grant viewers or collaborators access to a selected health profile. Invitation links are shared by you; this edition does not send invitation emails. An invitation is not access until the intended account accepts it. You can review or revoke access in the application.
Production requires email ownership verification. Preview verification is optional and its enabled state is shown by the application. Verification and password recovery messages are sent through the configured SMTP provider; these emails contain no health records. Share the secret, single-use invitation link through a trusted channel and check the recipient. An account must match the invited email to accept. People with access may read or download permitted information; exported files and printed briefs are outside the application’s access controls.
7. Retention, export, and deletion
Account data is retained while your account exists, unless you delete a file, record, or profile earlier. You can export your owned data, delete individual source files, and delete your account in Settings. Removing a source file removes the stored original; a retained record or text must be deleted separately if you also want that content removed.
Account deletion revokes your sessions and removes your account and owned profiles with their records and source files. It removes your access to profiles owned by others without deleting their information. Encrypted database, source-file and key backups are taken daily on the same host; the latest seven automatic snapshots are kept. Deleted data may remain in those snapshots until rotation. Older manual and release backups have no fixed deletion schedule yet. Automatic off-host backups are not configured. Account deletion does not instantly erase every backup copy. Monthly AI metering stores credits, token counts, time and billing status without source text; account deletion removes the user link while anonymous budget totals remain.
8. Payment and account email providers
Paid checkout, when opened, is handled by Waffo Pancake as merchant of record. Checkout sends your account email, selected product and an opaque account reference. We retain order and subscription identifiers, status, billing periods and event history to grant access and prevent duplicate processing. Health documents, profile contents and passwords are excluded from checkout. Waffo processes payment, transaction and legally required records under its own privacy policy; payment-record retention is separate from health-record deletion.
The support email uses Tencent business-mail routing. Account verification and password recovery messages use the configured transactional email provider over a secure SMTP connection. The provider processes the recipient email address and account verification or recovery link to deliver these messages. These messages contain no health documents.
Resend is the configured sender for account verification and password recovery. When enabled, messages are submitted using the Tokyo sending region (ap-northeast-1). They contain the recipient email address, account verification or password-reset link, and the message text needed for that account action, without health records. A sending region does not mean that all provider logs or account metadata stay only in Japan. Email delivery remains subject to provider processing and recipient mail systems.
9. Cookies and browser storage
An essential session cookie keeps you signed in. The browser also stores interface preferences such as language. Installing the PWA caches public install assets and an offline notice; account pages, health records and authenticated API responses are not cached by the service worker. Account-specific preferences must not be used as a substitute for server authentication. We do not set advertising or cross-site tracking cookies in this edition.
If you allow browser notifications, your device stores that permission. You can revoke it in your browser settings. Alerts require the site to remain open and are not guaranteed while offline or in the background.
10. Your choices and requests
You can correct records, control family access, export data, and delete your account. Depending on your location, applicable law may provide additional access, correction, deletion, portability, restriction, or complaint rights. Send privacy or account requests to the support email shown on the contact page. Do not send health documents or passwords by email; identify your account and the request instead.
11. Adults and dependent profiles
Account holders must be adults. A dependent’s profile may be added only by a person with valid authority and permission to handle the information. This edition is not designed for children to register their own accounts.
12. Changes to this policy
Material changes to data use, processing locations, or external providers require an updated policy and an appropriate notice before taking effect. The retention section describes the current backup limits, including the unresolved deletion schedule for older manual and release backups.