వికాసం · Vikasam
Privacy policy

Vikasam supports ITI attendance, teaching records, feedback and on-the-job training. This policy describes the Android app and its supporting account and database services. Accounts are provided by an authorised institute or the Vikasam team.

Information the app uses

• Account and institute details: name, email address or trainee identifier, account ID, role, institute and trade. Sign-in credentials are processed by Firebase Authentication.
• Training records: attendance, teaching progress, feedback, assessment activity, tasks and OJT records that you or your institute enter.
• Camera and face attendance: when you choose face enrolment, the app processes camera frames on your device and saves a numerical face template, your trainee identifier and a device identifier in the database. Attendance checks compare a live face with that template. The face-attendance flow does not upload the camera video or a face photograph.
• Location: with your permission, attendance and OJT check-ins can record precise coordinates, time and distance from the selected site. Vikasam does not request background location.
• Uploaded photographs: workshop photographs you choose to submit are uploaded to Cloudinary. Do not include unrelated people or private documents in a workshop photograph.
• Device and activity details: a device identifier, sign-in information and actions recorded in the app help associate entries with an account and investigate errors or attendance discrepancies. Service providers also process network information needed to deliver their services.

How information is used

Information is used to sign you in, provide the selected institute workflows, show records to authorised staff, associate entries with their author, and support the app. Face templates and location records are used for attendance verification. They are not used for advertising. Vikasam does not show advertisements or use Android's advertising ID.

Who receives information

Records are available to the institute and authorised officers according to their access. Google Firebase provides authentication and database services. Cloudinary stores submitted workshop photographs. Map tiles are supplied by Esri; opening a map sends requests for the viewed map area and ordinary network information to that provider. Opening an external website, email or WhatsApp link is governed by that service's own privacy policy.

The Android release does not include paid AI service credentials. Face matching runs on the device. A future change that sends information to another service will require an updated policy and any necessary notice or permission.

Your choices

You can decline camera or location access, or revoke permission in Android settings. Features requiring that permission will be unavailable. Contact your institute about an alternative attendance method. Accounts and training records cannot be made public through a self-service sign-up in this app.

Retention and deletion

Account and training records are retained for the institute's use and authorised record-keeping. To request access, correction, account closure, or deletion of a face template or other personal data, email workwithdevit@gmail.com with your institute and account identifier. Do not send your password, a face image or identity documents in the initial email.

The Vikasam team will verify the request and coordinate with the institute. Records that must remain for authorised educational, audit or legal purposes may be retained; the response will explain the applicable limitation. Removing the app from your phone does not delete server records.

Security and contact

Network connections to the app's authentication, database and upload services use HTTPS. Account access is controlled through authentication and database permissions. Data may be processed in the locations used by the named service providers; this policy does not claim India-only storage.

For privacy questions, contact WEDEVIT PRIVATE LIMITED at workwithdevit@gmail.com. Material changes to this policy will be reflected in the updated date and, where appropriate, in the app.