Privacy Policy
What personal data SISC Suite holds, where it lives, how long it stays, and what happens when somebody asks to be erased. This describes what the software actually does — the sections below are written from the erasure map the product runs on, not from a template.
In effect since 1 November 2026 · Last updated: 12 November 2026
1. Two roles, and which one applies
There are two different relationships in this product and they are governed differently.
For your own account with us — the person who signs up, the people invited into a workspace, what we bill — we decide why the data is held, so we are the controller.
For everything your company puts into its workspace — your guests, your employees, your customers, your contacts — your company decides why it is held, and we hold it on your instructions. There we are the processor and you are the controller. That distinction matters when one of your customers asks you to erase them: the request is yours to answer, and the product gives you the means to answer it.
2. Who we are
SISC Suite is provided by SISC Group, registered in Palestine, at registered address. Privacy questions and requests go to [email protected]. SISC Group itself can be reached at [email protected]. Data protection officer: whether one is appointed, and who.
3. What we hold about you as a user of the product
For each person with a sign-in, the product stores:
- Name and display name, email address, and optionally a phone number, job title, department, time zone and profile picture.
- A password, stored only as an Argon2id hash — we cannot read it and cannot tell you what it is.
- If you turn on two-factor authentication, the secret that makes it work and your recovery codes.
- A sign-in log: when a sign-in was attempted, whether it succeeded, the address it came from and the browser it came from. This is a security measure and it is one of the few things that will show us an account is being attacked.
- What you did, in an audit log — who changed what, and when.
4. What your company puts into its workspace
The product holds records about people your business deals with. Which of these exist depends on the apps you use:
- Hotel guests: name, contact details, nationality, date of birth, identity document type, number, issuing country and expiry, a photograph of that document where one is captured, stay preferences, and free-text notes staff have written.
- Employees, in the hotel and in HR: name, employer-issued number and work address, and payroll records.
- Customers and CRM contacts: name, contact details, addresses and the documents raised against them.
- Renters, travellers and address-book contacts, each with the name and contact details the app needs. A traveller’s name is stored exactly as it appears in their travel document, because ticketing will not accept anything else.
5. Where it is kept, and how it is protected
Each customer gets a database of their own. Which database a request reaches is decided by the address you signed in on, not by a column naming who owns each row — the most common way one customer sees another’s data is a query that forgot to filter, and there is no such query to forget here.
Identity document numbers are encrypted with AES-256-GCM before they are stored. A photograph of an identity document is sealed on disk and is never served from the same origin as the application.
Passwords are hashed with Argon2id. Access tokens live in the browser’s memory only and are never written to a cookie or to storage. The refresh token is stored on the workspace’s own origin, which no other workspace and no other subdomain can read.
The service is hosted at the hosting provider and the countries data is stored in.
6. Why we hold it
To provide the service you asked for, to bill for it, to keep it secure, and to meet obligations the law puts on us and on you — accounting records in particular, which several countries require to be kept for years and make an offence to destroy.
The formal mapping of each purpose to a lawful basis is the lawful-basis table, to be confirmed with counsel.
We do not make automated decisions that produce legal effects about anybody. The product suggests and refuses; it does not decide.
7. Who else sees it
This website sets no cookies and loads nothing from anyone else: no fonts from a content network, no advertising, no analytics service and no tag manager. Its few scripts all come from this domain. One remembers, in your browser, the language you choose. One counts each page view, anonymously, by country and page, with no cookie and nothing stored in your browser. The others show prices, the newsletter and contact forms, and the Ask SISC assistant. Our Cookies page lists everything that can be stored in your browser. View the source and count the hosts.
The service itself uses the list of sub-processors — hosting, mail delivery, payments — and what each one receives. We will tell you before that list changes.
Where the product sends mail on your behalf, it sends it through the mail settings your company configured.
If personal data has to move between countries, the mechanism relied on is the international transfer mechanism.
8. How long it stays
While your subscription is live, your data stays until you delete it.
If you cancel, you keep full read and export access for 90 days, and your database is deleted 365 days after cancellation. We warn you 30 days, 7 days and 1 day before deletion.
Data of an account suspended for non-payment is deleted 90 days after suspension, after three warnings.
Records the law requires to be kept are kept for as long as the law requires, which is longer than the two windows above. Those periods are the statutory retention periods that apply per country.
9. Your rights
You can ask for a copy of the personal data held about you, ask for it to be corrected, ask for it to be erased, object to how it is used, and complain to a regulator.
A full export of a workspace is a feature of the product, in JSON, CSV or SQL. Authentication secrets are never included in one: an export that carried password hashes and two-factor seeds would hand whoever ended up with the file the ability to impersonate every person in the company.
If your company holds your data in its workspace, send the request to that company. If it is about your account with us, send it to us at the address in section 2.
Complaints can be made to the supervisory authority a complaint may be made to.
10. What erasure actually does
Erasure in this product is not "delete every row that mentions the person", and a policy that promised that would be promising something no accounting system can do. Every column of every record a person touches is assigned, deliberately, to one of three outcomes:
- Cleared — personal data with no independent reason to keep it. It is overwritten in place, not marked deleted. A row flagged as deleted still has the name sitting in the column, readable by the next backup and by anyone with database access, which is not an erasure.
- Pseudonymised — personal data sitting on a record that has to be kept. A hotel folio is an accounting record; it keeps a payer, and the payer becomes a reference that identifies the erasure rather than the person.
- Retained — amounts, dates, currencies, transaction codes, tax withheld, filing references, and the internal identifiers that hold the retained records together. Also the audit log, which is the record that the erasure itself happened and has to survive to prove it.
11. Files are erased too, and first
A photograph of a passport is not a column. Clearing the row that points at it would leave the image on disk — still readable, and now impossible to find from the record that used to name it, which would make the erasure the very thing that made the leak permanent.
So the bytes are destroyed before the pointers are cleared, and the erasure report says which files were found and destroyed.
12. WhatsApp and other messaging channels
A company can connect its own WhatsApp Business number to its workspace. The number and its Meta account belong to the company. For the chats, the company is the controller and we are the processor, as section 1 explains.
When a company connects a number, SISC receives from Meta the number’s identifiers at Meta, the number as it is shown, the verified business name and an access token. For each message, SISC receives the sender’s phone number and WhatsApp profile name; the text, picture, document, voice note, video or location; Meta’s message number and time; and whether the message was delivered and read. If the company connects the number of its WhatsApp Business app and agrees to it in Meta’s steps, SISC also receives the app’s contacts, up to 180 days of earlier one-to-one chats, and copies of messages sent from the phone.
All of it is stored in the company’s own database. The access token, the app secret and the number’s registration PIN are encrypted with AES-256-GCM and are never shown again. Pictures, documents and voice notes are checked for safety and stored encrypted on disk; a file that fails the check is not kept. The text of messages is not encrypted inside the database: it is protected by each company having a database of its own, and by the permissions below.
Chats can be read only by the company’s own staff who hold the permission “WhatsApp: View”. The company can limit a number to chosen people and groups. No screen in SISC’s own operator tools shows WhatsApp messages. SISC support staff can enter a company’s account in a support session, which the company can see and end.
The company sets how long chats are kept, with “Keep message text and files for (days)”: 365 days unless it is changed, from 7 to 3,650. After that, the words, phone numbers and files are deleted; a record that a message was sent, and when, stays.
When a company disconnects a number, the access token and the app secret are deleted at once, and SISC asks Meta to remove its app from the company’s WhatsApp account. The chats already received stay until the retention period ends, until the person is erased, or until the company’s database is deleted. Our page “How to delete your data” gives the steps.
A customer who writes the single word STOP withdraws their consent. SISC then refuses to send them that company’s templates and automatic updates until the company records a new consent.
SISC Suite does not use WhatsApp messages for advertising. Nothing in the product passes their content to an advertising or analytics service, or uses it to build marketing lists.
The SISC AI Assistant uses chat text in two cases, and only for a company that has the AI add-on. First, “Suggest a reply with AI”: when a staff member presses it, the recent conversation is sent to our AI service provider and a draft appears in the reply box; nothing reaches the customer until the person presses Send. Second, the setting “Let AI read messages to suggest follow-ups”: while it is on, new incoming WhatsApp messages are read in the background, in small batches, to find promises and dates, and the staff member responsible for the chat is asked whether to set a follow-up. It is off for a new company until the company switches it on (a company that had it before keeps its setting), the company can switch it off, and it never sends anything to the customer. Our AI service provider is one of the sub-processors listed in section 7.
Mail the product sends for a company goes through that company’s own mail settings, as section 7 says.
13. How SISC uses Google data
A person can connect their own Google account to SISC Suite under My account → Cloud accounts. They tick the parts they want, and SISC asks Google only for those parts, as that person — never for the whole company. Google’s own screen lists each permission, and a part whose permission is unticked there is not connected. Every sign-in also asks for “openid” and “email”, which tell SISC only which Google account signed in. The parts, and the permission (scope) each one asks for:
- Gmail (https://mail.google.com/): to read, send and organise the person’s Gmail in SISC Mail. Google offers no narrower permission for this.
- Google Calendar (calendar.events, calendar.calendarlist.readonly): to list the person’s calendars and keep a SISC calendar they choose in step with a Google calendar, in both directions.
- Google Contacts (contacts.readonly): to copy the person’s Google contacts into their own private contacts in SISC, when they press Import. Nothing is written to Google.
- Google Drive (drive.readonly): to browse the person’s Drive and attach a file to a message they are writing in SISC Mail. Nothing is saved back to Drive, and SISC does not store the file apart from the message it is attached to.
- Google Meet (calendar.events): when the person presses “Add Google Meet link”, SISC creates an event in their own Google Calendar, because that is how Google makes a Meet link. The event stays in their calendar; SISC keeps only the link.
14. Google data: what is kept and deleted, the AI, and who sees it
What SISC keeps. The keys Google issues for a connection are stored encrypted with AES-256-GCM in the company’s own database, sealed to that person’s connection. To show the mail list quickly, SISC keeps for each Gmail message its sender, recipients, subject, date, flags and the first 200 characters of its text; the full message and its attachments are read from Google when the person opens them and are not stored. Calendar events synced into a SISC calendar become entries of that calendar, and imported contacts become the person’s own contacts in SISC.
Disconnecting. Under My account → Cloud accounts a person can disconnect one part or all of them, at any time, and SISC stops using a disconnected part at once. When Gmail is disconnected, SISC deletes at once the mailbox connection and its keys, the copy of the mail list described above, the folder list and SISC AI Assistant’s sorting marks for that mailbox. For that mailbox only, it also deletes its list of snoozed messages (the messages themselves stay in the mailbox’s Snoozed folder), the messages waiting to be sent later — which are then never sent — the rules and the marks they and the person made, the answers to invitations and the favourite folders. Removing a Gmail mailbox in SISC Mail’s own settings also stops the Cloud accounts connection from using Gmail, and deletes that connection and its keys when Gmail was its only part. When Calendar is disconnected, SISC deletes the keys of the calendar connection. When everything is disconnected under Cloud accounts, SISC first asks Google to withdraw SISC Suite’s access to the account, then deletes the connection and every key it held for it — even if Google cannot be reached at that moment — and can no longer reach the Google account.
These stay after disconnecting, because they are the person’s own records in SISC: entries already synced into a SISC calendar, contacts already imported, messages the person filed to a contact, deal, project or invoice (their subject, sender and date — kept as the company’s record of that work, never the message itself), and backups of the company’s database taken before. Unless everything was disconnected and Google accepted SISC’s request to withdraw access, Google keeps listing SISC Suite among the apps with access to the account until the person removes it at https://myaccount.google.com/permissions; SISC cannot use that access once its keys are deleted.
SISC AI Assistant. Google data reaches our AI service provider in two cases only, and only for a company that has the AI add-on and has turned the language model on in its AI settings. First, when a person presses an AI button on a message — summarise, translate, reply or improve — the subject and the text of that one message (up to 12,000 characters) and any instruction they typed are sent for that one answer; SISC stores neither the text nor the answer. Second, when a person switches on AI sorting for their own mailbox in SISC Mail, and while the company’s setting “Let AI read messages to suggest follow-ups” is on, new messages are read in small batches — for each, the sender’s or recipients’ addresses, the subject and the first 600 characters of the text. SISC keeps only the result (important or not, needs a reply or not, and a reason code) and deletes it when sorting is switched off or the mailbox is disconnected. Each person decides for their own mailbox, and the company can turn the setting or the language model off for everyone.
When asked, the SISC AI Assistant panel can also list the newest messages in a person’s inbox. That list is built in the person’s browser and is not sent to the AI service provider; it stays in their own conversation history, which is deleted 30 days after its last message.
SISC does not use information received from Google to develop, improve or train artificial-intelligence or machine-learning models.
Who can see it. Inside the company, only the person who connected their Google account can open its mail, its Drive files and the connection itself; calendar entries synced into a SISC calendar are seen by whoever that calendar is shared with. No screen in SISC’s own operator tools shows a company’s mail, calendar, contacts or Drive files, and a SISC support session — which the company must allow and can end — cannot open anybody’s Google connection or mailbox. SISC staff can see some of this data in three cases only: a copy of the company’s database, which a named SISC administrator can make to restore the service and whose making and download are both recorded, and which never holds the copy of the mail list or the folder list — every copy leaves them out, and they are rebuilt from the mailbox after a restore; an export made to answer a request under data-protection law; and the File safety log, which keeps the name of a Drive file only when the file is refused as unsafe.
We do not sell information received from Google and do not use it for advertising of any kind. Apart from the sub-processors in section 7 that run the service, it goes to nobody, except where the person sends it themselves — a message or an attachment — or where the law requires it.
The use of information received from Google Workspace scopes will adhere to the Google User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.
15. Changes to this policy
We will tell you before this policy changes in a way that affects you, and the date at the top of this page changes with it.