Privacy Policy

Operator and service scope

PT SINERGI TRANSFORMASI TEKNOLOGI operates Strans Space. This text covers stranspace.com, the business Dashboard at app.stranspace.com, browser POS at pos.stranspace.com, and table ordering connected to an outlet.

Strans handles account-owner information to provide the service. For customer and staff data entered by a business, its owner determines the purpose and permitted access. Owners should provide appropriate notices to their customers and staff.

Account and business setup information

Registration receives the owner's name, email, business name, and sign-in information. Setup may add the business type, outlet identity and address, contact number, cashier name, catalog, and uploaded images. This links the correct owner, business, outlet, and device.

Optional Google sign-in uses the Google identity, email, verification status, and profile information provided by Google. We do not ask for your Google password. Sign-in and verification methods depend on the available service configuration.

Transactions, customers, and devices

Business records may include products, variants, prices, ingredient costs, stock, transactions, payment methods, shifts, cash movements, reports, and receipt settings. Customer records may include names, contact numbers, and transaction history entered by the business.

Table ordering uses the outlet and table identity, items, variants, quantities, and order notes. Additional information depends on fields enabled by the outlet. Avoid unnecessary sensitive personal information.

POS pairing connects a device to an outlet using a code. Session and device information identifies checkout access, operates paired devices, and synchronizes transactions.

Billing and referrals

Subscriptions record plans, periods, invoices, payment statuses and references, and evidence submitted for manual verification. Some payment methods involve the provider you choose.

Referrals record codes, inviter and recipient relationships, qualifying invoices, balances, queues, and adjustments. Verified email identity checks eligibility and repeated claims. These records support payment verification and reward disputes.

Purposes and processing basis

Information is used to create accounts, pair checkout devices, operate orders and transactions, store catalogs, synchronize records, provide reports, activate subscriptions, and handle support or payment disputes.

The basis depends on the purpose: providing a requested service, consent for optional features, applicable legal obligations, or legitimate security interests that consider users' rights. Optional features do not authorize unrelated, unexplained purposes.

Contact, WhatsApp, and optional features

The landing contact form prepares a message in your browser and opens WhatsApp. Entries are not sent to the landing API or saved as new copies by the form. The team receives the message after you press Send in WhatsApp. Older form copies may remain on a device until site data is cleared.

If a business enables receipts, reports, or WhatsApp messages, recipient details and message content are processed for that delivery. The business should check destinations and ensure customer contact use follows the required notice or consent.

If an AI assistant is used, prompts and selected context may be processed to generate responses. Data sent, providers, and retention should be explained within the feature before activation. Avoid sending unnecessary sensitive information.

Cookies, device storage, and logs

The Dashboard uses session cookies to maintain sign-in access. POS and some order flows use browser storage for settings, carts, and local records. Unsynced records can be lost if browser data is cleared or a device is changed; check synchronization first.

Servers or hosting may record IP addresses, access times, pages or endpoints, browser types, and technical events for operation and security. Log types, operator access, and retention should match the service configuration.

The Landing prepares Google Analytics 4 as optional measurement for page views, Start Free clicks, demo interaction, plan choices, continuation to sign-in and opening support in WhatsApp. Opening WhatsApp does not prove a message was sent. The Google tag loads on the production domain only after you choose Allow analytics; declining does not prevent website use. Your choice is stored in your browser and can be changed through Privacy settings in the footer.

Once allowed, Google may receive technical information such as IP address and browser details and use analytics cookies. Measurement code does not include form contents, email addresses, phone numbers, referral codes or raw URL parameters in its events. To understand acquisition, it forwards only predefined source, medium and campaign labels and recognized search or social referrer domains, without referrer paths or queries. This integration does not enable advertising or personalization features. Withdrawing permission stops subsequent measurement in that browser and clears accessible analytics cookies; it does not automatically delete data already received by Google. The company must determine retention, property settings and international processing arrangements before production activation.

Access and data processors

Business access follows owner-assigned roles and outlets. Review staff and devices that retain access. Support staff may need information relevant to a request you submit.

The service may involve hosting and database providers, Google for optional authentication, payment providers for checkout, and WhatsApp for enabled communication. Third-party processing follows provider terms and integration purposes.

Production providers, processing locations, support access, and international transfer arrangements require company confirmation before approval. Application code alone does not establish where information is stored.

Retention and deletion

Account and operational data is needed while the service is used. Plan history limits determine records accessible through the service; they do not promise that all server or backup copies are deleted on the same date.

Retention after account closure, logs, support conversations, invoices, and backups awaits a company decision. This version does not establish automatic deletion schedules. Requests are reviewed alongside verification, dispute resolution, and applicable retention obligations.

Retain needed exports and synchronize checkout records before closing an account or deleting data. Deleting one device's data does not automatically remove server or other device copies.

Rights and data requests

You may request processing information, access or copies of personal data, correction, cessation or restriction, withdrawal of consent, and deletion as applicable. Requests are reviewed against identity, account authority, and relevant legal obligations.

Use Contact with the Privacy topic. Provide the account email, business identity, and request type without passwords or sign-in codes. For records from a business you visited, contact that business first; Strans can help trace requests within its authority.

Security and incident reports

Protect credentials, device codes, and staff access. Avoid shared devices without suitable access settings. Contact the team about unfamiliar access and review connected devices.

Report device loss, incorrect message recipients, or suspected data breaches through Contact. Handling and notifications follow the facts and applicable requirements. This text does not assert unverified certifications, server locations, or security guarantees.

Versions and responsible contacts

Changes to data scope, integrations, or purposes should appear in a new version. An effective date follows company approval of the text and operations. This review version does not replace any official policy that may apply to your service.

Contact PT SINERGI TRANSFORMASI TEKNOLOGI through Strans Space Contact. The responsible privacy channel and request-handling schedule require confirmation before this policy takes effect.