Privacy policy

Who processes the data

Stoika gives a venue its workplace: sales, stock, recipes, orders, shifts and the guest menu. A venue’s data is held in that venue’s own database.

The venue owner decides which staff get access and what is entered into the system. Stoika processes that data to make the service work.

What data is collected

Account: username, display name, role, and the email address and phone number when the venue owner enters them.

Sign-in: the password hash, session tokens and their expiry. The password itself is never stored.

Profile photo — only when the user takes one with the camera or picks one from the gallery.

Venue working data: sales, stock levels and movements, recipes, orders, shifts and staff payments. Venue staff enter these records.

Action log: who performed which action and when. The log supports accounting and the review of disputes.

A device token for push notifications and the interface language — only when notifications are enabled.

Technical request data: the IP address and service details in server logs.

What the applications do not do

The applications contain no advertising and no advertising identifiers.

No third-party analytics or tracking libraries are used, and behaviour is not tracked across services.

Data is not sold and is not shared for advertising or data-broker purposes.

The applications do not request location, contacts, calls, SMS or device files.

Biometrics only unlock a sign-in key inside the device: the fingerprint or face never leaves the device and is not available to Stoika.

Device permissions

Camera — to take a profile photo. The picture is sent to the venue server only after the user confirms it.

Notifications — to deliver messages about orders and venue work.

Biometrics — to sign in quickly on the same device without typing a password.

Internet — to open the venue site and exchange data with its server.

Why the data is processed

To provide the application’s features: sales, stock, orders and shift accounting.

To verify identity at sign-in and to separate role permissions.

To keep the service secure: to detect password guessing, token reuse and unauthorised access.

To deliver notifications when the user has enabled them.

Who the data is shared with

The Stoika server that hosts the venue sites, as hosting and storage.

Google Firebase Cloud Messaging, only to deliver push notifications to the device. The device token and the notification text are passed on.

No other recipients. Disclosure is possible only on a lawful, justified demand.

Retention and deletion

Venue data is kept for as long as the venue uses the service.

The venue owner disables or deletes a staff member’s access in the users section.

Session and device tokens are removed when they expire or when the user signs out.

To request deletion of an account or of a venue’s data, write to the contact below. Records the venue’s own accounting requires may be retained by the venue owner.

Security

Traffic is protected with TLS, and the application does not allow cleartext traffic.

Passwords are stored only as hashes, access tokens are short-lived, and the refresh token rotates: reuse revokes its whole family.

Access is limited by the user’s role and venue; data from different venues is never mixed.

Children

The applications are made for work in a venue and are not directed at children under 16. Stoika does not knowingly collect children’s data.

Changes

When this policy changes, the date on this page is updated. Venue owners are told about material changes.

Contact

Questions about data and deletion requests: Telegram https://t.me/stoikaArmeniaBot.