Aplauso uses BigQuery as an internal analytical serving layer for authorized Business reporting. It prepares bounded summaries, trends, rankings, and service signals for the scope a user is permitted to access. It is not a customer-managed data warehouse, a direct dataset login, or a source of raw transaction records.
Authorized analytics are scoped
Business analytics is limited to the organization, property, department, or outlet scope that the signed-in user is allowed to view, in the active environment. The service returns a bounded snapshot rather than unrestricted fact collections. A visible aggregate never grants access to another property's records, an employee's private payment details, or the underlying BigQuery tables.
The metrics and comparison period shown in the current Business workspace are the available report. Do not assume that every account has every chart, leaderboard, date range, currency treatment, or analytics control.
Read the data state before using a result
An analytics snapshot identifies whether its serving data is ready, empty, stale, or unavailable, and can provide its as-of time. BigQuery is refreshed and reconciled by platform jobs, including checks for late changes, so a report is not a real-time settlement confirmation or a guaranteed refresh schedule. If the current workspace labels data as stale or unavailable, use that state in the operational decision and retry later or contact Support; do not substitute an old chart for Wallet, payout, or payment status.
Reporting, exports, and privacy
Use the report and export controls currently visible to your authorized Business account. The supported Business export is limited to scoped tip activity and ratings in CSV or PDF. It is not a financial ledger, employee-earnings payroll file, scheduled delivery, JSON or Excel download, custom schema, or customer BigQuery access.
Analytics is privacy-minimized. It is designed to provide counts, rates, trends, authorized organizational dimensions, and operational context without exposing guest names, contact details, payment identifiers, free-text notes, exact guest tip amounts, or raw request bodies. Treat every export and report as operational evidence that still requires the correct authorization and reconciliation for payroll, finance, or legal use.
Getting help
When an authorized report appears incorrect, provide the active environment, authorized scope, visible date range, as-of time or data-state label, and a non-sensitive description of the discrepancy. Do not send credentials, raw data extracts, guest information, card details, or verification codes.