Privacy Policy

Scope

This draft covers the Veda mobile app, which connects people seeking care for a loved one (care seekers) with care providers, and this informational website. It is meant to describe the app as currently built.

Owner decision needed: Confirm the legal entity name that operates Veda and that will be responsible for this policy.

Owner decision needed: Confirm whether this policy also covers the website and any other channels, and which regions and users it applies to.

Data categories and purposes

Based on the current app, Veda handles the following categories of information. Each is used to operate the features described.

• Account information: email address, phone number, and a password (stored only as a one-way hash), plus sign-in session tokens, used to create and secure your account.
• Profile information: display name, city, ZIP code, profile photo, and an about section. Care seekers also provide the care recipient’s age group, care needs, and preferred languages. Providers add details about the care they offer. This is used to show profiles and to match care seekers with providers.
• Location and search filters: ZIP codes on profiles and care requests, used to find providers and requests nearby.
• Care requests, applications, and engagements: what you post or apply for, and the status of resulting engagements.
• Messages: the content of messages exchanged between care seekers and providers in the app.
• Provider verification information: license type and number, legal name, and license check results, used to check a license against a public registry. Providers may also consent to a background check, which involves a third-party vendor; the app stores the consent, order status, and a non-identifying summary. A check or license lookup is not a guarantee about any provider.
• Payment information: payment method references (card brand and last four digits), payment and payout amounts, and provider payout account status. Full card details are handled by a payment processor rather than stored in the app database.
• Reviews: ratings and written reviews.
• Push notifications: a device notification token and your notification preferences, used to send alerts such as new messages, applicants, booking updates, payment receipts, and reviews.
• Photos and device features: the app asks permission to access your photo library so you can choose a profile picture. On supported devices it can use Face ID to unlock the app; the app does not receive your biometric data.

Owner decision needed: Confirm this list against actual production collection, including analytics, crash reporting, logs, and any data not visible in the code.

Sharing and service providers

Veda shares information between users as needed for the service, for example a profile shown to another user or a message delivered to its recipient. Veda also appears to rely on outside services to run features such as payments and payouts, background checks, license lookups, and push notifications.

Owner decision needed: Provide the confirmed list of service providers (for example the payment processor, background-check vendor, and notification service), what each receives, and where it is processed.

Owner decision needed: State whether Veda sells or shares personal information for advertising, and any legal-disclosure practices.

Retention and deletion

This draft does not state retention periods because none have been confirmed.

Owner decision needed: Provide retention periods for each data category, how account deletion works, and what must be kept for legal, payment, or safety reasons.

Your rights

Depending on where you live, you may have rights to access, correct, delete, or export your information, or to object to certain uses. The specific rights and how to use them have not been finalized.

Owner decision needed: Confirm the rights offered, applicable laws (for example state privacy laws), how requests are verified and answered, and the age and children’s privacy position.

Contact

Privacy questions and requests will be directed to the operator once contact details are confirmed.

Owner decision needed: Provide the operator’s legal name, mailing address, and a verified privacy contact channel. None is shown here on purpose.