Privacy Policy - Workora

Who we are

We provide a mobile application for tracking work time for teams.

What data we collect

• Account information: When you sign up or sign in, we process identifiers required to authenticate you. Sign-in is handled by our authentication provider using email-style identifiers (for example, addresses derived from owner or employee usernames as implemented in the app).
• Organization and employment relationship: To connect the right people to the right workspace, we store a mapping between your account and an organization identifier (typically tied to the business owner’s account), and your role (for example, owner or employee), as needed for the app to function.
• App usage and workforce data: Information you enter or generate in the app may include business/owner profile fields, employee names, shift start/end times, hours summaries, payment-related notices shown in the app, and activity logs recorded for operational visibility within the workspace. This data is stored to provide the service to your organization as designed.

How we use data

We use this information only to operate the app: authentication, syncing data for your organization, and showing records and summaries to owners and employees in accordance with how the product is built. We do not use this data for advertising.

Where data is stored

We use Google Firebase, including Firebase Authentication and Cloud Firestore, to host authentication and application data. Data is stored in logical organization-scoped structures (for example, documents keyed to an organization) and related configuration needed for access control. Processing may occur on Google’s infrastructure in line with Google’s and Firebase’s terms and the settings of the Firebase project used by the app.

Sharing

We do not sell your personal information. Data may be processed by service providers (such as Google / Firebase) strictly to run and host the app.

Security

We rely on industry-standard protections provided by Firebase, transport encryption (such as HTTPS) where applicable, and access rules intended to limit Firestore access to authenticated users in connection with their organization membership as implemented in the app.