Privacy policy

1. About this policy

Strimlyne is a workspace for managing companies, staff, attendance, shifts and leave. This policy explains the information involved when you visit the website, create an account or use a company workspace.

Your organisation decides how it uses Strimlyne for workplace administration, including which staff to add, who can view records and how attendance is reviewed. Its own employment and privacy notices also matter. Ask your company owner or supervisor how those arrangements apply to you.

2. Information in your account

The information handled depends on the features you use:

• Account details: your name, phone number, password in a hashed form, and account security information such as two-factor authentication settings.
• Workplace details: company membership, role, job title, department and shift assignments supplied by you or an authorised manager.
• Attendance records: attendance dates, check-in and check-out times, attendance status and related schedule information. Records can include a snapshot of staff details when the attendance was recorded.
• Leave information: dates, request details, reasons you provide and the decision recorded by an authorised reviewer. Avoid including unnecessary sensitive information in free-text fields.
• Subscription records: the selected company plan, payment status, transaction references and payment-provider details associated with a purchase.
• Technical information: session information and operational logs used to handle requests, investigate errors and protect account access. Error logs can include information associated with the affected request.

Some information comes directly from you. Other information comes from your organisation, from actions taken within the workspace, or from a connected provider confirming a transaction or verification request.

3. How information is used

Strimlyne uses this information to provide account access, organise company workspaces, record attendance, manage shifts and leave, and produce the reports available to authorised users.

Phone numbers also support account identification and password recovery. Payment records help associate payments with the correct company and subscription. Technical information supports troubleshooting and account security.

Attendance summaries are tools for your organisation to review. Questions about a late mark, an absence, a shift or a workplace decision should be raised with your supervisor or company owner so that the underlying record can be checked.

4. Location and device permissions

When you use a check-in or check-out feature that requests location, your browser asks for permission. The record can include latitude, longitude and the accuracy reported by your device. This helps provide context for the attendance event.

The attendance pages request a location reading when you take the relevant action; they are not designed as continuous background location tracking. Read your organisation's attendance requirements before using these features.

You can manage location permissions in your browser or device settings. Refusing permission can prevent a location-dependent attendance action from completing. Location readings can be affected by your device, signal and surroundings; tell your supervisor if a reading appears incorrect.

5. Who can receive information

Your organisation: access to staff and attendance information depends on workspace membership, roles and permissions. Company owners and authorised supervisors may review records within their permitted scope. Treat downloaded reports as workplace records and share them carefully.

Verification providers: the password-recovery process sends your phone number to Hawksend to deliver a verification code through WhatsApp. Verification requests also involve the code you enter. Those providers handle the information needed to deliver and verify the message.

Payment providers: when you use paid subscriptions, TenkiPay receives checkout information such as the amount, plan description and company reference. It returns transaction information used to record the payment. Payment information you enter on the provider's page is handled under that provider's own terms and privacy notice.

Website infrastructure: the website relies on hosting and delivery services. Pages that load Google Fonts make requests to Google for those files, which expose standard connection information such as an IP address and browser request details.

These external services may operate in a different country from you. Review their notices when using them. This policy describes Strimlyne's use of the integrations; it does not replace the providers' own notices.

6. Cookies and local storage

The application uses session and security mechanisms to keep requests associated with your account and protect form submissions. Choosing "Remember me" can keep your sign-in recognised between visits.

The installable web app also caches assets such as images, styles, fonts and an offline page on your device. This helps the interface load and provides a fallback when a connection is unavailable; it does not guarantee that attendance actions can be completed offline.

You can clear cookies and site data through your browser. Doing so may sign you out, remove saved preferences or require assets to download again. On a shared device, sign out when you finish.

7. Security and your responsibilities

Passwords are stored using hashing rather than as readable passwords. The application provides role-based access and supports two-factor authentication. These measures help protect access, but no online system can guarantee that every incident will be prevented.

Use a strong, unique password. Keep verification codes and recovery codes private, protect the phone associated with your account, and avoid sharing your login. If you suspect misuse, change your password where possible and notify the person who manages your workspace.

8. Keeping and deleting records

Different records serve different purposes. Account information supports access; attendance and leave records support workplace administration; subscription records support payment reconciliation; technical logs support troubleshooting and security.

Leaving a company, losing workspace access and deleting a personal account are different actions. Do not assume that one action removes every historical workplace record, exported report or record held by a connected provider. Attendance records may include details saved at the time of the event.

Ask your organisation which retention schedule applies to its staff records and which records it needs to keep. Before deleting an account or company, review the confirmation shown in the application and arrange any authorised records your organisation needs. No fixed deletion period is specified here.

9. Reviewing information and raising concerns

Review the information available in your profile and workspace. Use the available profile controls to correct your own details, or ask an authorised manager to review workplace records you cannot edit.

For access, correction, deletion or other privacy requests concerning employment records, start with your company owner or supervisor. Explain which information is involved and what you want reviewed. Identity or authority may need to be checked before information is released or changed.

Depending on the law that applies, you may have additional rights concerning your information, including the ability to raise a concern with a relevant authority. This policy does not remove those rights. Do not send passwords, verification codes or recovery codes with a request.

10. Updates and related information

This policy may be updated as the service and its integrations change. The date at the top identifies the current text. Revisit it when you begin using a new feature or have questions about how information is handled.

The Terms of Service explain account use and workspace responsibilities. Your organisation can provide its own workplace privacy notice and the appropriate contact for questions about its records.