Privacy Policy

Information we process and why

Accounts: names, email addresses, password verification records, account identifiers and sessions support registration, sign-in and access control. The server stores a salted password verification value rather than your original password. Business accounts also include administrator roles and assigned businesses.

Google and Apple sign-in: when you choose an enabled sign-in provider, we receive a provider account identifier, verified email address and, when provided, your name. Apple may provide a private relay email address instead of your personal email. These details verify your identity and link your chosen sign-in method to your SmartAlong account. We request basic identity information, not access to your Gmail messages, contacts or files. Signing in does not grant business or platform administrator permissions; those are assigned separately.

Reservations: selected spaces, visit times, locations, prices, taxes and booking, payment, refund and access references and customer-supplied booking notes support inventory reservations, visit details, transaction reconciliation and access.

Memberships, packages, rentals and gifts: product selections, validity dates, remaining visits or balance, redemption history and merchant-recorded settlement references support your purchases and benefits. Gift purchasers provide a recipient name, email address and optional personal message. These are used to prepare or send the gift and manage a private, single-claim link. A recipient receives the sender's display name, message, merchant and gift value. Claim links grant access to the gift, so share them only with your intended recipient.

Business resources: authorized administrators enter space names, descriptions, public venue locations, time zones, prices, taxes and publication settings. Published listing details are visible to customers. Venue addresses are not device GPS collection.

Support: we receive the sender's email, message and any references or attachments supplied, to handle requests and related account or transaction issues. Do not send passwords, full card numbers or security codes.

Security: hosting and security services process IP addresses and basic request, browser or device information. The application uses derived rate-limit keys, authentication records and business-administration audit events to limit abuse, enforce permissions and investigate issues.

Who can see information

Customers can access their own reservations. Authorized business administrators can view customer names, email addresses and booking, payment and access status for their own business. Platform administrators have the access needed to administer the service. One business is not given unrestricted access to another business's customer records.

Public resource listings do not display customer account information. Service providers receive information needed to deliver their part of the service. Information may also be disclosed where a legally required disclosure applies.

Payments, access and examples

When a venue's online payment service is enabled, YolkPay / Payrix processes payment. Payrix-hosted fields receive card number, expiry and security code; SmartAlong receives a payment token and server-verified results. The flow also uses customer email, billing postal or ZIP code, booking reference, merchant and amount. SmartAlong does not store full card numbers or security codes in its booking database.

Where you choose automatic membership renewal or a business subscribes to a SmartAlong monthly plan, we record the agreed amount, frequency, consent date and cancellation status. Reusable payment references are encrypted on the server and used with the selected YolkPay collection account for scheduled charges. Cancelling renewal stops future scheduled charges; payment and consent records can remain for reconciliation and disputes.

Payrix checkout includes provider diagnostics and ThreatMetrix fraud prevention, which can process device, browser and network information. The current native apps do not include an advertising SDK or native analytics SDK; provider security processing is separate.

When a venue has configured physical access, TTLock receives lock identifiers, visit windows, booking-related references and commands to create or revoke access and respond to requested openings. SmartAlong retains operation references and outcomes for status and issue resolution. Payment confirmation does not itself physically open a door.

Examples: labelled example bookings simulate payment and access without charging a card or operating a lock. Registration and support still process any real personal information you supply, even when you use only examples.

Service providers

SmartAlong uses Sites, the platform serving its website at chatgpt.site, for website hosting; Cloudflare for network delivery, API hosting, security, email forwarding and requested gift-card emails; and PlanetScale for the application's PostgreSQL database. Cloudflare Email Service processes the gift recipient's address, message and private claim link for delivery. An email marked accepted means the provider accepted it for sending; it is not proof that it reached the recipient's inbox.

Messages to info@smartalong.com are forwarded through Cloudflare Email Routing to the operator's support mailbox hosted by Google Gmail. Messages and attachments pass through those mail services.

If you choose Google or Apple sign-in, that provider processes authentication under its own privacy terms. SmartAlong verifies the provider's response on the server and retains the linked provider identifier for future sign-ins. Provider credentials needed to manage or revoke that connection are encrypted on the server. Apple account-revocation notifications can disable a linked sign-in and its SmartAlong sessions.

YolkPay / Payrix, its payment and fraud-prevention services, and TTLock participate when the relevant venue service is enabled. Their own legal and operational requirements can apply to records they hold. Provider processing and backups can involve systems outside your country.

Sessions, browser storage and security

Native sign-in sessions stay in memory; the apps do not save your password to app storage. Web sign-in uses session cookies, and checkout uses a short-lived payment-session capability. Sign-out and successful customer deletion invalidate the corresponding server sessions.

Some website preview pages keep example state in browser local storage. Clearing it removes the local preview state, not a server account or booking. The external browser and payment providers may maintain their own cookies or storage.

A browser sign-in flow uses short-lived state and a one-use return code. The website may keep a limited, non-sensitive booking selection in session storage to restore your place after sign-in. Restoring a selection does not place an order or authorize a payment. Provider and application session tokens are not stored in a return URL.

App-to-service traffic uses HTTPS. Server-side authorization restricts account and business access, and provider credentials remain on the server. The current native apps do not request device GPS, contacts, camera or Bluetooth access.

Retention

Account information remains while the account is active, subject to correction or the deletion process below. Session expiry is enforced even if an expired session record has not yet been purged.

Booking, payment, refund and access-operation records currently remain after customer deletion for settlement, reconciliation, dispute handling and investigation of unresolved results. Necessary accounting records may also be subject to legal record-keeping requirements. Retained references are not represented as fully anonymous: they can remain connected to venue or provider transaction records.

The service does not currently apply an automatic age-based purge to transaction records or support correspondence. You can request a review of retained information associated with you and deletion of information that is no longer needed. A financial or legal retention need may limit removal.

Deletion from the active account does not mean every backup or independent provider record disappears immediately. Provider retention and backup expiry depend on the service and configuration. Contact us to include those records in a data request.

Account deletion

In SmartAlong Customer, use Account → Delete account, or use the web deletion page without reinstalling the app. The self-service flow verifies your password or requires a fresh sign-in with a linked provider, and asks for explicit confirmation. Successful deletion removes linked sign-in identities and revokes the Apple connection where applicable.

Successful deletion replaces the profile name and email with deleted-account values, disables the password verification record, removes customer sessions, and clears associated stored checkout contact details and payment-session capabilities, and clears customer and staff notes on retained storefront reservations. Internal account and transaction references remain as described above.

The automatic flow cannot finish while active reservations, pending product orders, unused passes or gift balances, active rental terms, unresolved gift delivery, payments, refunds or access changes remain. Successful deletion also clears stored gift-recipient details, personal gift messages, claim-link secrets and associated free-text settlement or event notes for the deleted purchaser's completed records. Necessary order and redemption references remain. You can request deletion and help resolving those items by email, including if you cannot sign in. Do not send your password.

Business administrators: request access changes or deletion through the same support address. Business accounts use a separate administration process; the Customer form does not delete an administrator or its business records.

Access, correction and other requests

Email info@smartalong.com with your account email and the information or action requested. We may need to verify account control or business authority before disclosing or changing information. Include a booking reference if relevant, but never a password or full card details.

You can request access, correction, account deletion, or review of retained transaction or support records. Necessary transaction or legal obligations and provider-held records must be considered when handling the request.

Changes to the service or its data handling will be reflected here with an updated date.