Frequently Asked Questions

No. SlidesClock never runs continuous background location tracking. Location coordinates are accessed only at the exact point in time when an employee slides to clock in or out under a branch GPS policy, or when a manager explicitly captures coordinates to establish a workplace geofence radius. When the app is closed or between shifts, location is not monitored.

Apple iOS does not allow standard third-party apps to access Wi-Fi SSID or BSSID network names for attendance check-ins. Therefore, iOS network verification relies on the public IP address observed by the SlidesClock server. On Android, the app may transmit SSID/BSSID when available. Managers can configure authorized office IP addresses and network identifiers in branch settings.

Registered device checks bind an employee’s company membership to their primary smartphone, recording the device model, operating system description, and IDFV (on iOS). This helps organizations review which registered device submitted an attendance action. Note that while device registration is operational, hardware-level cryptographic attestation is not active, and SlidesClock does not claim to be tamper-proof or spoof-proof.

Yes. Attendance verification policies are configured per branch. For example, a central corporate office can enforce Wi-Fi network verification, an outdoor warehouse can enforce GPS geofencing, and a retail store can enforce a combination of both.

Managers configure shift start and end times, overnight hours, and scheduled rest days. Organizations can set a configurable grace period (for example, 5, 10, or 15 minutes) before a clock-in is flagged as late. The employer organization retains full authority over company policies and employment decisions.

Employees can submit an attendance correction request directly in the mobile app, with mandatory explanatory notes. The branch manager reviews the evidence before approving or declining. To maintain absolute audit integrity, original punch events are never overwritten or silently deleted; approved corrections are stored as independent adjustment events with a permanent supervisor audit log.

Payroll is completely optional and plan-dependent. SlidesClock is designed so that companies can use attendance, shifts, leave, and corrections without ever enabling or configuring payroll. For companies that do enable payroll, it serves as an administrative calculation tool; employers remain solely responsible for compliance with Cambodian Labor Law and tax requirements.

Yes. A single personal user account in SlidesClock can belong to multiple company workspaces (for example, a part-time worker employed across two different businesses). Each organization maintains completely segregated attendance, schedule, and permission boundaries.

Subscriptions for Standard and Premium plans are billed through Apple In-App Purchase. The prices displayed on your localized Apple App Store storefront are authoritative. Subscriptions renew automatically every month or year unless cancelled in iOS Settings → Apple ID → Subscriptions at least 24 hours prior to the renewal date.

No. Deleting your SlidesClock account or company does not automatically cancel an active Apple App Store subscription. Because billing is managed by Apple, you must cancel your subscription directly in your iOS device settings, or Apple will continue to bill your Apple ID.

Account deletion is performed directly inside the mobile app by navigating to Profile → Settings (gear icon) → Account → Delete Account and typing DELETE. Personal auth credentials, profile information, private avatar files, registered device records, and push tokens are deleted. Employer operational records (attendance timestamps, GPS evidence, approved corrections, leave logs, and payroll runs) are preserved under a detached, inactive member identifier for historical business continuity.

Profile photos (avatars) and payment receipts are stored in private, access-controlled storage. Company logos, however, are public branding files accessible by exact URL to display the organization’s identity on invitations and mobile interfaces.

Notification outbox records that have reached a terminal state (sent or permanently failed) and are older than 30 days are automatically purged daily by scheduled background maintenance tasks. Sensitive data such as salary numbers and private correction notes are excluded from push notification payloads.