MyWorkFiles Privacy Policy

1. Information You Provide

Depending on features used, users may provide account/profile information, Work records, Life records, Files, Documents, Sheets, Contracts, Shifts, Salary information, Payslips, reminders, Automations, Workspace information, comments, review information, Ask Me inputs, aliases and support information.

2. Guest Mode

Supported local functionality may be used without an account. Guest data may be stored locally. Eligible Guest data may migrate only when a NEW account is created for the first time on the device; signing into an EXISTING account does not automatically merge unrelated Guest data.

3. Account Information

Creating an account is optional (Guest Mode is fully supported). When an account is created, we collect Name, Email Address, and User IDs (such as Firebase UID). Account creation is used for account management, authentication, and communication. Creating an account does not upload your local documents or records to Alisoplay servers.

4. Legal Consent Records

Registered accounts may store Terms acceptance state/version, acceptance time, Privacy acknowledgement state where used, acknowledgement time, interface language and limited consent history for account agreement, compliance, security and dispute purposes.

5. Local Storage

MyWorkFiles has substantial local-first functionality. Work, Life, Files/file references, Documents, Search/index information, Ask Me derived information, Automations, Personal Shifts, Salary, Payslips, Analytics-derived information, settings and Guest information may be stored locally.

6. Local-First Storage Architecture

MyWorkFiles operates on a local-first architecture. Records, tasks, attachments, payslips, spreadsheets, and personal notes are stored locally on your device. Alisoplay does not maintain hosted remote cloud storage for user files.

7. Personal Shift, Salary and Payslip Privacy

Personal Shifts, Salary Profiles, configured pay rules, payslips, salary comparisons, and related Personal Analytics are strictly stored on-device and are never uploaded to remote servers or shared with third parties.

8. Workspaces and Local Organization

Workspaces exist locally on the device to organize projects and categories. Team collaboration seats and remote workspace sync have been discontinued. Workspace records remain local.

9. Personal Information Separation

Life records, private Personal Documents, Personal Shifts, Salary Profiles, Payslips, salary comparisons and Personal Salary Analytics do not automatically become available to Workspace Owners, Editors, Reviewers or other members.

10. Files and Media Permissions

MyWorkFiles does not request or require broad READ_MEDIA_IMAGES or READ_MEDIA_VIDEO storage permissions. File access, document imports, and photo attachments are user-mediated using the standard system photo/document picker (Storage Access Framework). The app only accesses files explicitly chosen by the user.

11. Document Processing and On-Device OCR

Document scanning and text recognition (OCR) are performed entirely on-device using Google ML Kit. Scanned document images and extracted text are processed locally and are never transmitted to cloud AI services or used to train machine learning models.

12. On-Device Translation

Language translation is performed on-device using Google ML Kit. When a new translation language is selected, a static language model file may be downloaded to the device. The text you translate is processed locally and is never sent to remote servers.

13. Ask Me

Core Ask Me may use local Search, application knowledge, structured local queries, calculations, user-scoped derived information, aliases and permitted Workspace information according to current access rights. It is designed not to require a paid remote AI provider.

14. Ask Me Derived Information

Indexes, derived knowledge, cached results, aliases and other rebuildable information may be created to improve Search/Ask Me. Source records remain authoritative.

15. Automations

Automation rules, triggers, conditions, actions, execution state, run history and related resource identifiers may be processed to evaluate and execute supported Automations.

16. Analytics Inside MyWorkFiles

User-facing product Analytics may derive Work summaries, financial summaries, Shift summaries, Salary trends, period comparisons and other supported metrics from user records. These are distinct from third-party telemetry/advertising analytics.

17. Subscriptions and Purchase Information

Google Play processes subscriptions/in-app purchases. MyWorkFiles may process purchase information needed to verify entitlement, identify plans, restore purchases, handle plan changes and enforce features/limits. Alisoplay does not need the user's full payment-card number for subscription verification.

18. Device Storage Custody

Storage is managed locally on your device. Alisoplay does not impose cloud storage quotas (such as obsolete 5 GB or 20 GB tiers), because data is not hosted on Alisoplay servers. Users are responsible for managing device storage and creating backups.

19. Pro Entitlements and Purchase History

For users who purchase MyWorkFiles Pro, Google Play processes the purchase and provides purchase history tokens. We process purchase history and subscription status solely to activate Pro features (such as ad removal and premium tools) and verify entitlements. Commercial tiers are limited to Free and Pro.

20. Advertising on Free Tier and AdMob Disclosures

The Free tier of MyWorkFiles may display advertisements powered by Google Mobile Ads (AdMob), including optional rewarded video ads. For Free users, Google Mobile Ads may collect and process: Approximate location (coarse IP-based location for region/ad targeting), Device or other IDs (advertising identifier), App interactions (ad views and clicks), and Diagnostics (ad loading performance and crash data) for advertising, analytics, and fraud prevention purposes. The Pro tier is completely ad-free and disables Google Mobile Ads.

21. Advertising Consent

Terms acceptance is not consent to personalized advertising or optional tracking. Separate consent must be used where required by applicable law/platform behavior.

22. App Lock and Biometric Authentication

App Lock may use PIN/passcode and supported biometric/device authentication. OS/device mechanisms perform biometric verification; Alisoplay does not receive/store raw biometric templates merely because App Lock is enabled.

23. Notifications

Notifications may support reminders, tasks, Automations, Team activity and other enabled alerts. Sensitive content may be limited on the lock screen. Users can manage permissions.

24. Camera and Document Scanning

Camera access may be requested contextually for document/Payslip scanning and barcode/QR features. MyWorkFiles does not continuously use the Camera.

25. Location

The approved Personal Shift feature does not use continuous employee location surveillance. The released app must disclose Location only if the actual current implementation uses it.

26. Device and Technical Information

To ensure reliability and diagnose errors, the app may collect limited technical data such as device model, operating system version, crash diagnostics (via Crashlytics), and anonymous app performance metrics. This data is used solely to fix defects and maintain stability.

27. Product Usage Analytics / Telemetry

If product-usage analytics/telemetry is enabled, the provider, categories, purposes and controls must be disclosed. Private Document contents, Salary amounts, Payslip contents, private Ask Me content and Life records must not be sent merely for ordinary product analytics.

28. Crash and Diagnostic Information

If crash/diagnostic services are enabled, technical information may be processed to diagnose failures. Ordinary logs should avoid unnecessary private content and authentication secrets.

29. Support

When users contact Support, Alisoplay may process information voluntarily provided plus appropriate account/technical information such as support identifier, entitlement state, sync status, processing state and error information. Ordinary Support does not automatically have unrestricted access to private content.

30. Information Users Should Not Provide

Users should not send passwords, authentication codes, full payment-card information or unrelated private secrets through ordinary Support/feedback channels.

31. Why Information Is Processed

Information is processed solely to provide core app functionality, authenticate accounts, verify Pro subscription entitlements, deliver on-device OCR and translation, provide local search and automations, enforce local security (App Lock), deliver notifications, support crash diagnosis and app maintenance, and serve approved ads on the Free tier. We do not sell user data.

32. Sharing of Information

Personal content is not made available to other users merely because they use MyWorkFiles. Information may be shared/accessed as appropriate for explicit Workspace collaboration, resource sharing, user-directed export/share, required infrastructure processing, actual service providers, or legal/security requirements.

33. Workspace Sharing

Workspace information may be visible to authorized members according to membership, role, permissions and financial restrictions. Personal Life, Shift, Salary, Payslip and Personal Salary Analytics do not automatically become Workspace-visible.

34. Service Providers

MyWorkFiles may rely on actual enabled providers such as Google Play, Firebase, Android platform services, Google ML Kit and the actual advertising provider. Only providers actually used in the released app should be disclosed.

35. Google Play

Google Play may process app distribution, subscriptions, purchases, billing, purchase verification and marketplace functionality under Google's policies.

36. Firebase and Cloud Infrastructure

MyWorkFiles utilizes Firebase Authentication for secure sign-in and account management, and Cloud Firestore for account profile and entitlement verification metadata. User files, records, documents, and payslips are not stored in Firebase.

37. Google ML Kit On-Device Processing

Google ML Kit operates on-device for optical character recognition (OCR) and text translation. Document contents, images, and translation queries remain strictly on your device and are not uploaded to Google cloud servers.

38. Data Selling

Alisoplay does not sell users' private MyWorkFiles content to advertisers. This does not mean an enabled advertising provider never processes technical advertising data.

39. Advertiser Access to Private Content

Advertisers must not receive private Documents, Payslips, Salary records, Life records, private Ask Me content or other private user content merely for advertising targeting.

40. International Processing

Because files and documents remain on your device, your personal records do not leave your device. Account authentication metadata and crash diagnostics processed by Firebase/Google infrastructure may be processed on secure servers located in various jurisdictions in compliance with applicable data protection laws.

41. Data Security

Alisoplay uses reasonable technical/organizational measures appropriate to the service, including actual implemented authentication, access controls, security rules, permissions and platform transport. Do not claim bank-grade, military-grade, 100% security, end-to-end encryption or full local database encryption unless verified.

42. App Lock

App Lock restricts app access on the device. It does not by itself mean every locally stored database/file is separately encrypted.

43. Data Retention

Local records and documents are retained on your device for as long as you keep them. Server-side account metadata is retained while your account remains active or until you delete your account.

44. Local Data Retention

Local information may remain until the user deletes it, the feature removes it, app data is cleared, the app is uninstalled, a supported migration changes storage, or another device/app event removes it.

45. Local Data Retention and Backups

Because Alisoplay does not host your documents on remote cloud servers, deleting files in the app or clearing app storage deletes the local copy. Users control their own data retention and backup schedules.

46. Trash, Archive and Permanent Delete

Archive, Trash and Permanent Delete are different. Trash may remain recoverable; Permanent Delete may be irreversible through ordinary recovery. Derived information may be removed/invalidated with source deletion.

47. Account Deletion

Users may request account deletion where supported. Workspace ownership or dependencies may need resolution. Account deletion does not necessarily cancel Google Play subscriptions. Limited information may be retained where required/permitted for legal, transaction, security, fraud-prevention or dispute purposes.

48. Workspace Ownership and Account Deletion

If an account owns a Workspace with other members/shared resources, appropriate ownership or lifecycle resolution may be required before account deletion.

49. Subscription Cancellation Is Not Account Deletion

Cancelling a Google Play subscription stops future recurring billing but does not delete your MyWorkFiles account or local data. Conversely, deleting your MyWorkFiles account does not automatically cancel an active Google Play subscription, which must be cancelled directly in Google Play.

50. User Controls and Account Deletion

Users have full control over their data: you can edit, export, or delete local records at any time. You can request deletion of your online account and server-side metadata at any time within the app or at https://alisoplay.com/account-deletion.

51. Export

Supported export may include PDF, CSV, printing, file export or other formats. Exported copies may leave the MyWorkFiles environment.

52. User Corrections

Where automated extraction is supported, verified user corrections may take priority over later automated extraction for supported fields.

53. Children

MyWorkFiles is not designed specifically for young children. Use remains subject to applicable age, consent and contractual requirements and the actual Google Play target-audience configuration.

54. Changes to This Privacy Policy

Alisoplay may update the Privacy Policy when the product, providers, legal requirements or processing practices change. Material changes may be communicated through appropriate channels. Internal technical version identifiers need not be displayed.

55. Terms of Use

Terms govern contractual use. Viewing/acknowledging Privacy is distinct from accepting Terms. Terms acceptance does not replace separate optional-processing consent.

56. User Questions and Privacy Requests

Privacy questions or supported privacy/account requests may be sent to Alisoplay at info@alisoplay.com. Users should not send passwords, authentication codes or full payment-card information.

57. Privacy Policy Scope

The Policy applies to MyWorkFiles functionality provided by Alisoplay. Third-party services may have their own policies. User-directed exports/shares may leave the MyWorkFiles environment.

58. No Hidden Change of Purpose

Information collected for one purpose should not silently be repurposed for a materially different incompatible purpose without appropriate disclosure and, where required, user choice/consent.

59. Data Minimization

MyWorkFiles should process only information reasonably needed for functionality, security, compliance, Support or other disclosed purposes.

60. Privacy by Product Boundary

Personal Life, Personal Shifts, Salary, Payslips and Personal Salary Analytics remain private; Workspace membership does not automatically grant access; Ask Me and Automations do not override permissions; derived cache is not authoritative; supported verified user corrections take priority.

61. Contact

Privacy questions may be directed to Alisoplay at info@alisoplay.com. Do not publish private personal contact information unless separately required/approved.

This policy applies to the Alisoplay MyWorkFiles app (com.alisoplay.myworkfiles) only. For the Alisoplay web platform privacy policy, see here.

Request account deletion