Effective: 8 October 2026 · OnTimeShift closed testing

OnTimeShift (OTS) helps companies manage attendance, shifts, locations and team access. Contact the developer at bokimk.ap@gmail.com for privacy questions.

Data we process

• Account: email address, account identifier and sign-in details processed by Firebase Authentication. Google sign-in supplies the account identity you choose. Passwords are not stored in workplace records.
• Workplace: name, optional phone number, company membership, role, assigned locations, job categories, invitations, schedules, attendance, breaks and corrections.
• Requests and notes: time-off types, dates, reasons and notes you submit. A sick-leave request or note may contain health information; avoid unnecessary sensitive detail.
• Location: at attendance verification we obtain your current location, accuracy and timestamp to verify the workplace radius. Verified attendance stores location coordinates. There is no continuous background tracking.
• QR: Google Code Scanner processes a location QR code for attendance verification. The app sends the decoded attendance code to the server; it does not upload camera images.
• Security: Firebase App Check and Google Play Integrity process device/app attestation information to help prevent unauthorized access. Google Play handles app update availability and download status.
• On-device settings: selected language and local UI preferences. Optional profile photos are resized to a small JPEG and stored with your company profile in Firestore. Authorized managers can see team avatars. You can replace or remove your photo in Account.

Workplace map and testing

When you choose a workplace point on the map, OpenStreetMap supplies map tiles and receives the network address and map area requested. No continuous tracking occurs. The foreground current-position button uses location permission to fill workplace coordinates for your confirmation. A manager may enable a seven-day test attendance window for a location. Such records are explicitly marked unverified and contain no QR or GPS evidence. Normal verified attendance still requires QR and location checks.

Purpose and access

We use data for sign-in, workplace attendance and shift planning, cloud synchronization, corrections, requests and security. Authorized company owners and managers can access team records within their permissions; employees can access their own permitted records. Firebase and Google services process data on our behalf. We do not sell personal data.

Storage and choices

Cloud workplace records are stored in Firebase Firestore; the configured workplace backend is in Europe. Google authentication and security services may process data in other locations. Transfers to the backend use encrypted connections. Records remain available for your company account until deleted or subject to a disclosed retention requirement. You can deny location permission, but verified attendance then cannot be recorded. You can ask your company manager to correct workplace records.

Deletion

Request account and data deletion

Use the deletion page without installing the app, or open Request account deletion from Welcome or Account. Support verifies account ownership and explains the expected completion date and any specific legally required retention. Signing out or uninstalling does not delete cloud data.

Team PINs, notifications, advertising and subscriptions

Employee access uses a PIN and email address; initial access and recovery verify email ownership. Authorized full-access managers can view team PINs within their permissions. PINs are not included in exported reports or notification text. Optional shift reminders and manager announcements use Firebase Cloud Messaging device tokens and your selected reminder time. You can change reminders and notification permissions.

Trial and Free companies display a small Google AdMob banner. Google Mobile Ads may process device or advertising identifiers, network information and ad interactions for advertising, measurement and fraud prevention. Where required, Google User Messaging Platform asks for your privacy choices. Settings provides advertising privacy options when available. Paid company subscriptions remove banners for the company team. Google Play handles payment; our server processes purchase tokens, product identifiers and subscription status to verify company access. We do not receive full payment card details. OnTimeShift is a workplace app and is not directed at children.

This informational website

Website information updated 15 October 2026. The public pages provide product information, reference USD pricing and help. This site does not collect attendance, authenticate workplace employees, take payments or display AdMob advertisements. The support-ticket form, when enabled, is described below. Help search and filters run in your browser; your query is not sent to an analytics service. Images and website assets are served with the page. Hosting providers may process network and technical request information to deliver and protect the site.

The website does not set optional advertising or analytics cookies. External Facebook, Google and email links have their own privacy practices. If you contact us, the information you choose to send is used to answer your request. Do not send passwords, PINs or live verification links.

For Google service information, see Google Privacy Policy and how Google uses information from partner sites and apps. Advertising choices for the Android app are managed in the app, separately from this website.

Website support tickets

If online ticket delivery is enabled, the support form collects the name, reply email, topic, subject, message and optional company/app version you choose to submit. Requests are stored privately in Google Firebase with a ticket reference and delivery status and sent to bokimk.ap@gmail.com through Gmail. Boki can reply to your submitted email address. We use these details to answer and manage your support request, not for advertising. Do not include passwords, PINs, verification links or unnecessary sensitive employee information.

The server validates submissions and limits repeated attempts. It stores a keyed, non-readable representation of the request network address in short-lived rate-limit records; raw IP addresses are not stored in the ticket database. Ticket data is retained as needed to resolve the request and for applicable recordkeeping, with access restricted to support operations. Contact support to ask about your ticket data. If ticket delivery is not configured, the form is disabled and does not submit your message.

See Google’s Privacy Policy. A ticket reference confirms that a submission was accepted for email delivery; it is not an account-deletion confirmation.