Sijilak

Privacy Policy

Last updated: October 4, 2026

1. Who we are and what this policy covers

This policy explains what data the Sijilak service that we provide ("we", "us") processes, why we process it, who we share it with, how long we keep it, and your rights over it. It is part of the Terms of Service and should be read with them.

Sijilak is a service for businesses. It covers managing orders, customers, inventory, conversations and tickets, and the accounting module (ERP) with its ledgers, invoices, purchasing, tax returns and payroll.

2. Our role and yours in processing data

  • Account and subscription data (the names and email addresses of the owner and users, the owner's phone number, and subscription and payment details): we are the "controller" of this data, and we process it to provide the service, bill you for it and contact you about it.
  • Customer Data (everything the Customer or its Users enter or sync about its customers, employees and suppliers): the Customer is the "controller" and we are the "processor", within the meaning of the Personal Data Protection Law No. 151 of 2020, as in section 4 of the Terms. We process it only to run the service for the Customer and according to its instructions.
  • If one of the Customer's customers or employees asks to access, correct or delete their data, the Customer receives and decides on that request, and we help the Customer carry it out.

3. The data we collect

  • Account data: each user's name, email address and password (the password is stored hashed, never as text), the business name, currency and language, the owner's phone number if entered, and the point-of-sale personal PIN (also stored hashed).
  • The Customer's business data: orders, customers, products, inventory, conversations, tickets and expenses, and in the accounting module: journal entries, invoices, purchasing, tax returns, payroll, employee records and bank details, and attached files such as supplier invoice images and employee documents. Product images and the business logo are stored at public links so they can be shown in the store and on printouts.
  • Payment data: card payments are made directly on Lemon Squeezy's checkout page. Lemon Squeezy sends us a notification for each payment or subscription change, which may include the buyer's name and email address, the card brand and its last four digits; of it we store only the plan, amount, currency, order or invoice number, and the subscription number, status and dates. The full card number never reaches us and we do not store it. For manual payments (InstaPay or a mobile wallet) we record the amount, its date and the payment method.
  • Error logs: when an error happens on a screen we record its message, the page, the browser type and the user's email address so we can fix it, and we keep these logs for 90 days before they are deleted automatically. The error is also sent to Sentry (section 5).
  • Visit statistics and cookies: we use Google Analytics on the website pages and the orders app pages, and not in the accounting module (ERP). Google Analytics sets its own cookies and receives the page address, device and browser type, and approximate location; it does not receive what you type on the screens. The app itself keeps your sign-in session, language preference and some temporary settings in your browser's storage, and sets a cookie only for 10 minutes while a Shopify store is being connected.
  • Contact requests: the "request a demo" form on the home page sends your name, business name, phone, email and message to our mailbox through the FormSubmit service, and we keep it so we can reply to you.
  • Technical data: to prevent abuse, we record the IP address, the request time and the name of the service requested for every request that reaches our public endpoints: programmatic (API) connections, notifications from stores, channels and shipping carriers, public forms such as "request a demo" and feedback, the artificial intelligence features, sending to channels, and account-connection steps. Records older than one hour are deleted when the next request reaches any of these endpoints. Our hosting providers may also log technical request data, such as the IP address and request time, under their own policies.

4. Why we use the data

  • Running the service the Customer asks for: managing orders, inventory, conversations, accounts and reports, and carrying out the connections and sending it requests.
  • Billing and collecting the subscription, and telling you when a payment fails or is late, when the subscription ends, and when the data is due to be deleted.
  • Service messages: password resets, in-app announcements, and notices of planned maintenance and of changes to the Terms and prices.
  • Introductory messages about the service for new account owners, each with a link to stop them.
  • Finding and fixing faults, and protecting the service from abuse.

We do not sell Customer Data, we do not use it for advertising, and we do not train any artificial intelligence model on it. Our team does not look at Customer Data except at the Customer's request, to fix a fault in the service, or when the law requires us to. Our team's operations on any account from the admin panel are recorded in an internal audit log under the name of whoever performed them: viewing its data to help, exporting it, changing its status, plan or subscription period, and deleting it. Direct technical access to the database to fix a fault is limited to a small number of our team and is not recorded in that log.

5. The service providers we use

We use the following providers, each only for its own part. Some of them are used only if the Customer connects them itself or uses the related feature.

  • Supabase: the database, sign-in (including password-reset emails), file storage, and the daily encrypted retention copy of the backups in private storage that only our servers can reach.
  • Railway: hosting for the application and its servers.
  • Lemon Squeezy: collects card subscription payments as the Merchant of Record, and processes payment data under its own policy.
  • Resend: sends email: service messages, notices, introductory messages, and the daily backup email to our team, which may carry the encrypted backup itself as an attachment so it can be moved to Google Drive, and always carries it if it could not be saved to storage.
  • Google (Gmail and Google Drive): the daily backup email reaches our team's Gmail mailbox, and a script on our team's Google account saves the encrypted copy to Google Drive as an additional copy outside the hosting provider, on the same cycle, then moves the old backup emails to the trash.
  • Sentry: error monitoring, with its servers in the European Union (Germany). When an error happens, or an unresponsive element is clicked repeatedly, a short recording of the screen's movement is sent to it with all text masked and images blocked, so no names or numbers appear in it.
  • Google Analytics: visit statistics on the website and the orders app (section 3).
  • Google Gemini: the artificial intelligence features; nothing is sent to it unless one of them is used: suggesting a reply to a conversation (the conversation text, the customer's name and their order details), extracting an order from a conversation, the in-app help assistant, the accounting assistant in the accounting module (the company's balances and reports, including customer and supplier names), reading a supplier invoice image, and the sales chat on the home page (the visitor's messages only). We use the paid Gemini API, which does not use the content to train models.
  • Meta (Messenger, Instagram and WhatsApp): only when the Customer's Facebook Page, Instagram account or WhatsApp number is connected, to receive and reply to its customers' messages inside Sijilak. We read the list of Pages it manages so it can pick one, the Page's name, and the public name and picture of whoever messages it; we do not read Page insights, posts, comments, ads or followers. The steps to delete what we hold from Meta are on the data deletion page.
  • Telegram: when the Customer connects its own bot to receive and reply to its customers' messages. We also use it to notify our team internally of each new sign-up (the business name and the owner's email, currency and plan).
  • Store platforms (Salla, Zid, Shopify, WooCommerce, EasyOrders, ExpandCart, Wuilt, YouCan and Zammit): when the Customer connects its store, we receive the store's orders with the buyer's details (name, phone, email and address) and its products, and we send stock levels and shipping status back to Shopify.
  • Shipping carriers the Customer connects (Bosta, ShipBlu, Aramex, Mylerz, OTO, DHL Express and FedEx): only when a shipment is created, the recipient's name, phone, address and cash-on-delivery amount are sent to the carrier it chose.
  • Google Analytics Data API: only when the Customer connects its own Google Analytics account, to show its website statistics inside Sijilak (section 6).
  • The Egyptian Tax Authority (e-invoicing system): only when the Customer presses "Send", the e-invoice it signed is sent to the Authority using its own company's connection credentials. The Authority is an official body that receives the data under the law, not a provider of ours.
  • Browser notification services (Google, Apple or Mozilla, depending on your browser): if you turn notifications on, they receive an alert with the number of waiting messages only, not their content.
  • FormSubmit: delivers messages from the "request a demo" form to our mailbox.

If the Customer connects its own artificial intelligence tool to its account (through MCP), that tool reads its data with the permission the Customer granted and is subject to its provider's terms. Data is processed on the servers of the providers listed above, most of which are outside Egypt.

6. Google user data: Limited Use

  • Sijilak's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
  • Google Analytics data is shown only to the Customer that connected it, is never used for advertising, and is never sold or transferred to any other party.
  • We never use Google user data to train, fine-tune or improve any artificial intelligence or machine-learning model.
  • The Customer can disconnect Google Analytics at any time from inside Sijilak, or revoke Sijilak's access directly from its Google Account permissions page (myaccount.google.com/permissions).

7. How long we keep data, and deletion

  • We keep Customer Data for as long as the subscription lasts. What the Customer deletes itself is deleted from the live database, except posted accounting entries, which are not deleted but reversed with an offsetting entry to keep the books intact.
  • If a payment fails or is late, the account switches after 7 days to "read and export only" mode until it is paid. Data is not deleted because of late payment.
  • After the subscription ends, the account stays in "read and export only" mode for 90 days so you can download your data. We email the account's administrator 30 days and then 7 days before deletion, and once the period is over the data is permanently deleted from our systems within 30 days. This deletion happens only after the 7-day notice has actually been sent; if it could not be sent, or the account has a payment under review or a card subscription that is still active, the data stays and is not deleted until we review the account.
  • If you ask for deletion yourself, we email you about the request, you can cancel it within 7 days, and the data is then permanently deleted within 30 days of your request. A deletion request is not accepted while a card subscription is still active with Lemon Squeezy, so cancel it first.
  • Deletion covers all of the company's data, its stored files (product images, the logo, employee documents and supplier invoice images), and the sign-in accounts that do not belong to another company. Data is deleted from backups in their regular cycle.
  • After deletion we keep only what the law requires, such as the invoices and payments for your subscription with us, and what proves we met our obligations: a record that the notices were sent (their type and date, without any email address or name), and an entry in the admin log that the account was deleted (its name, its number of orders and the deletion date).
  • Error logs are deleted after 90 days, and entries in the IP address record (section 3) once they are more than an hour old, when the next request arrives.

The Customer must keep its books and documents for the period set by law (section 5 of the Terms), so make sure you download your copy before the read-and-export period ends, because we cannot recover data after it has been deleted.

8. Your rights

  • Access and export: the account owner can download its data from inside the account, or ask us for a full copy of it.
  • Correction: edit the data from inside the account at any time, or ask us to correct what cannot be edited there.
  • Deletion: delete whatever data you want, or ask for the whole account to be deleted, in which case its data is deleted within 30 days as described in section 7.
  • Objection and opting out: stop introductory messages from the link in each message, and object to any processing by writing to us. Service messages and the notices the Terms provide for still reach you even if you stop introductory messages.
  • Disconnecting: disconnect any store, channel or Google Analytics account you connected, from inside Sijilak.

To exercise any of these rights, email us at hello@sijilak.com. You also have the right to file a complaint with the Personal Data Protection Center.

9. Data security

We take reasonable measures to protect data, including:

  • Encrypting connections to the service (HTTPS) and requiring the browser to use it.
  • Isolating each Customer's data at the database level, so a user cannot read the data of a company they do not belong to.
  • Storing passwords and personal PINs hashed, never as text.
  • Roles and permissions the Customer sets for each user, and an audit log of operations in the accounting module.
  • Encrypting backups (AES-256) before they are stored or sent.

Even so, no system is completely secure, and we cannot guarantee that a breach will never happen. If we learn of an incident affecting a Customer's data, we notify that Customer. The Customer is responsible for keeping login details confidential (section 2 of the Terms).

10. Changes to this policy

We may update this policy. We announce material changes inside the system and by email 30 days before they take effect, and we update the "Last updated" date above.

11. Contact

For anything about your data: hello@sijilak.com

← Back to home