Sarluma
  • Features
  • Security
  • API
  • Terms
  • Privacy
Sign in

Privacy policy

Draft for legal review. Text in [brackets] must be completed before this policy is published to customers. Last updated: [date].

1. Who is responsible

When an organisation uses Sarluma to review its staff, that organisation decides what is collected and why. It is the controller of that data and we, [Company legal name], process it on its behalf. Employees with questions about their own evaluation should first contact their employer.

2. What we hold

DataExamplesWhy
Employee recordsName, employee code, job title, departmentTo assign and show evaluations
EvaluationsScores per question, written comments, who evaluated whom, datesTo calculate results and reports
Management accountsName, work email, roleTo sign in and to apply permissions
Sign-in secretsPasswords and PINs, stored only as hashes; two-step verification secret, stored encryptedTo protect accounts
Security recordsAudit log of actions, IP address of sign-ins and changesTo detect misuse and to give the customer a record
Subscription detailsCompany name, plan, datesTo manage the account

We do not ask for, and customers should not enter, health information, identity numbers or other special categories of data.

3. What we do not do

  • We do not sell personal data or use it for advertising.
  • The service sets one cookie, which keeps you signed in. There are no analytics or tracking cookies and no third-party scripts.
  • We do not use customers' evaluation data to train AI models.

4. Who can see the data

Inside a customer's organisation, access follows the role each person was given: evaluators see only their own assignments; department managers see averages of their department; HR and administrators see full results. Our own staff see a customer's data only in a time-limited support session that is recorded in that customer's audit log.

5. Service providers

ProviderPurposeLocation
Cloudflare, Inc.Hosting, database, network protectionGlobal network; database region: [region]
Resend ([if enabled])Sending password-reset codes by email[region]

6. How long we keep it

  • Customer data is kept while the account is active.
  • After an account is closed, the customer has [30] days to export; we then delete the data within [60] days, and it leaves backups within a further [30] days.
  • Sessions and sign-in attempt counters are deleted automatically within days.

7. Security

The measures we take are described on the security page.

8. Your rights

Depending on where you live, you may have the right to see, correct, export or delete personal data about you, or to object to its use. Employees should send such requests to their employer, who can carry them out in the service; we help the customer respond. Account administrators can write to us directly.

9. International transfers

[Describe where data is stored and the legal basis for any transfer out of the customer's country.]

10. Changes

We will post changes here and tell account administrators before a material change takes effect.

11. Contact

[Privacy contact email] · [Company legal name], [address]