Privacy policy

The personal data Repose processes on behalf of a merchant, why, where it goes and how long it is kept.

Last updated 2026-11-15T00:00:00.000Z.

Repose is operated by Ruckus Repose, Melbourne, Australia. Contact: support@reposeaccess.com.

What Repose is

Repose is a Shopify app for recovery and wellness venues. It sells and redeems timed access to a physical space (sessions, visit passes and memberships) and tracks how many people are booked into the venue at once. A merchant installs it on their Shopify store. The venue’s staff use it in the Shopify admin, and the venue’s customers use it through a booking block on the merchant’s storefront.

This policy describes the personal data Repose processes on behalf of the merchant, why, where it goes and how long it is kept. For the merchant’s own customers, the merchant is the data controller and Repose is a processor acting on their instructions.

The personal data Repose processes

Customer identity. Repose stores the Shopify customer ID against every booking, credit ledger entry, membership, hold and processed order. The customer ID is the only identifier written to Repose’s database.

Names and email addresses are read from the Shopify Admin API at the moment they are needed: when a staff member opens a page that shows them, such as the day’s booking list or the desk’s customer search, and when the app sends a customer one of the emails described below. They are not written to Repose’s database. Repose does not request addresses.

Phone numbers are used at the till only. When staff search for a customer in Shopify POS, Repose reads the phone number from Shopify to show it in the results and to find a customer by phone. When staff add a new customer at the till, Repose can send the phone number that staff typed to Shopify, which keeps it on the customer record. Repose does not write phone numbers to its database, and it does not use them to send messages.

Waiver acceptances. Where the venue requires a waiver, Repose records that a customer accepted it: the customer ID, the version, the time, a hash of the exact wording they were shown, and the IP address the acceptance came from. The wording hash exists so that a customer asking “what did I agree to?” gets the text they actually saw rather than today’s text.

Abuse prevention. When an anonymous visitor holds a time slot while paying, Repose stores a salted SHA-256 hash of their IP address to rate-limit that path. The raw address is never stored for this purpose.

Order data. Repose receives orders/paid and refunds/create webhooks from Shopify and reads the line items, products, customer ID and paid date to decide what access an order granted or a refund withdrew. It ignores orders containing none of its products, and it does not read payment details or addresses. When an order breaks an offer limit, Repose refunds it in full, cancels it unless Shopify has already marked it as fulfilled, and records the order number, the reason and the refund id.

Weekly membership payments. When a venue has Repose take a membership’s weekly payment, Repose stores, for each such membership: the customer ID, the ID of the subscription Shopify creates, the price and schedule the customer agreed to (the plan’s values as they were when they joined), how many payments have been taken, and a reference to the customer’s saved payment method (an identifier only). Repose never receives or stores card numbers or any card data. The card stays with Shopify, which takes each payment. Repose also records each attempt to take a payment (its identifiers, the outcome and Shopify’s error code) so that a member is never charged twice for one payment. When the customer signs in to their own customer account to see their membership, update their card or cancel, Shopify gives Repose a signed token naming that customer, and Repose shows and changes only that customer’s own membership. Repose does not request the customer’s name, email or address for this.

Merchant staff. Repose stores the Shopify session for the installing user (name, email and the API access token), which is what keeps them signed in to the embedded admin.

Free sessions given at the till. When the venue lets its staff give a free session at the POS, Repose records each one: the customer ID, the booking, the reason the staff member typed, the POS device account and the staff member ID the POS reported. The venue sees this log in the app. On a customer redaction request the customer ID is replaced and the reason is removed.

Membership links sent from the till. A membership is never sold at the till. When staff at the POS choose Membership sign-up, Repose records one row for that email: the customer ID, the membership product, the link Repose sent (the membership’s public page on the online store, which carries no password or token), the POS device account and the staff member ID the POS reported, when it was sent, and, once that customer’s own paid order carries the membership, when it was bought. No email address is stored. The venue sees on the customer’s POS screen whether the link was sent and whether they joined. On a customer redaction request the customer ID is replaced with the same irreversible token.

Customer fields Repose writes back to Shopify. Repose writes a small number of values, derived from its own records, onto the customer’s Shopify profile so the merchant can build customer segments on them: whether they hold an active membership, its name and covered-until date, and how many credits of each kind they can currently use. These values contain no name, email or other contact detail, only a status word, a date and a number, and are read by nobody but the merchant, inside their own Shopify admin. The read-only Repose cards on the Shopify product and customer pages work the same way: they show Repose’s own records (an offer’s setup, a customer’s membership, credits and bookings) and do not read or return the customer’s name or email.

Email to customers. Repose can send a customer these emails: one when they book (including when they pay for a held time at checkout), one when a booking is cancelled, one when the venue’s staff move a booking to a new time, and, only when staff choose it at the desk, the venue’s waiver to accept (with a link to pay for a held time when staff hand the sale to the customer’s phone). Staff can send any of these again. Staff can also email a customer the link to a membership on the online store (see Membership links sent from the till above). For a membership paid through Repose, the customer also gets one email when a weekly payment did not go through, one when their card needs updating, one when their membership is cancelled (and one when they cancel and the minimum term keeps it running until it ends) and one before their price changes, and the venue gets one when a member’s payments have stopped and one when a member cancels. Where the store’s customer accounts have a page for it, these emails link to the customer’s account, and the booking emails link to the venue’s booking page when the venue has set its address. Shopify sends the link to update a card. These go only to people who joined a membership paid through Repose, name the venue and the membership, and carry no card detail. The customer’s address is read from their Shopify record at the moment of sending and is not kept. Each message names the venue (and shows the venue’s logo when the venue has set one), the booking, and the venue’s public contact email from Shopify, and nothing else. The merchant can turn these off on the app’s Settings page.

Why

Repose processes this data for two purposes only, which are the two reasons declared to Shopify: store management and app functionality. In plain terms: to let a venue’s staff run the desk, and to let the app work out who is allowed to book what.

Repose does not use personal data for analytics, personalisation, marketing or advertising. It does not sell personal data or share it with anyone for their own purposes. It does not profile customers. It makes two automated decisions: whether a given person may book a given time, based on the credits, membership and waiver the merchant’s own rules define, and, for a membership the customer chose to pay for through Repose, when to ask Shopify to take the next payment, for the price the customer agreed to when they joined. Neither is a decision about the customer’s eligibility for anything beyond what they bought.

Where the data goes

Repose runs on Google Cloud Run and stores data in a Neon PostgreSQL database, both in Australia (australia-southeast1) with the database in ap-southeast-2. Its subprocessors are:

Subprocessor Role
Shopify source of the merchant’s store, customer and order data, and the holder of customers’ payment methods, which take every membership payment
Google Cloud (Cloud Run, Secret Manager, Cloud Build) hosting and secret storage
Neon PostgreSQL database and backups
Cloudflare (Email Service) delivery of the emails described above

How long it is kept

  • Unconverted slot holds are deleted 30 days after they resolve.
  • Bookings, credit ledger entries, memberships and processed orders are kept for as long as the merchant has Repose installed, because they are the record of access the customer bought and the venue’s own history.
  • Sent emails are kept as a record of what was sent and when, without the recipient’s address.
  • On a customer redaction request (customers/redact from Shopify), Repose replaces the customer ID on bookings, ledger entries, holds, processed orders and usage records with an irreversible token, deletes waiver acceptances and memberships outright, replaces the customer ID on membership links sent from the till with the same token, replaces the customer ID on weekly membership payment records with the same token and clears the payment method reference (and Repose never charges that record again), and scrubs any earlier data-request snapshot that held contact details. Bookings and ledger entries are anonymised rather than deleted, so a credit already spent cannot be spent again. Usage records are anonymised for the same reason: each one is this app’s free-tier count and its guard against the same booking being counted twice, not a money record, and erasing one would hand back a place in a venue’s free allowance that was already used. Every field Repose has ever written onto that customer’s own Shopify profile (the membership and credit-balance values described above, and the older waiver-acceptance flag) is deleted from Shopify at the same time.
  • On uninstall, Shopify sends shop/redact 48 hours later and Repose purges every row it holds for that shop.
  • On a customer data request (customers/data_request), Repose assembles everything it holds about that customer (bookings, credits, waiver acceptances with the wording they were shown, memberships, holds and processed orders) for the merchant to forward.

Security

Data is encrypted in transit and at rest, and backups are encrypted. Credentials are held in Google Secret Manager and never in source control or environment listings. Test and production run as separate Shopify apps, separate services and separate database branches, so no test ever touches production data. Access to production data is limited to Ruckus Repose’s sole operator, protected by two-factor authentication and a password manager, and access is logged.

Your rights

A merchant’s customer should contact the venue they booked with. Merchants can reach Ruckus Repose at support@reposeaccess.com for any request about access, correction, export or erasure, and Repose acts on Shopify’s mandatory privacy webhooks automatically in any case.

Changes

Material changes to this policy will be notified to installed merchants before they take effect.