KitVergeOrganize equipment, record inspections and manage returns with local records.
Privacy PolicyKitVerge is an equipment-kit organization, inspection, checkout, return and reporting application from DEWAN ENGINEERING WORKS. It keeps manually entered kit information in device storage rather than requiring an account. Its purpose is to help users maintain understandable equipment records and local activity history.
KitVerge gives you a place to name kits, describe equipment and note where items are stored. Categories, quantities and serial labels help give each local entry useful context.
Preparation and return inspection entries record checklists, conditions and timestamps. The history helps you look back at what was entered for a kit.
The app is intended for general equipment management rather than specifically for children. DEWAN ENGINEERING WORKS provides KitVerge for organizing day-to-day equipment records.
Kit readiness is calculated from entries you make. KitVerge does not independently locate, identify, scan or physically confirm the equipment itself.
The app brings different parts of equipment record-keeping into one local workflow. Each feature relies on the details that you enter, not on remote tracking or independent equipment verification. Online decorative imagery is separate from the core records, which remain usable without a connection.
Enter kit names, storage locations, categories and notes. Record equipment quantities, serial labels and descriptions as details of each kit.
Use preparation and return checklists to document what is present or damaged. Readiness summaries derive from the quantities and condition details entered in the app.
Record who or what a kit is assigned to, its purpose, and expected or actual return dates. Assignment labels may contain a person’s or team’s name if you choose to include one.
Browse local searches, filters, summaries and charts built from the same records. Request PDF reports, CSV exports or JSON backups when you want copies.
Decorative equipment images may load from Unsplash infrastructure over HTTPS using Glide. The app can still handle its main kit tasks when no internet connection is available.
Theme, country and onboarding-completion preferences can be retained on the device. No account is necessary to use the main equipment features.
The policy distinguishes between data held inside the app and files that you decide to save elsewhere. Your entries drive local searches, calculations and histories. Sending information to another service is a separate action, such as exporting a file or choosing to email support.
Kit information, assignment labels, inspections and personal notes are entered or generated in the app. Free-text fields may contain personal data if you type it there, so avoid unnecessary sensitive information.
The Room database and SharedPreferences keep core records and settings in Android app storage. The app does not automatically send its kit database to the developer’s server.
Kit readiness, missing and damaged counts, histories and summaries are based on saved manual records. They are not a claim that an item has been physically inspected by software.
A CSV, PDF or JSON file is created on your request and saved using Android’s file picker. The destination can be local storage or a third-party document provider.
Some records with audit history can be archived rather than deleted. Clearing app storage or uninstalling removes app-private information ordinarily, but exported files require separate deletion.
KitVerge keeps its main records in Android app storage and does not require a login. There are a few important exceptions and boundaries to understand: optional online image requests, manually exported files and messages sent through your email provider. These choices affect who may receive technical or shared information.
The core kit-management features are available without sign-in or remote account sync. The reviewed version has no advertising or analytics-tracking SDK.
Photograph requests can expose connection metadata such as an IP address to image infrastructure. Kit names and inspection notes are not intentionally added to those requests.
JSON backup files can hold kit records, inspections, assignments and preferences. Protect exported copies because the app does not encrypt these backup files.
The manifest uses INTERNET for photos but does not request camera, microphone, precise location, contacts, SMS, calls or broad storage access.
Contact Support opens a compatible email app; sending a message is your choice. The developer does not automatically send the email.
Android’s app sandbox helps restrict unrelated apps, but the app does not claim extra application-level database encryption. A device screen lock and careful file handling remain important.
You decide what goes into your kit records and whether to export them. You can work offline, update eligible entries and clear private app storage using Android settings. Keep in mind that archived audit histories and files saved outside the app are handled differently from ordinary deletable records.
You control which kit descriptions, assignment labels, replacement estimates and notes you enter. Avoid adding more personal detail than a record needs.
Kit management, inspections, checkout, local reports and backups remain usable offline. Decorative images may instead show a fallback when unavailable.
Eligible equipment records can be edited, and kits may be deleted or archived under the history-preservation rules. This helps avoid silently discarding the audit trail.
Create a PDF, CSV or JSON copy, or initiate a validated, confirmed restore. Remember that an exported backup may remain wherever you saved it.
Android Settings can clear KitVerge’s storage, and uninstalling ordinarily removes app-private records. Exported copies and previously sent support emails are separate.
The developer can be contacted using the support address named in the policy. Applicable privacy-law rights continue to apply, and support correspondence deletion can be requested subject to legal obligations.
Good equipment records depend on both careful entries and sensible file handling. KitVerge uses Android’s local storage protections, while also recognizing the limitations of device security and unencrypted exports. Understanding third-party destinations and the difference between a record and a physical check helps users interpret the app correctly.
The local Android app sandbox offers a measure of protection against unrelated apps. Still, no storage or transmission system can be guaranteed completely secure, and exported JSON files have no app-level encryption.
Unsplash infrastructure can process request information when a decorative image is loaded. Email services and any selected third-party document destination can process information according to their own policies.
Clearing KitVerge storage does not automatically remove a PDF, CSV or JSON file placed elsewhere. You may need to delete those files and any remote copies directly from the service that holds them.
The current app does not process banking or payments. Manually entered replacement-cost estimates are only local record-keeping values, and equipment readiness is based on records rather than physical scanning.
The policy identifies its effective and last-updated dates. It says future changes to functionality, services or handling practices will be reflected in an updated policy, with notices for material changes when required.
See the complete wording on local data, image providers, exports, security and retention.
Read the Privacy Policy