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

Registered-account information is processed as needed for authentication, account maintenance, supported Cloud/Team features, entitlements, security, consent records, recovery and management. Alisoplay does not store a user's Google password.

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. Cloud Functionality

Cloud-enabled plans may provide supported sync, backup, multi-device, Team/Workspace and Cloud storage. Purchasing Cloud does not mean every local item is uploaded.

7. Current Personal Shift / Salary / Payslip Cloud Status

At the current implementation, Personal Shifts, Salary Profiles, Salary rules, Payslips, salary comparisons and related Personal Salary Analytics are local-only unless the app expressly indicates owner-private Cloud synchronization has been implemented.

8. Workspace and Team Information

Workspace identity/settings, membership, roles, seats, invitations, permissions, shared Work resources, comments, review requests, activity and supported Team notifications may be processed to provide collaboration and access control.

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

MyWorkFiles may store supported files in app-controlled storage, supported Cloud storage where applicable, or references to files elsewhere on the device, depending on feature and user action.

11. Document Processing and OCR

On-device OCR/local document processing may identify text, dates, amounts, document types, deadlines, Payslip fields and other structured information. Automated extraction may contain errors.

12. On-Device Translation

Supported on-device machine translation may require downloading language models. The approved path does not require a paid per-translation Cloud API. Machine translation may contain errors and is not certified.

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. Cloud Storage Usage

Cloud usage information may be processed to measure usage, display capacity, warn users, enforce quotas and support storage management. Cloud includes 5 GB; Complete 20 GB; optional add-ons may be available.

19. Team Seats and Entitlements

Plan, Full Seats, Reviewer Seats, membership, role, permissions, Cloud/storage entitlement and other capabilities may be processed to enforce purchased/assigned functionality.

20. Rewarded Advertising

The Free plan uses/targets optional Rewarded Video advertising for clearly identified additional uses/benefits. The actual released AdMob/provider implementation and consent behavior must be disclosed accurately. Paid plans are intended to be ad-free.

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

Limited technical information may be processed as needed for authentication, security, Cloud connectivity, subscription verification, reliability, error diagnosis and compatibility, depending on enabled SDKs/services.

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 may be processed to provide app functionality, organize records, authenticate accounts, provide Cloud/Team features, enforce permissions, Search, Ask Me, Automations, document processing, translation, Salary estimates, Payslip comparison, user-facing Analytics, subscription verification, quotas/seats, notifications, security, diagnostics, Support, legal-consent records and applicable legal obligations.

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 / Cloud Services

MyWorkFiles uses actual enabled Firebase services for supported account, Cloud, Team and other functionality. The published policy must identify only Firebase products actually used in the released processing path.

37. ML Kit

Supported Google ML Kit functionality may be used for implemented on-device OCR/translation. Some functionality may require downloading device-side models/components.

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

Depending on actual Cloud/platform/billing/support providers, information may be processed in countries other than the user's country. Do not promise all Cloud information remains physically in the user's country unless verified.

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

Retention depends on feature, local/Cloud status, user actions, account/Workspace/subscription status, security needs, legal obligations and technical requirements. Do not invent a universal fixed retention period.

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. Cloud Data Retention

Cloud information may remain according to the supported account/Workspace lifecycle. Cancellation/downgrade does not by itself authorize immediate deletion of ordinary Cloud records.

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 Pro, Cloud, Complete or an add-on does not itself delete the MyWorkFiles account or ordinary records.

50. User Controls

Depending on feature, users may create, view, edit, correct, archive, delete, restore, export, share, stop sharing, manage permissions, Automations, notifications, App Lock, marketplace subscriptions, Cloud storage and 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.