Privacy Policy

1. Scope and publisher

This policy describes Veromtec Calendar for Android, including its planner, business tools, notes, document reader and alarms. The app has no publisher-operated user account or automatic record-sync service. Local app locks are not online accounts.

Publisher: Roman Liskin. Privacy and support contact: veromtec@gmail.com. Effective date: 2026-10-26.

2. Plain-language summary

3. Your records stay on your device

Calendar events and tasks, imported calendar schedules and retained original .ics files, client and supplier details, inventory and service records, local charges, payments, refunds and correction history, notes and recordings, imported documents and attachments, file names and paths, file metadata, reader search and recent-file history, reading progress, favourites, folders, bookmarks, saved file-tool outputs, alarm settings and preferences are stored on your device. The app does not send these records to the publisher, AdMob or the purchase-verification service for storage, advertising or entitlement checks.

Some files remain at a location you selected rather than inside the app. Android notifications, home-screen widgets and the optional floating-notes bubble can display record content on your device; control their visibility in the app and Android settings. App-private storage and app/note locks do not mean every live database or document is separately encrypted. Device security still matters.

4. Backups, exports and sharing

New full backups are password-protected .vbackup files using AES-256-GCM and a password-derived key. They include managed planner and business records, notes and media, reader documents and tool files, logical alarms and preferences. Running timers/stopwatches, app/note credentials, device permission grants and paid entitlements are not portable backup data. Keep your password safe: the publisher cannot recover it. A derived key is held in device secure storage for configured automatic backups; the password itself is not stored.

Automatic backups run when the app is open or reopened, stay on this device, and retain up to 20 local copies. The app disables Android automatic cloud backup and excludes its data from Android device-transfer backup rules. Local copies can be lost with the app or device. Saving or sharing an encrypted copy uses the Android destination or recipient you choose, which may be a cloud provider. The app does not automatically upload backups; a share handoff does not prove delivery. The selected provider's handling applies after export.

ICS calendar exports and retained-original exports, CSV exports, ordinary note/document sharing and files handed to external editors are unencrypted exports, unless you independently protect them. CSV and ICS are not full backups. Local .ics import has a preview and explicit duplicate choices, does not fetch attachment URLs or activate invitations and alarms, and keeps the complete selected source inside the app after confirmation. Calendar export includes selected event series; skipped components and file-level properties remain available in retained-original exports. Imported series are updated by reimporting a file rather than by the simple event editor. Legacy ZIP/JSON restores may contain unencrypted records; old device-key encrypted backups require their original installation key. Restoring replaces managed local data after confirmation and validation. Exported copies are not remotely revoked or erased by deleting app records.

5. Permissions and reminders

You can use the planner, notes and files without granting alarm permissions. Notifications are requested for reminders; precise clock alarms additionally need exact-alarm access. Full-screen presentation and battery settings affect behavior but are optional. Android restrictions, force-stop, reboot/unlock, power loss and time changes can delay or prevent alerts. Do not use this app as your only safety-critical alarm.

Microphone access supports recordings you initiate. Camera access supports scanning or images you select; file/photo pickers support imports and attachments. Biometric/device authentication is handled by Android; the app does not receive your biometric template. Overlay access is for the optional floating-notes bubble. You can revoke permissions in Android settings; related features may stop working without preventing access to existing records.

6. Advertising: Google AdMob

The seven-day in-app preview may show Google AdMob ads when the ad consent system permits requests. Paid subscribers are ad-free; expiry does not start a new ad-supported trial. Google User Messaging Platform (UMP) requests consent information and shows consent or privacy choices when required. When Google requires a privacy-options form, it is available under Help & support and the privacy policy screen. Consent does not imply that no data leaves the device.

Google's Mobile Ads SDK collects and shares IP addresses (which can indicate approximate location), app/ad interactions, diagnostic information, and device or account identifiers such as the advertising ID and app set ID, for advertising, measurement and fraud prevention. Actual handling depends on consent, Google settings and the configured ad providers. The app does not supply your planner, client, note or document contents as ad targeting data. Google processes ad data under its own policies and retention rules. Android advertising-ID controls and available ad privacy choices provide additional controls.

7. Google Play purchases and verification

Google Play handles subscription checkout, payment details, purchase history and subscription management under Google's policies. The app receives purchase status and a purchase token; it does not receive your full card details. The token and signed entitlement are stored in device secure storage and are excluded from portable record backups.

The app checks Google Play billing availability and product information at startup and periodically while running. When a purchase token is available, it also attempts to refresh verification with the configured service. These checks can happen without opening checkout; they are separate from the external links you choose to open.

For Google Play purchases, verification sends the purchase token, a random installation identifier and a random request nonce over HTTPS to the configured verification service. That service sends the token and fixed app package to Google Play's Publisher API, checks subscription status and expiry, acknowledges eligible purchases and returns a signed entitlement. No email, advertising ID, calendar/client/note/document content or backup is sent by this verification request.

If you explicitly enter a publisher-supplied review access code, the app sends that code, its random installation identifier and a request nonce to the same verification service over HTTPS. This optional complimentary grant is separate from a Google Play purchase or subscription. Your code and signed grant are held in device secure storage, excluded from portable backups, and used to refresh access after activation. The server checks a protected credential hash and does not retain the submitted code or record contents. A cached grant lasts at most 24 hours after verification. Deactivating review access removes its local code and grant without cancelling or deleting a real subscription. Local records, personal tools and backup/export remain available. Review grants are unavailable unless the publisher has configured the service to issue them.

Verification operator: Roman Liskin. Endpoint: https://veromtec.com/calendar-purchases/v1/entitlements/verify. The service does not create user accounts or keep purchase histories, purchase tokens, installation identifiers or request nonces in a database or application logs. It keeps only the temporary abuse-prevention counters described below. Checkout is disabled when verification is unconfigured.

To limit automated verification requests, the service derives rotating keyed hashes (HMACs) from connection IP addresses. Its private counter store contains these temporary identifiers, request-rate counters, update and expiry times, and one global counter. Raw IP addresses and purchase-request contents are not written to this store. These counters contain no calendar, client, note, document or backup contents.

The keyed identifiers rotate every 10 minutes. Expired counters are deleted when requests arrive and by a cleanup task scheduled every 5 minutes. Application counter retention is approximately 15 minutes when the scheduled cleanup is operating correctly. If cleanup stops and no new requests arrive, expired counters remain until cleanup or requests resume. This counter retention does not describe hosting logs or provider backups.

Hosting and network infrastructure can separately process raw IP addresses, request times and operational metadata. Hosting access-log retention has not yet been verified. Hosting metadata/log retention status: The application does not persist purchase tokens, installation identifiers or purchase histories, and does not intentionally log request bodies. Abuse-prevention counters use keyed IP identifiers that rotate every 10 minutes; expired counters are removed on requests and by a configured five-minute cleanup job, normally within about 15 minutes. Hosting infrastructure may separately retain IP addresses, requested paths and timestamps. The hosting provider's access-log and backup retention periods have not yet been verified; no fixed deletion period is claimed for those provider records. These infrastructure logs are separate from the temporary counter store.

Verified paid access can work offline for at most 24 hours after a successful check, capped at subscription expiry. A connection is then needed to renew that access. Local records, personal tools and backup/export remain available when paid access cannot be verified. There is no promise of immediate refund/revocation detection on an offline device.

8. Barcode scanning: Google ML Kit

Inventory barcode scanning uses the bundled Google ML Kit barcode scanner through mobile_scanner, with automatic zoom enabled. Camera frames and decoded barcode results are processed on your device; ML Kit does not upload those images or decoded contents to Google. The selected barcode can be saved in your local inventory record.

ML Kit sends device and app information, per-installation identifiers, performance measurements, API configuration, input/output sizes, feature versions, events and errors to Google for diagnostics and usage analytics. Automatic zoom also sends a generated scanning-session identifier, zoom changes and predicted barcode-boundary coordinates. Google documents HTTPS protection for this technical data. ML Kit may contact Google for maintenance or compatibility information. These SDK diagnostics are separate from advertising consent. You can avoid camera scanning or revoke camera permission in Android settings.

9. External actions and support

Opening a website, a record's URL, a WhatsApp action, an external document editor, Google Play or a storage/share destination hands the selected link, file or message to another application or service. Those recipients may receive content and connection metadata under their own policies. Public policy pages may produce ordinary web-host access logs. These actions are initiated by you.

Contacting support sends only what you choose to put in your email or support request. No records, logs, backup, purchase token, password or attachment are automatically included by the support entry. Avoid sending confidential records or passwords. Support correspondence is handled by the publisher and its chosen email/support provider. Retention: Support messages remain in the publisher's email account until deleted. You can request deletion using the support address. Information needed for an unresolved request or a legal obligation may be retained for that purpose; no automatic deletion schedule is currently configured.

10. Retention, deletion and your choices

Local records remain until you delete them, use the relevant cleanup controls, clear app storage or uninstall. Deleting a client or appointment preserves payment history and saved client/appointment labels. Voiding or correcting a payment entry keeps its original in history. To erase this history, select Payments & balances in the authenticated data-wipe controls; a full planner wipe also erases it. Notes may remain in trash until permanently deleted. Deleting imported events retains their original .ics source until you explicitly remove it after its linked series are deleted. A calendar-data wipe or full planner wipe removes retained sources; external original files and exported copies remain at their chosen locations. Deleting a record does not remove older backups, exported files or copies retained by another app. Settings data-wipe options cover the selected planner data; remove reader/tool files and alarms in their respective tools, or clear Android app storage to remove all app-private data. Files saved outside app-private storage must be deleted at their destination.

There is no publisher account or remote copy of your planner database for the publisher to delete or recover. For a privacy request about support correspondence or verification metadata, use the contact above. Google independently controls its purchase and ad records; use Google's privacy/account controls for those records. Clearing storage or uninstalling does not cancel a Play subscription.

11. Security, changes and questions

Backups use authenticated encryption; purchase verification uses HTTPS and signed, time-limited entitlements. Android app-private storage and secure storage protect different kinds of local data. No security measure guarantees protection against a compromised device, a weak/disclosed password or copies you share. Keep Android updated and keep an exported encrypted backup.

Changes to data handling will be reflected in an updated dated policy and relevant in-app disclosures before new uses that require them. Contact veromtec@gmail.com about this policy. This policy is currently provided in English.

12. Third-party privacy information

Google provides advertising, billing and scanner services. The configured verifier handles purchase checks. Email, messaging, editing and storage providers receive information when you choose their services. Each recipient handles its own records and retention under its policies.

13. Contact and privacy requests

Publisher: Roman Liskin
Privacy contact: veromtec@gmail.com
Website: https://veromtec.com

Identify the app and the information your request concerns. Use the deletion controls described above for records held only on your device. For information held by Google or another recipient, use that provider’s privacy controls.

14. Data-practice summary

On smaller screens, scroll the table sideways to read all four columns.