Version 0.8 of 17 November 2026, published at https://business.sigmela.com/legal/privacy.

1. Who is responsible

The business service at business.sigmela.com is provided by Alikhan Mussabekov, Individual Entrepreneur (IE "MUSSABEKOV"), Almaty, Republic of Kazakhstan, email support@sigmela.com (Sigmela, we, or the Operator). The provider is a sole proprietor, not a separately incorporated company.

This Policy covers business-site visitors, account users, restaurant representatives and staff, business contacts and people contacting support. For the purposes we determine, we act as the owner and/or operator of the relevant personal-data database under applicable Kazakhstan law. Processing on a restaurant's instructions is distinguished below.

The service at business.sigmela.ru has a separate operator and policy; the two operators share information only on an independent lawful basis. This Policy is a notice, not consent. Where the law requires consent, we ask for it separately.

2. Restaurant and guest data

The restaurant determines its purposes for orders, fulfilment, staff access and requested business analytics. Sigmela processes the necessary guest and staff information on its documented instructions under Appendix A of the Business Terms (https://business.sigmela.com/legal/terms). In this role Sigmela does not acquire an independent right to sell or reuse identifiable guest data.

The restaurant must provide its own notices and obtain the permissions required for its processing. Sigmela remains responsible for its own applicable duties as a person processing the data. Where Sigmela independently operates guest-account features, those purposes belong in a separate guest notice, rather than being treated as restaurant instructions.

For a meal, delivery or restaurant marketing request, contact the restaurant. We help identify the relevant party and handle information within our control. A restaurant instruction cannot override an individual's mandatory rights.

3. Information, sources and purposes

PurposePeople, information and sources
Account creation and authenticationUsers provide email and name; we create account and session identifiers. A selected available Apple or Google provider supplies the identifier and profile/contact fields authorized for that login.
Business onboarding and supportRepresentatives provide business identity, role, contacts, menus, images, files, integration configuration and correspondence; authorized systems may supply imported information.
Plans, payments and settlementProprietors, representatives and payers supply required registration, tax, address and billing details. For a plan bought through Paddle checkout, we create a Paddle transaction with the plan's price and our purchase and company references; Paddle, as Merchant of Record, collects the payer's name, email, address or country, any VAT identification number and the payment method itself, and returns the transaction, subscription and customer identifiers, status, amounts and tax, and refund, chargeback, failed-payment and cancellation events. For a plan period paid through PayPal, we pass PayPal the purchase and invoice references, a description, the amount and the currency; PayPal collects the payer's email, name, address and payment method itself and returns the order and capture identifiers, amount, currency, status, refund, reversal and dispute events, and the payer details it includes in the order record. We maintain plan periods, subscriptions, invoices and reconciliation records.
Security and reliabilityRequests and devices provide IP address, browser/device information, timestamps, access events and diagnostics needed to operate and protect the Service.
Website and product analyticsVisitors' and users' pages, interactions, events, campaign/referrer information, device details and identifiers; configured identification can associate user ID, email and name. Session replay may record website interactions as described below.
Optional promotional communicationsRecipient contact details and communication preferences, subject to the required separate permission and withdrawal mechanism.
Restaurant instructionsGuests' and staff members' names, contacts, delivery/pickup details, order items and notes, amounts, timestamps, statuses, payment references, order/visit history and staff roles/actions, supplied by them or authorized restaurant systems.

We limit collection to information necessary for the stated purpose. Menus and business contacts become public only within the publication the Merchant directs; an account email or private staff detail does not become public through registration.

The ordinary Service is not intended for biometric identification or unnecessary sensitive information. Do not put identity documents, passwords, full card details or card security codes in menu files, order notes or support messages. Allergy or health information in free text requires particular care and a lawful basis; a text field is not permission to collect it.

Card details are entered through the applicable payment provider. Sigmela uses necessary payment references and statuses. Authorized business administrators can access integration credentials through designated settings; credentials must not be copied to analytics, diagnostic messages or unrelated communications.

4. Permission and processing limits

We obtain consent to collection and processing where Kazakhstan law requires it. Processing without consent must fall within a specific applicable statutory exception; the existence of a business contract is not a universal substitute for consent. Additional rules may apply to a person's location and the service offered there.

Where consent is required, it identifies the Operator, the information, purposes, duration and recipients, and any disclosure or cross-border conditions, in the form the law requires, and we keep a record of it. A login code, acceptance of the Terms or continued use of the website is not consent to these operations.

A representative's authority over a restaurant does not extinguish the rights of its employees or guests. A Merchant supplying someone else's data must have the necessary authority and permissions. Required information is identified in the relevant flow; without essential account/contact information we may be unable to provide access.

Operations include collection, recording, organization, storage, retrieval, use, correction, authorized transmission, blocking, anonymization and destruction, limited to the stated purposes. Access by personnel must be limited to their authorized role and work. Decisions with legal consequences based solely on automated processing require the applicable legal conditions and opportunity to exercise relevant rights; AI recommendations are intended for human review.

5. Cookies, sessions and analytics

Necessary browser and session mechanisms support authentication, preferences and operation. Blocking them may prevent sign-in. Email login codes have a limited validity period; the standard configuration is 10 minutes. Expiry of a code or session is not deletion of the account or all security records.

PostHog, when configured, receives page views, page exits, exceptions and explicit product events; after sign-in, identification attaches the account ID, email and name. PostHog runs on its United States cloud; the browser reaches it through our proxy domain pp.sigmela.com, which does not change the recipient. Cookie names and expiry depend on supplier settings, versions and browser behavior; they can be inspected and removed in browser storage controls. Removing browser storage does not remove information already sent to a supplier.

When a Paddle checkout opens in the cabinet, the page loads Paddle.js from Paddle's servers; Paddle then processes checkout, device and payment information under its own privacy notice. First-touch campaign, referrer, page and time information is stored in sigmela_attribution. The implementation treats it as valid for 90 days and removes an expired record on the next read, rather than running deletion in a closed browser. Attribution sent during registration may also become part of the server-side account record and is subject to its purpose and retention rules.

The website shows no cookie banner, and continuing to use it is not consent. Where the law requires consent, we ask for it separately; contact us to withdraw it or to ask about processing. Essential service messages are separate from optional marketing, and registration does not subscribe a person to promotional messages.

6. Recipients and integrations

Recipients may process information for us, on a restaurant's authorized instructions, or for their own stated purposes where they are independent providers. Disclosure is limited to the relevant service and lawful permissions.

Service / recipientFunction and information
Hetzner Online GmbH, Germany; servers in its Helsinki data centre, FinlandServer infrastructure: the business website, the Service's application servers, primary databases, image processing and technical service components. Web-server logs record IP address, time, requested address, response status, referrer and browser information.
Cloudflare, Inc., United States; R2 object storage with EU jurisdictionMedia and file objects and off-server database backups, stored in the European Union.
Resend (Plus Five Five, Inc.), United StatesTransactional email delivery: recipient address, message content including a login code, and delivery diagnostics.
Apple or Google, where available and selectedAuthentication and permitted profile information. The contracting provider and its own processing depend on the selected service and region.
PostHog Inc., United StatesConfigured product events, technical information, identified account details and registration attribution, received through the pp.sigmela.com proxy.
OpenRouter, Inc., United States, and the selected model providerPrompts, selected context and media submitted to an available AI feature. The actual model route determines additional recipients.
Paddle.com Market Limited (United Kingdom), Paddle.com Inc. (United States) or Paddle.com (Canada) Ltd, depending on the buyer's location; Merchant of Record for plans bought through Paddle checkoutSells the plan, processes the payment and handles tax, invoices, billing support and refunds for those orders. The plan's price and our purchase and company references from us; payer name, email, address or country, VAT identification number and payment method collected by Paddle at checkout; transaction, subscription and customer identifiers, status, amounts, tax, and refund, chargeback, failed-payment and cancellation events returned to us. Paddle processes buyer and payment information as a controller under its own privacy notice.
PayPal, through the PayPal entity serving the payer's region, such as PayPal (Europe) S.à r.l. et Cie, S.C.A., Luxembourg, or PayPal, Inc., United StatesPayment processing for plan periods sold directly by Sigmela. Payer email, name, address and payment method are collected by PayPal at checkout. Purchase and invoice references, description, amount and currency from us; order and capture identifiers, amount, currency, status and refund, reversal and dispute events, and the payer details PayPal includes in the order record, returned to us. PayPal processes payment information for its own regulated purposes under its own privacy statement.
Banks and payment providers identified for the transactionNecessary payer, amount, payment-status and settlement information. Guest payments use the Merchant's acquiring arrangement.
POS and other systems selected by the MerchantOrder, catalog, payment-status and necessary contact information within the authorized integration.
Authorized support and technical personnelInformation necessary for the specific support, maintenance or incident task, subject to confidentiality and access restrictions.

Supplier notices include Hetzner (https://www.hetzner.com/legal/privacy-policy/), Cloudflare (https://www.cloudflare.com/privacypolicy/), Apple (https://www.apple.com/legal/privacy/), Google (https://policies.google.com/privacy), Resend (https://resend.com/legal/privacy-policy), PostHog (https://posthog.com/privacy), OpenRouter (https://openrouter.ai/privacy/), Paddle (https://www.paddle.com/legal/privacy), and PayPal (https://www.paypal.com/myaccount/privacy/privacyhub). They describe suppliers' responsibilities and do not replace ours.

An AI integration is not permission to transmit arbitrary guest data. Before personal data is used with a model, we establish the actual recipient, processing country and retention and use conditions and obtain the required permissions. We do not promise that every model is local or that every supplier excludes retention or training; the Business Terms grant no right to train on instructed guest data.

We may also disclose necessary information in response to a valid legal requirement, and we provide information about actual processing and recipients in response to a lawful request.

7. Storage and international processing

The Service, including the business website and the databases behind it (PostgreSQL and ClickHouse), runs on Hetzner servers in Helsinki, Finland. Media files and off-server backups are stored in Cloudflare R2 with EU jurisdiction. The service at business.sigmela.ru runs as a separate deployment with its own databases.

Kazakhstan's personal-data law sets requirements for where personal-data databases are stored and separately regulates cross-border transfers. Where that law requires a database to be stored in Kazakhstan, we keep the affected records in Kazakhstan; where it regulates a transfer abroad, we obtain the required permission before the transfer. Disclosure of foreign hosting and consent to a transfer do not replace a storage requirement.

Email delivery, analytics, AI features, plan orders through Paddle, payments through PayPal and selected login providers involve the United States, United Kingdom, European Union and other recipients listed in section 6; remote technical access can involve further international processing. A Sigmela proxy domain does not change the upstream recipient. We establish the actual countries and protective arrangements and obtain the legally required permissions before the corresponding transfer.

Information about actual recipients, purposes, countries and applicable permissions is available through the contact in section 10 within the legally required scope. A new purpose or recipient is not justified merely by changing this notice.

8. Retention, closure and deletion

We retain information only while necessary for its stated purpose or an applicable legal obligation. The applicable criteria are:

CategoryRetention and ending the purpose
Accounts, roles and contactsWhile needed for active access and the business relationship; after closure, delete or restrict individual records retained on a separate lawful basis.
Support correspondence and supplied filesWhile needed to resolve the request or establish/defend a substantiated claim; remove unnecessary copies and material without a continuing purpose.
Billing, tax and payment recordsFor the mandatory period applicable to the particular record and proprietor; closure does not erase a statutory recordkeeping obligation.
Instructed guest/staff dataFor the restaurant's lawful purpose and instructions, followed by return/deletion; an export opportunity does not postpone a mandatory earlier deletion.
Analytics and attributionWhile the specified purpose and required permission remain valid, including appropriate deletion or anonymization at suppliers. A browser lifetime is not the server's retention period.
Security and diagnosticsFor the justified security/investigation purpose. Standard local monitoring configuration limits Loki to 72 hours and Prometheus to 7 days; this is not a universal limit for other databases or suppliers.

The backup storage's routine lifecycle settings are: PostgreSQL hourly copies for 2 days, daily for 30 days and monthly for 400 days; ClickHouse daily copies for 7 days, weekly for 28 days and monthly for 365 days. These are backup-object rotation periods, not a retention period for personal records.

Lawful correction, blocking and destruction requirements take precedence over routine backup rotation. Relevant copies must be identified and restricted, and required destruction must be completed within applicable deadlines. Restoration must not restart processing that has lawfully ended. Records preserved for a legal obligation or substantiated dispute must be limited to that purpose and access.

Withdrawal, closure and deletion have different effects. Where the law permits or requires continued processing despite a request, we explain the reason and applicable limits. We do not promise that account closure instantly erases every accounting record or backup.

9. Protection and incidents

The shared service uses account and venue access controls, protected connections, database backups and technical monitoring. Database backup workflows use encryption. These measures are not a claim of certification, encryption of every application field or absolute security.

The Operator is responsible for arranging appropriate organizational and technical protection, assigning responsibility, keeping access current, binding personnel and suppliers to relevant duties and investigating unauthorized processing. Upon an incident, we must contain it, assess affected information and make notices required by applicable law within its deadlines. For restaurant-instructed information, we notify and assist the restaurant without undue delay so it can fulfil its own duties.

Report a suspected personal-data incident to support@sigmela.com, with the subject “Personal data incident”. Include affected account/order references and the nature of the problem; do not email passwords, card secrets or unnecessary copies of affected data.

10. Your requests and complaints

Contact support@sigmela.com to ask whether and how we process your information, request access or correction, withdraw applicable consent, request blocking or destruction, object to relevant processing or exercise another right under applicable law. Describe the request and provide enough information to locate the account. We verify identity and authority proportionately and request a secure method if sensitive verification is necessary.

We respond and take action within the deadline applicable to the particular request under Kazakhstan law and any other mandatory law that applies. A general support or contractual claims deadline does not extend a statutory personal-data deadline. If we cannot grant all or part of a request, we explain the legal reason and available recourse. A record required for one purpose cannot be retained indefinitely for unrelated uses.

You may complain to Kazakhstan's Information Security Committee, whose official personal-data protection page (https://www.gov.kz/memleket/entities/infsecurity/activities/9552?parentId=6) identifies the competent authority, including through the eOtinish government appeals service (https://eotinish.kz/). Judicial remedies and other competent authorities available under applicable law remain available. Contacting us first is not a mandatory waiver or restriction on those rights.

11. Versions and a future company

We date and version this notice and communicate material changes. A revision does not replace consent where a new purpose or disclosure requires it. The version date is not evidence of an individual's consent.

Incorporating a company later does not automatically change the Operator. Before an effective transfer, the parties must identify the successor, transferred information, purposes, date, continuity of obligations and required notices, permissions and contractual arrangements. Until then, Alikhan Mussabekov, Individual Entrepreneur (IE "MUSSABEKOV"), Almaty, Republic of Kazakhstan, remains the .com provider and responsible for its processing.