Privacy Policy

This policy explains how personal data is handled in Project Workflow Management ("PWM", the "Service"), provided by RestoHQ Technologies ("we"). It applies to the people who use the Service at their workplace, the people whose details their employer records in it (such as customer contacts), and visitors to the sign-in pages.

1. Who is responsible for your data

The Service is used by companies ("Customers") to run their work. When your employer uses PWM, your employer is the controller of the data about you in its company space: it decides what is recorded and why. We act as its processor, handling that data only on its instructions under a Data Processing Agreement. If you have a question or request about your work data, please contact your employer's administrator first; we will help them answer it.

We are the controller only for the limited data we use to run our own business: billing and contract contacts at Customer companies, members of our own platform team, and security logs of the Service as a whole.

2. What we collect

CategoryExamplesWhere it comes from
Account detailsName, work email, role, and optional phone, job title, department, location, short bio and profile pictureYour administrator, or you on your profile page
Sign-in and securityA one-way hash of your password (never the password itself), sign-in times, failed sign-in attempts, the company code you use, and — where our network setup passes it on — the IP address of a failed sign-inYour use of the Service
Attendance and leaveClock-in and clock-out times, hours worked, late or early notes, reasons for reopening a day, extensions, leave periods and leave requestsYou and your managers
Work recordsTasks, projects, phases, checklists, notes and comments, holds and approvals, refusals with reasons, reminders, sticky notes, reportsYou and your colleagues
Files and evidenceDocuments, emails and images attached to tasks, notes, projects and holds; these may themselves contain personal dataUploaded by users or synced from Jira
Customer recordsYour employer's customers' company details, addresses and contact peopleYour colleagues
IntegrationsIf you connect Jira: your Atlassian account id, display name and site, and encrypted access tokens; comments and attachments exchanged with linked ticketsYou, and Atlassian on your instruction
MessagesCopies of the notification emails the Service sends (for example task assignments, holds, attendance notices), and in-app notificationsThe Service
Activity and diagnosticsAn audit log of actions (who did what, when), error reports with the browser type, and performance measurementsThe Service

We do not use advertising or tracking cookies, analytics trackers, or social media plugins. See the Cookie Notice.

3. Why we use it

  • To provide the Service your employer has subscribed to: signing you in, showing your work, sending the notifications your employer has configured, and running scheduled tasks such as reminders and automatic clock-out.
  • To keep the Service secure: preventing unauthorised access, limiting abuse, investigating incidents and keeping an audit trail.
  • To support your employer: when asked, our platform team may open your company's space for a limited time to resolve a problem; each such session is recorded in your company's audit log.
  • To operate and improve the Service: diagnosing errors and measuring performance.
  • To meet legal obligations and to bill Customers.

Where we are the processor, the legal basis is your employer's (for example performance of your employment contract, legal obligations, or legitimate interests). Where we are the controller, we rely on performing our contract with the Customer, our legitimate interest in running a secure service, and legal obligations.

4. Who we share it with

  • Within your company: your colleagues see work information according to the roles and permissions your administrator sets. Some actions (for example task assignments, holds, attendance notices) email the people your company has configured.
  • Service providers (subprocessors) that host and run the Service, listed in the Subprocessor List with their location and purpose.
  • Integrations you or your company choose, such as Jira.
  • Authorities, when we are legally required; we will tell the Customer unless the law forbids it.

We do not sell personal data and do not share it for advertising.

5. Where it is stored

The application and its database run in Singapore. Email is sent through a provider in Japan, and encrypted backups are kept in the Asia-Pacific region. Data may therefore be transferred outside your country; where the law requires, we use appropriate safeguards (such as contractual clauses) for those transfers. Details are in the Subprocessor List.

6. How long we keep it

Your employer controls most retention periods. By default: the audit log and email copies are kept for 2 years, read notifications for 30 days, error reports for 90 days, and completed reminders for 90 days; attached documents are kept until your employer sets a retention period or deletes them. When a Customer leaves, its data is deleted as described in Data Retention and Deletion, and backups age out within 90 days.

7. How we protect it

Encrypted connections, a separate database area for each company, hashed passwords, encrypted stored secrets, role-based permissions, an audit trail and encrypted, signed backups. See the Security Overview.

8. Your rights

Depending on the law that applies to you (for example the Oman Personal Data Protection Law, the Sri Lanka Personal Data Protection Act, or the GDPR), you may have the right to access, correct or delete your personal data, to object to or restrict its use, to receive a copy, and to complain to a data-protection authority. Because your employer controls your work data, send these requests to your employer; if you contact us, we will pass the request to them and help them respond. For data we control, contact [email protected].

9. Children

The Service is for business use and is not directed at children.

10. Changes and contact

We will post changes to this policy and, for material changes, notify Customer administrators in advance. Questions about this policy or about data we control: [email protected], or write to RestoHQ Technologies, Colombo, Sri Lanka.