Status and scope.
This working privacy notice describes the IPDI website and the application behavior confirmed by the developer on 23 October 2026. The app is under development. Provider identities, retention and account-deletion details still require confirmation before the notice is finalized.
The identified developer is Natural Vision Global Private Limited. Questions and requests can be directed to hello@ipdi.in. The company’s registered address, applicable legal contact and jurisdiction require owner confirmation.
The marketing website.
The website presents product information and fictional demonstrations. It is not connected to the app’s production customer database. Public previews replace personal customer details and use an illustrative Eye PD portrait.
An enquiry asks for a name, reply email, shop, request topic, preferred device, message and consent to a reply. The purpose is handling the request. On the live website, it is sent to the configured team inbox through the website mail service. The theme does not save enquiry content in a separate leads database. Do not include prescriptions, customer records, face images or payment credentials.
The live website uses Google Analytics through the Google Site Kit plugin to measure website traffic and interactions. A browser-local motion preference is separate from Analytics and does not disable it. The complete cookie inventory, Analytics retention and consent configuration, hosting logs and email-delivery practices require owner review.
Application data and cloud access.
IPDI uses sign-in accounts for its subscription service. Supabase is used for cloud services. Customer records, bills and prescriptions are stored in the cloud so an account holder can access their information after signing in on another device.
Camera photos, facial data and depth data used for Eye PD are processed on the device and are not uploaded to any server. The workflow displays the calculated PD number. Whether a derived PD number can be saved with a customer record must be confirmed for the release.
Other application details to confirm.
The app interfaces also show linked families, payment balances, orders, reports and business-profile information. The precise field inventory, access permissions and retention rules must be confirmed against the shipping release.
The developer must confirm the controller and provider responsibilities, processing purposes, account fields and each relevant user group.
- Account identifiers and sign-in providers.
- Customer profiles, family relationships and optical records.
- Invoices, payments, order records and business details.
- Camera access, face imagery, depth data, derived PD values and their storage or transmission.
- Biometric authentication behavior and whether the app receives only a system result.
- Device information, diagnostics, crash reports, analytics and notification services.
Camera and biometric permissions.
Eye PD camera photos, facial data and depth data are processed locally on the device and are not uploaded to a server. Camera access is used for the PD workflow.
The app access screen also shows Face ID on supported devices. Authentication-provider behavior, the system result available to the app and platform-specific permission details still need confirmation. Do not infer that cloud customer records are local-only from the Eye PD processing behavior.
Service providers and sharing.
The developer has identified Supabase as the cloud provider. The configured project region, service configuration, authentication methods, retention and backup settings must be confirmed before release. Website hosting, email and any diagnostics providers also need to be identified.
A PDF, WhatsApp handoff, print action or device share sheet may involve another service selected by a user. The final policy must explain the actual handoff and which information leaves IPDI. No sale, advertising use or third-party sharing guarantee is asserted in this draft.
Retention, security and offline copies.
No verified retention schedule, backup-deletion interval or account-closure timeline has been supplied. The final policy must distinguish live records, enquiries, device copies, logs, backups and any records that must be retained for a valid obligation.
No encryption standard, certification or absolute security guarantee is claimed. The final policy must describe verified safeguards and the limits of access control, offline storage, synchronization and deletion on a device.
Requests and choices.
Email hello@ipdi.in to ask about access, correction, deletion or another privacy concern. Include the nature of the request and an email address for a reply. The team may need proportionate information to verify identity and authority before handling account or customer records.
Do not send passwords, PINs or identity documents with an initial request. Submitting a request does not itself perform account deletion. Applicable rights, exceptions, response periods, escalation routes and authorized representatives must be confirmed in the final approved policy.
Children, retailer responsibilities and changes.
Family-linked records can potentially include information about children. The owner must confirm whether the service permits this, who can provide it, the age and consent arrangements and any special safeguards.
Retailers must have appropriate authority to enter, use and share information about their customers. The final terms and policy must clarify the retailer’s responsibilities and the developer’s role.
The effective date and notification process for policy changes will be established after owner and legal approval. This draft should not be described as an approved app-store privacy disclosure.
Required owner decisions before publication.
Confirm each item against the deployed website and the shipping app, then obtain the review appropriate to the business and its markets.
- Legal identity, registered address, contact role and applicable markets.
- Data inventory, purposes, responsibilities and any applicable processing agreements.
- Configured Supabase region, service roles and any other providers or international data flows.
- Camera, depth-data and biometric behavior on each platform.
- Retention, backups, account deletion and device-copy handling.
- Diagnostics, analytics, cookies and any future marketing tools.
- User rights process, identity checks, timelines and complaint route.
- Children’s records and retailer authority to process customer information.