Effective date: 10 October 2026 Last updated: 15 October 2026
Publisher: Laissaoui Mohammed Lotfi Country: Algeria Privacy contact: contact@raystate.com
1. About this policy
Staffly is a workplace application for managing employee profiles, attendance, schedules, leave and gross payroll on a shared business phone or tablet. This policy explains how the Android application handles personal information, including local workplace records, optional advertising, subscriptions, and support communications.
In this policy, “we,” “us,” and “our” refer to Laissaoui Mohammed Lotfi, the publisher of Staffly. “Business administrator” means the person or organization managing the workplace device and its employee records.
Core HR records are stored locally. Advertising and subscription services use internet connections and process separate service-related information. Staffly does not provide HR cloud synchronization or require a remote HR account.
Optional nearby employee access
Where enabled by the business, Staffly can enroll an employee's personal phone through an administrator-issued invitation and a connection code compared on both devices. The business device sends only that employee's permitted attendance, breaks, schedule, leave/balances, identity labels, optional small profile-photo thumbnail and QR badge to an encrypted cache on the enrolled phone. Payroll amounts, internal notes, contact details and other employees' records are excluded. The employee can read the last downloaded snapshot offline and save readable badge or attendance exports. This is nearby device-to-device transfer, not HR cloud storage or remote synchronization at home.
Bluetooth, Wi-Fi and camera permissions support discovery, direct transfer and QR scanning. On older Android versions and on iOS hotspot connections, the operating system may also require location-related permission; Staffly does not request location updates or implement employee location tracking. Android Nearby uses Google Play services, whose connection performance diagnostics and device information may be processed under Google's usage and diagnostics settings; see Google Nearby data collection. Employee mode does not initialize Staffly's advertising or subscription services.
The administrator controls enrollment and revocation. Revocation prevents future downloads but cannot erase snapshots or exported files already on an offline phone. Employees can disconnect to remove their local employee cache; separately exported copies must be deleted separately. Restoring a workplace backup requires fresh employee enrollment and badge issuance. A static QR badge can be copied; it is a checkpoint identifier and does not authorize downloading personal records. Businesses must explain personal-device access, permitted use and retention to employees before enabling this optional feature.
2. Responsibility for workplace information
The business using Staffly determines why employee information is entered, who may access it, and how long workplace records should be kept. Where applicable data protection law uses this terminology, that business is the controller of those workplace records. It must provide appropriate employee notices, establish a lawful basis, and follow employment and record-retention requirements that apply to it.
We provide the application and are responsible for the publisher-side processing described here, including subscription administration and communications sent to us. We do not receive or remotely administer your locally stored employee database through Staffly's normal operation.
Employees seeking access, corrections, or deletion of their workplace records should contact their employer or business administrator first. We cannot retrieve or remotely delete records that remain solely on their workplace device.
3. Information handled by Staffly
Workplace records stored on the device
Depending on what an administrator enters, Staffly handles:
- Business name, language, currency, timezone, and checkpoint preferences.
- Employee names, employee numbers, contact details, departments, job titles,
employment dates, notes, profile photographs, and active or archived status.
- NFC and QR credential identifiers, assignments, replacements, revocations, and history.
- Gross payroll rates, calculated earnings, adjustments, finalized wage records and recorded payments.
- Clock-in and clock-out records, timestamps, checkpoint methods, recorded timezone,
corrections, reasons, and related audit history.
Leave records may include requested dates, paid/unpaid categories, full/half-day units, approval/rejection/cancellation reasons, manual allocations and adjustment history. These workplace records stay in the encrypted local HR database and administrator-created backups; leave reports may be exported on request. Avoid entering medical diagnoses or unnecessary sensitive details in free-text reasons.
Work schedule records may include weekly hours, employee assignments, dated exceptions, revision history and administrative reasons. Attendance insights are calculated locally from these records. They remain in the encrypted local HR database and administrator-created backups; schedule reports may be exported.
These records support employee organization, credential recognition, attendance review, corrections, and administrator-requested backup and restoration. Optional profile fields should contain only information needed for workplace administration.
Authentication and recovery information
When you choose device authentication, Android checks the supported biometric or device credential. Staffly receives an authentication result; it does not receive fingerprint templates, your device PIN, or your device unlock pattern.
If you configure a Staffly PIN, the app stores salted verification values and retry-control information in platform-protected storage. Recovery-code verification information and device-held encryption keys are also stored locally. Do not send your PIN, recovery code, encryption keys, or backup passwords to support.
Information from network services
Advertising and subscription providers handle the technical and transaction information explained in sections 5 and 6. This information is separate from employee identities and attendance records.
Support communications
If you contact us, we receive your email address and any information or attachments you choose to send. We use them to respond, troubleshoot, and handle privacy requests. Avoid sending identifiable employee records, photos, card identifiers, or unredacted backups. If a screenshot is needed, remove unnecessary personal data.
4. Photos, NFC, and the shared checkpoint
Staffly launches the device camera when an administrator requests a profile photo. Accepted photos are processed locally; the saved profile copy is resized and stripped of source metadata, including embedded location information. The operating system or camera application may create temporary files before processing. Staffly attempts to remove its temporary captures after handling them, but interruption or operating-system behavior can affect cleanup. Copies created separately by a camera application are subject to that application's settings.
Staffly reads a supported NFC card's identifier for employee credential enrollment and attendance recognition. It does not use this workflow to read the contents of a national identity document or extract its printed government identification number. A card identifier is not proof of who is holding the card. Staffly does not perform employee facial recognition or generate facial matching templates.
The shared checkpoint briefly displays a recognized employee's name, checkpoint result, and profile photo where available. People near the device may see this confirmation. The app clears the feedback after approximately five seconds and when backgrounded. Businesses should position the device appropriately and explain this checkpoint display to employees.
5. Advertising and privacy choices
The free application may display Google AdMob banners and native ads on selected administrator screens, interstitial ads at designated administrator workflow breaks, and App Open ads during eligible startup or foreground-return transitions when those formats are enabled. Checkpoint scans, authentication, and backup operations do not trigger ads. Staffly Pro removes all Staffly ad placements.
Google's advertising services may receive IP addresses, approximate location inferred from IP, advertising or app/device identifiers, app/ad interaction events, and performance information. These services use this information for ad delivery, measurement, diagnostics, and fraud prevention. Available identifiers and ad personalization depend on device settings, regional requirements, and your choices.
We do not supply employee names, contact details, photos, NFC identifiers, or attendance records for advertising or ad targeting. We do not sell local HR records.
Staffly uses Google's User Messaging Platform to obtain advertising privacy choices where required and requests ads only when that platform permits them. Where required, a privacy-options entry is available in the Staffly Pro administrator area. You can also use Android's advertising-ID and privacy controls. Withdrawing consent applies to future processing that depends on that consent; it does not invalidate processing already lawfully completed. Refusing advertising consent does not disable core staff management, attendance, or backups.
Learn more: Google Privacy Policy and Google advertising information.
6. Subscriptions and purchases
Optional Staffly Pro subscriptions are processed through Google Play Billing and managed with RevenueCat. Purchase tokens, product and subscription information, transaction history, entitlement status, app-user identifiers, and relevant app or device information are processed to validate access, handle renewals, prevent purchase misuse, and restore eligible subscriptions.
Staffly uses a RevenueCat-generated subscription identifier rather than employee identities. We do not configure employee contact attributes or HR records in RevenueCat. Its subscription records may be accessible to us through the publisher's RevenueCat dashboard for subscription administration and support.
Google Play handles payment credentials. Staffly does not receive your full payment card number or card security code. Restoring a subscription requires the appropriate store account and internet access; it does not restore employee records.
Subscription status may be cached locally for bounded offline use. This cache is separate from HR backups. Uninstalling Staffly or clearing its data does not cancel a subscription. Manage or cancel subscriptions through Google Play.
Learn more: RevenueCat privacy information and Google Play subscription management.
7. Disclosure, service providers, and international processing
Local HR records are not automatically uploaded to us, AdMob, or RevenueCat. They can leave the device when an administrator exports a backup, uses a selected file or cloud-storage provider, or voluntarily sends information to someone else. Those recipients' practices govern their handling of the information.
Google provides advertising, consent, and store-payment services. RevenueCat provides subscription infrastructure and processes end-user subscription information on our behalf under its service arrangements. These providers may process service information in countries outside Algeria or your country of residence. Applicable agreements and legal requirements govern those transfers and safeguards; contact us for information about arrangements relevant to your request.
We may disclose information we actually hold when required by applicable law or a valid legal process, or as necessary to protect against fraud, security incidents, or abuse. This does not give us access to a locally stored employee database. Any material change in publisher or data handling will be addressed through appropriate notice and applicable legal requirements.
8. Purposes and legal bases
Where a law requires us to identify a legal basis, publisher-side processing may rely on performing the subscription or support service you request; consent for advertising-related processing where required; applicable legal obligations; or legitimate interests in securing services, preventing fraud, and responding to inquiries, subject to your rights and applicable law.
The business administrator is separately responsible for the legal basis for employee records and workplace attendance monitoring. Installing Staffly or agreeing to this policy does not replace an employer's required employee notices or establish consent for all workplace processing.
9. Storage, security, and backups
Staffly encrypts persisted HR records and saved profile attachments in its private application storage. Device-held keys and administrator verification information use platform-protected storage. Administrator screens lock on backgrounding, explicit locking, and inactivity. Processing in device memory and camera temporary files may occur before encrypted persistence.
These controls reduce risk but cannot guarantee protection against a compromised operating system, unauthorized device access, shared administrator credentials, or someone observing an unlocked screen. Use a strong device lock and restrict who knows or can use administrator authentication.
Administrator-requested HR backups are encrypted and protected by a user-held backup password. Exported copies are outside the app's private storage and may be retained by a chosen device, storage service, or recipient. Protect those copies and their passwords separately. We cannot recover lost device keys or backup passwords.
Generated Excel, CSV, and PDF reports are stored in an encrypted, device-local Documents library. They are excluded from HR backups and cleared when a backup is restored. Opening a report in another app or saving a copy provides a readable, unencrypted document to that app or chosen destination. Temporary viewing copies are removed on return to Staffly or at its next startup. External copies remain under the chosen app, storage provider, or recipient's control. Deleting a document inside Staffly removes only its library copy.
Imported HR backups do not transfer administrator authentication or establish subscription authority. A device change requires both appropriate local data restoration and, where applicable, separate subscription restoration.
Staffly keeps the current and previous encrypted database snapshots for local recovery. A previous snapshot can retain recently changed or removed data, including a replaced profile photo, until another successful save retires it. Interrupted or damaged snapshots may be retained to avoid destructive recovery. Recovering a previous snapshot requires administrator authentication and confirmation; recent changes may be missing.
10. Retention and deletion
Local workplace records: Records remain under the business administrator's control. Archiving an employee retains their profile and historical attendance; archiving is not deletion. Corrections and credential revocations may retain audit history. Administrators must establish an appropriate retention schedule.
Deleting the local installation's data: An authorized device owner can clear Staffly's app storage in Android Settings or uninstall Staffly to remove its local application data and device-held keys. Export any records you lawfully need to retain first. Separately exported backups, camera-app copies, recipient copies, and provider-held information must be managed separately. Restoring an older backup can reintroduce records it contains.
Subscription and service records: Provider records may be retained for service operation, transaction history, fraud prevention, or legal obligations. Removing local HR data does not automatically erase Google Play or RevenueCat records. Contact us about publisher-managed subscription information; Google account and payment-related requests may also need to be directed to Google.
Support records: We retain support communications while needed to address the request and relevant follow-up, disputes, security matters, or legal obligations. They are not kept for an indefinite unrelated purpose. Contact us to request deletion of support information, subject to applicable retention requirements.
Staffly does not create an online HR account whose deletion would remove records from an employer's device.
11. Your privacy rights and requests
Depending on the law that applies, you may have rights to access information, correct inaccuracies, request deletion, restrict or object to processing, obtain portable information, withdraw consent, and complain to a competent data protection authority. Rights and exceptions vary by jurisdiction and type of information.
For employee records, contact your employer or business administrator. For publisher-held subscription or support information, email contact@raystate.com, identify Staffly, and describe your request. We may request proportionate information to verify your identity or authority and will respond within applicable legal time limits. We do not require payment details, employee databases, or secret credentials to submit a request.
RevenueCat requests concerning information processed on our behalf should be addressed to us. Requests concerning Google's independently managed information may also require Google's privacy or account controls.
12. Children
Staffly is designed for business administrators and workplace attendance. It is not directed to children, and we do not knowingly solicit children's personal information through publisher communications. Businesses must follow applicable employment, child-protection, and privacy requirements for any employee information they enter, including records relating to younger workers where lawful.
13. Changes and contact
We may update this policy to reflect application changes, provider practices, or legal requirements. The revised policy will show an updated date. Material changes will be communicated through appropriate available channels, and additional consent will be requested where legally required.
For privacy inquiries or requests, contact:
Laissaoui Mohammed Lotfi Algeria contact@raystate.com
14. This showcase website
This website provides product information and legal documents. It does not receive your Staffly employee database, offer an HR account, or process subscription checkout. Its images, fonts and scripts are served with the website; we do not embed website advertising, analytics or tracking scripts. An optional local browser preference remembers your selected language. You can remove it through browser storage settings; blocking storage does not prevent viewing the website.
The site is prepared for hosting on GitHub Pages. GitHub may process connection information such as IP addresses and technical request information to operate and secure its hosting service under the GitHub Privacy Statement. We do not claim that hosting creates no server logs, and we do not set a retention period for GitHub's independently handled information. If hosting changes, this section must be updated to describe the actual provider.
Following a Google Play link opens Google's service; emailing support uses your chosen email provider. Their own terms and privacy practices apply. The website does not contain a contact form or send messages automatically.