Privacy Policy

About Pet E-Dex

Pet E-Dex helps households and caregivers organize animal information, care directions and reported care. This notice explains information used for those services. The operator is Corie Jean Allen, an Illinois sole proprietor operating under the name Pet E-Dex. The public business mailing address is 2565 Bluff Drive, Kankakee, IL 60901, United States. The website is petedex.com. Send privacy questions to info@petedex.com or the mailing address above. Never send passwords, sign-in tokens or invitation secrets. Share private files only if a verified support process arranges an appropriate secure transfer.

Pet E-Dex is in prelaunch preparation. New beta enrollment remains closed. Publishing these policies does not open registration or activate in-app support. Support access, account-deletion operations and coordinated backup recovery are still being completed and verified; this notice does not represent those operations as fully ready. These limits do not postpone applicable privacy or incident duties.

Information Collected

Accounts and authentication. Google Firebase Authentication handles email/password registration, verification, sign-in and password reset. Firebase processes the credentials, provider identifiers and authentication-related technical information. Application records include internal account ID, provider identity mapping, email, available display name, creation time, household membership and access status. Passwords are not stored in the application's record tables. Provider account creation and permission to use saved app records are separate steps; saved-record access requires a verified email and authorized application access.

Closed-beta admission. New application enrollment is closed during prelaunch. When enrollment opens, admission will use a private list of approved, verified email identities and require the Terms, Privacy acknowledgment and age/eligibility confirmations. Admission does not grant access to another household. Existing accounts retain their original sign-in identity association and remain subject to account status and household permissions. A caregiver invitation is separate from new-account admission. A Firebase sign-in identity can exist without application enrollment; rejected enrollment does not automatically delete that identity. Contact the privacy contact if you need help with a sign-in identity that has no application account.

Animal and care information. Users choose which animal profiles and identifying details; veterinary records, appointments and test results, including user-entered appointment costs, deposits and payment notes; food, medication, treatment and care directions; allergies and restrictions; tasks, assignments and outcomes; contacts and caregiver information; notes, photographs and documents to provide. Files may contain information about people, including information about children entered by an authorized adult. Provide only information you are authorized to use and share; avoid unrelated sensitive personal information. Appointment payment notes are records users enter, not a Pet E-Dex payment-processing service. Do not enter payment-card credentials in free-text notes.

Sharing and history. Caregiver invitations store invited email, selected animals, access dates/time zone, status, creating/accepting accounts and times. The server stores an invitation-token hash. Tasks/corrections retain authenticated attribution, server recording times and original instruction snapshots. General record edits have change history, but not every older change log identifies an authenticated actor. Meaningful account activity for retention, export/deletion requests, approved-policy acceptance receipts and operational case evidence are distinct records.

Support. Email includes the sender’s address and chosen message. The in-app feedback form is not yet accepting reports. When enabled, it collects a report type, description, optional user-selected area and manually entered error reference, along with the signed-in account’s ID and reply email, application version and recording time. It does not automatically attach animal names, records, files, page URLs, passwords or tokens. Saved reports go to a restricted application inbox; submission does not itself send an email or emergency alert. A user’s stored reports are included in their account export and removed during completed account deletion.

Technical information. The app’s own failure reports use an opaque reference, a fixed operation label and a broad category rather than raw errors, request contents, identities or care details. Authentication and hosting providers separately process technical information, which can include IP addresses, browser/device information and request details such as method and URL. Their processing and retention are not controlled solely by the app’s failure-report format. Browser sign-in storage, display preferences and limited drafts/retry references are described below.

Purposes and Sharing

Information supports accounts, security, authorized records, schedules/directions, reported care, exports, sharing, support, privacy requests, troubleshooting and retention. A saved contact does not create an account or permission. Viewing a task, elapsed time or acknowledging an alert is not proof of completed care.

Authorized household users can see information allowed by their roles. Temporary caregivers receive permitted work for selected animals during the approved period, including needed directions, restrictions and supported care context. They do not receive general household-file access merely by accepting an invitation. Ending access does not recall information already seen/copied or erase legitimate care history belonging to another household.

Owners may also share a separately selected care-summary snapshot with a verified recipient for an expiring period. The stored snapshot, recipient email, accepted account, creation/expiry and revocation details support that sharing. A summary is a copy of the selected information at creation, not an automatically updated care plan or a household membership. Its recipient does not gain general file access.

External links you choose. Choosing Directions on a veterinarian profile opens Google Maps with the selected veterinarian address. Choosing Schedule opens that veterinarian's saved external booking website. Those services handle the visit under their own terms and privacy notices. These links do not automatically send the full animal or household record.

We may disclose only information reasonably necessary to meet a legal obligation or valid legal request, investigate abuse or protect service security, or address a serious safety concern when disclosure is permitted by law. We assess the request and limit the information and recipients to its legitimate purpose. If ownership of the service changes, any transfer of personal information must remain subject to applicable law and the privacy commitments in effect; a business transfer does not by itself authorize unrelated new uses. We will provide any notice or obtain any consent that the law requires.

Our privacy commitments. Pet E-Dex will not sell customers' personal information or share it for cross-context behavioral or targeted advertising. Pet E-Dex will not use customer records, animal medical information, photographs, uploaded documents or other customer-submitted content to train AI models. Necessary processing by authorized hosting, authentication, email and other service providers may continue for legitimate application operations, subject to applicable agreements and this policy. Authorized sharing among animal owners, households and caregivers remains available within their permissions. These service functions and user-directed sharing do not authorize advertising or customer-content training uses.

Service Providers and Locations

The public site at petedex.com continues to use OpenAI’s Sites hosting service, with Cloudflare Workers for hosting, D1 for application records and R2 for stored files. A separate prelaunch deployment also exists in the operator’s own Cloudflare account. The public domain has not yet moved to that separate deployment, and the existing Sites resources remain in use. Google Firebase Authentication handles sign-in, verification and password reset. Support email uses Microsoft 365 through GoDaddy; GoDaddy also provides domain registration.

Authorized service providers process information needed for those functions under the applicable service arrangements. Processing may occur in the United States and other locations where the providers operate. Firebase documents United States processing for its Authentication service, but this is not a promise that every category of information handled by Pet E-Dex or its other providers stays in the United States. We make no whole-service US-only storage or processing claim.

Provider-held technical records, backups and mailbox copies have separate lifecycles. Their settings and actual removal are still being verified during prelaunch. Operator-controlled backups and downloaded copies are also subject to the retention and access commitments below; publishing this notice does not establish that a complete backup or tested restoration service is already in place.

Stripe is selected for possible future billing, but no payment collection is active during the free beta. We will update this notice before enabling payment processing.

Cookies and Browser Storage

The app uses an HttpOnly session cookie, a selected-household cookie and a sign-out security cookie. HTTPS cookies use Secure/SameSite protections. Firebase manages credential persistence: Keep me signed in requests persistence across visits; the session choice limits provider storage to the current session/tab. App authorization remains bounded by verified token validity.

Browser storage coordinates sign-in between tabs, remembers requested Home preferences, preserves limited save/deletion retry references, and can hold a temporary caregiver draft/token. Some temporary items include an invited email, animal IDs or invitation secret; they are not analytics. Protect shared devices. Signing out does not promise to clear every draft/preference. Clearing site storage may remove these items and require sign-in, but does not delete saved server records. Downloaded exports remain under the recipient's control.

The application does not currently change its processing in response to a browser's Do Not Track setting. Necessary sign-in and security functions continue when that setting is enabled. Terms acceptance and Privacy acknowledgment do not supply marketing or tracking consent.

Security

We use reasonable administrative and technical safeguards appropriate to the personal information we handle and will notify affected people when applicable law requires. The app uses verified sign-in, household and action permissions, dated animal-scoped caregiver access, private file and export routes, bounded uploads and limited error responses. The public site uses HTTPS.

No service can guarantee prevention of every loss or unauthorized access. Local checks do not establish an independent penetration test, security certification, end-to-end encryption or a completed provider recovery drill. Provider access, operational support and backup recovery verification are still being completed during prelaunch.

Retention, Exports and Deletion

We keep active account records while in use, including archived or deceased animals and original care history. Accounts and records enrolled in the approved beta carry into launch without a reset. Our Data Retention policy provides 12 calendar months of view/download access after future paid access ends and review after 24 calendar months without meaningful use for free accounts. Removal for either reason requires a first notice at least 60 days beforehand and a separate final notice at least 7 days beforehand. Meaningful use or Keep my account stops inactivity deletion before processing begins. No paid subscription or unattended purge service is active.

For eligible signed-in accounts, My Account → Your data provides an own-household records/files export, Keep my account and a deletion-request route requiring recent password reauthentication. Exports stream to the requester; the app does not retain generated ZIP archives. Incomplete file reads prevent an apparently complete export. The account export is a portable copy, not a complete service backup. If a self-service route is unavailable or an export cannot finish, contact us for an appropriate assisted route after verification; do not delete records first merely to obtain a copy.

Deletion requests require identity and ownership review and may be canceled until processing starts. We target completing reviewed removal of live application records and files, and initiating deletion of the associated Firebase sign-in identity, within 30 days from original receipt, subject to applicable deadlines and explained exceptions. The 60-day and 7-day inactivity/ended-paid-access notices do not delay a requested deletion or restart its deadline. Deletion is not immediate or automatic, and this target does not certify removal of every provider-retained copy. Legitimate care history belonging to another household is reviewed separately rather than erased merely because its contributor leaves.

Policy-acceptance receipts record the authenticated application account, exact document versions and content, and the server acceptance time. Accepting a later version preserves earlier receipts while the account exists. Completed account deletion removes that account’s policy receipts and support reports. We retain restricted deletion-case and identity-suppression evidence needed for safe recovery; policy acceptance does not create indefinite retention of every receipt or case detail.

Completing live application deletion and removing retained copies are separate steps. We target removal of backup copies under our control within 90 days after live application deletion. Firebase’s published lifecycle allows up to 180 days after we initiate deletion of the sign-in identity for associated authentication information to be removed from its live and backup systems. These periods have different scopes and starting dates. A successful live deletion or elapsed time alone does not prove removal from every retained copy.

We restrict access to retained copies and keep only necessary deletion and access-restriction evidence while older copies could restore deleted information or access. We review retained deletion-case evidence at least every three months and remove unnecessary details while preserving the minimum records needed for safe recovery. Restored information must be reconciled with those records before access resumes. Necessary legal or security exceptions must have a documented purpose, restricted access and a reviewed end condition.

Our maximum retention targets are 30 days for routine technical logs, 90 days for security logs and 12 calendar months after resolution for support conversations, with narrowly documented incident or legal exceptions. Care history is not a technical log. Provider logs, mailbox copies and operator archives must be addressed separately; their actual retention and removal are not yet fully verified. These targets do not mean all providers have already been configured to erase their copies on those dates.

For in-app reports, an authorized operator’s explicit resolution starts the 12-calendar-month support period. Unresolved reports do not expire merely because time has passed since submission. Reopening stops the active expiry period; a later resolution starts it again. Expired reports can remain stored until manual removal and remain in the submitting account’s export while stored. We do not promise unattended erasure or a complete support correspondence history.

Account-deletion operations, provider/archive removal and coordinated recovery are still being completed and verified during prelaunch. We will not describe a particular deletion or backup removal as complete without supporting evidence. No particular restoration time or recoverable history window is promised.

Choices, Eligibility and Applicable Rights

You can edit supported records, end caregiver access, download your own household data and request deletion. For help, a copy or correction request, or a concern about personal information recorded by another household, contact info@petedex.com. Historical care facts may need a reviewed correction rather than silent replacement.

We will ask only for information reasonably needed to verify identity and authority. Never send passwords or sign-in tokens. Provide identity documents only if an appropriate verified process arranges a secure transfer. We may request evidence that an authorized representative can act for you. We do not reveal another household's private records when handling a request. If we decline all or part of a request, we will explain the reason unless prohibited by law and explain any applicable appeal route. You can ask us to reconsider by replying or emailing “Privacy request review” to the same address. We will meet the applicable response deadlines and explain any lawful extension. We will not penalize you for exercising privacy rights protected by law.

Rights depend on applicable law and can include access, correction, deletion, portability, limits on certain uses, appeal or complaint to a regulator. The app's 30-day requested-deletion target does not replace a shorter legal deadline or create one universal deadline for every type of request.

Accounts are for invited US adults 18 or older. Adult users may enter necessary, authorized information about other people, including children, in contacts or files. Do not give a child an account or collect unrelated sensitive information. Contact us if you believe a child is using the service or their information has been included improperly; we will investigate and take appropriate action consistent with applicable law.

Policy Changes and Contact

New versions will show their effective date, and prior published text will remain available. We will explain material changes before they take effect through an in-app notice and, when required or appropriate, the account’s contact channel. Changes needed urgently for security or legal compliance may require earlier action with notice as soon as reasonably possible. We will obtain separate consent when the law requires it; acknowledging this notice is not blanket consent to new processing.

The app presents newly active policy bundles for affirmative review. Until review is completed, ordinary app use can be limited; eligible account-data, export, deletion-request and support routes remain subject to identity and access checks. If an available self-service route cannot be used, contact us by email or mail. Continuing to use an old tab does not silently create an acceptance receipt.

Publishing a revised policy or requiring acknowledgment of a new policy bundle does not itself authorize a new use of information already collected. We will honor the privacy commitments made when we collected that information and obtain any separate consent required for a proposed change.

Corie Jean Allen, operating as Pet E-Dex, is the primary support and privacy contact at info@petedex.com, or by mail at 2565 Bluff Drive, Kankakee, IL 60901, United States. The planned monitoring schedule is every business day, Monday–Friday; support setup is still being completed during prelaunch, and reliable email replies are not yet confirmed. The internal support inbox will follow that schedule once enabled and accessible to the authorized operator. No backup operator is currently appointed. Support is not monitored continuously, on weekends or during holidays, and no response time or service-level agreement is guaranteed. Pet E-Dex does not provide emergency veterinary or animal-care assistance. Ordinary support coverage does not extend applicable privacy or incident deadlines.