GlintiumHome

Privacy Policy

Last updated: 3 October 2026

This Privacy Policy explains how Glintium (“Glintium”, “we”, “us”) collects, uses and protects personal information across the Glintium mobile app (the “App”), our integrations with connected stores, and Glintium POS — our till app for shops. Glintium is operated by Famouslinker Pty Ltd (ABN 78 666 959 084), an Australian company.

1. Overview

Glintium is a social-commerce service. It surfaces real purchases — made in physical stores and online — to the buyer’s friends and wider network, so people can discover products from those they actually know. To do this we work with two groups: people who use the App (“users”) and businesses (“merchants”) — who either connect an existing store or record in-store sales with Glintium POS, our till app.

2. Information we collect from App users

  • Phone number. Used to verify your identity by one-time code at sign-in. We store it only as a one-way SHA-256 hash, not in readable form.
  • Profile information. A username you choose at sign-up, and optionally a display name and profile photo. Your username and photo are visible to other Glintium users (for example on purchases you share with your network). You can edit them in the App, and they are deleted with your account.
  • Who you follow. Glintium is follow-based: you choose to follow other users, and we store those follow relationships (and any follow requests) to build your feed and show your followers/following. You can unfollow at any time.
  • Close Friends list. If you use it, the list of users you add as Close Friends. It is private — people are not told they are on (or off) your list.
  • Contacts (to suggest people you know). If you grant permission, your device hashes your contacts’ phone numbers (SHA-256) on your device and uploads only those hashes so we can suggest contacts who already use Glintium for you to follow. Matching a contact does not automatically connect you — you choose whether to follow. We never receive your contacts’ names or readable numbers.
  • Purchase attribution. When a purchase from a connected store is matched to your account (by hashed phone number), we record that purchase event so it can appear in the feeds of people allowed to see it, according to your sharing audience.
  • Sharing audience. Your choice of who sees your purchases attributed to you — Everyone, Followers (the default), or Close Friends. People outside your chosen audience may still see the purchase, but anonymously, with no link to you. You can change this at any time.
  • Saved products. If you save a product to your list (to buy it later), we store that saved item against your account. Your saved list is private — it is not shown to other users — and you can remove items or delete the whole list at any time; it is removed when you delete your account.
  • Likes and comments. Glintium has product-level engagement: you can “like” a product, and post comments or replies in a product’s public chat. Likes are shown only as an anonymous total (we don’t reveal who liked). Comments and replies are public — visible to anyone on Glintium and shown with your username. You can delete your own comments at any time, and your likes and comments are removed when you delete your account.
  • Sharing a product. You can share a product from the App via a public link. The link opens a web page that shows the product only — its name, image, price and an anonymous count of how many people have bought it — to prompt the person you share with to get Glintium. That page shows no buyer identities and does not name the shop, and purchases by people who muted that shop are left out of the count. Anyone you give the link to can open it.
  • Safety: reporting & blocking. You can report comments or users you believe break our rules, and block other users. We collect the reports you submit and a record of which accounts you block, to review content, enforce our Terms, and keep the Service safe. Blocking is private — the blocked person is not told, and it hides their comments from you. Reported content may be hidden while we review it. Reports are reviewed by people, not automated systems, and are removed with your account.
  • Loyalty (“My code” and stamp cards). Shops that run their till on Glintium POS can offer a loyalty program, and your Glintium app is the loyalty card. If you choose to show your Glintium code at the counter, one scan earns your stamp, adds you to that shop’s member list, and records the purchase to your account — where it is shown to others only under your sharing audience, like any other purchase. The shop can see your username, photo, visit count, stamps and rewards, and your purchases at that shop only — never your activity at other shops or elsewhere on Glintium. Showing your code is optional on every purchase; if you don’t, the sale stays anonymous. Your stamp-cards screen shows you the same membership record the shop sees — member since, visits, stamps and rewards — and you can leave a shop’s program there at any time: leaving deletes your membership (including remaining stamps and unclaimed rewards) from that shop’s member list, and does not change your past purchases or sharing settings. If a shop pauses its program, your stamps are kept and rewards you have already earned remain redeemable.
  • Review invites. Shops on certain plans can invite customers to review them on Google after a purchase. If your purchase is linked to your account (a loyalty or order-code scan), the invite arrives as an app notification — including a device push notification if you have allowed them; if you gave a shop your number for an SMS receipt, the review link may ride that same message. Invites are limited to one per shop per month, are never sent late at night, and every one carries a working opt-out. Opting out once stops review invites from every shop on Glintium. To deliver push notifications we store your device's push token against your account.
  • Ordering ahead (shop menus). Some shops publish their menu in the App. If you build a cart, it is packaged as a signed code on your device and nothing is sent to the shop until that code is scanned at the counter; the scan places the order and has the same loyalty effects as above. You pay the shop directly — Glintium takes no payment.
  • Quote requests (trades and services). Some shops take job quote requests through Glintium (for example a fencer or an electrician). If you ask a shop for a quote, we collect what you put in the request — a description of the job, optional photos you take or attach, and an optional job address — and deliver it to that shop only, together with your profile name. The shop sees the request in its till app to price the job; their quote, and any decline, comes back to you as an app notification, and accepting a quote is always your explicit choice. Quote requests are visible only to you and the shop — never to other users or anywhere public — and any work you agree is paid to the shop directly: Glintium takes no payment. The request becomes part of that shop’s job records (see “Quotes and jobs” below); you can see all your requests in the App.
  • Sharing a job with your own tradie. You can also describe a job and share it with a tradesperson who is not on Glintium yet. Doing this creates a web link that shows the job to anyone who has the link — your profile name, the job description, any photos you attached and the address you entered — so only share the link with people you want to see it. You send the link yourself (for example by text message); Glintium does not message the tradesperson. The link stops working 7 days after you create it if no one has replied. A reply made on that page — the tradesperson’s name, quoted price, note and optional phone number — is stored and shown to you in the App. Your shared jobs, and any replies, are listed in the App’s Quotes tab.
  • Inviting a business to Glintium POS. Authorised Glintium agents can invite a business to Glintium POS from the App by entering the owner’s mobile number (with their agreement, gathered in person). We process that number on the inviter’s behalf to send one invitation SMS containing the invitation link and an opt-out link — following the opt-out stops all future invitation SMS to that number, from any inviter. If the invited number registers a shop within the invitation window (7 days), the invitation — and its extended trial — attaches to that shop automatically, and the shop’s registration is attributed to the inviter. If the invitation isn’t taken up, we remove the raw number 30 days after it expires, keeping only a one-way hash so the opt-out keeps being honoured. Inviters see only a masked form of the number and the invitation’s progress — never anything else about the recipient.
  • Sharing your visits. A finished visit — a completed appointment, a paid job, or an in-store purchase recorded to your account — can be shared, but only when you choose to: nothing is shared automatically. A shared visit shows the shop, what kind of visit it was (for example “Haircut” or “Plumbing job”), and the photo and note you add — never the job description, address, price or appointment time. It is then visible exactly like a shared purchase: people in your sharing audience (your audience setting in the App) see it with your name in their feed, and it also appears anonymously — without your name or profile — in the App’s public Explore area, where anyone can view it, open its page and comment publicly. Only share photos you’re happy for others to see. You can unshare at any time, which removes it (and its comment thread) immediately.
  • Direct messages. If you message another user, we store those messages so they can be delivered and shown in your conversations. They are private to you and the other participant (accessible to our team only where needed for safety, legal or support reasons) and are not end-to-end encrypted. You can start a conversation with someone you follow — either by messaging them about a purchase of theirs you can see, or by sharing a product with them — and blocking prevents messaging. Your messages are deleted when you delete your account.
  • Location — only if you turn on “Nearby”. If you tap Nearby in Explore and grant permission, the App reads your device’s approximate location while the app is open and sends it with that request so we can show shops near you and sort results by distance. We use it only for that request — we do not store your location or build any location history. It is entirely optional: leave “Nearby” off and we never access your location, and you can revoke the permission anytime in your phone settings.
  • Information collected automatically. When you use the App or our websites, our infrastructure automatically logs basic technical data — such as your IP address, device/app information, and request timestamps — to operate, secure and debug the Service. We do not use this data for advertising.

3. Information we collect from connected stores

When a merchant connects a Square, Shopify, Lightspeed Retail or Clover store, Glintium acts as a data processor on the merchant’s behalf; the merchant is the controller of their customer data and is responsible for disclosing this sharing to their own customers. Through the merchant’s authorisation we access:

  • Order details — line items, product names, prices and order identifiers.
  • Store identity — the business name and store domain/identifier.
  • Customer phone numbers — used solely to match a buyer to a Glintium user. They are converted to a one-way SHA-256 hash and are never stored in readable form.
  • Authorisation tokens — the access tokens the platform issues so we can receive the merchant’s order events. Stored securely and revoked on disconnect.

4. Glintium POS — information handled for shops and their customers

Glintium POS is our till app for shops with no POS software. A shop owner signs in with a Glintium account and runs their business on it, and each sale feeds the same purchase network as connected stores. Card payments always happen on the shop’s own EFTPOS terminal — Glintium never receives, stores or processes card numbers or payment details. Data handled through Glintium POS:

  • Merchant account and shop details. The owner’s sign-in phone number (stored hashed, as above), and the shop’s business details — name, category, address, an optional public contact phone number, ABN, logo, and catalogue items with photos, prices and descriptions. Shop details, and the catalogue when the shop publishes its menu, are shown publicly in the App and on the shop’s booking page.
  • Sales records. Each sale’s line items, totals, GST component, payment method (cash or card), refunds and voids, and which staff member and till recorded it. These are the shop’s own business records; we process them on the shop’s behalf to run the till, its reports and its GST summaries.
  • Staff. Staff first names and their 4-digit till PINs, the PINs stored only as one-way hashes. Staff members do not need Glintium accounts.
  • Loyalty and the shop’s customer view. When you show your Glintium code at a POS shop’s counter (see “Loyalty” in section 2), the shop’s member view shows your username, photo, visit count, stamps and rewards, and the purchases you have made at that shop only — never your activity at other shops or elsewhere on Glintium. Customers see a mirror of this membership record in their own app and can leave a shop’s program at any time, which deletes their membership row (and remaining stamps) from the shop’s member list; the shop’s own sales records are unaffected.
  • Optional phone-number attribution. Instead of a code scan, a shop may offer to record a purchase against a customer’s phone number. The number is converted to a one-way SHA-256 hash immediately and is never stored in readable form — it links the purchase to a matching Glintium account (now, or later if one is created), shown under that user’s sharing audience.
  • Bookings and appointments. Shops that offer services keep an appointment book in Glintium POS. A booking records the service, date and time, and the customer details given with it — a name and phone number, and any note — whether it was made at the counter or by the customer on the shop’s public booking page at glintium.com. We process appointment records on the shop’s behalf to run its calendar and to send booking confirmations and reminders. The phone number on a booking is kept for the shop to contact the customer and is also hashed the same way as above: if the hash matches a Glintium account, the booking (and the purchase, once charged) is linked to that account. Appointment records are part of the shop’s business records; to correct or cancel a booking, contact the shop.
  • Quotes and jobs. Shops that quote work (trades and services) can keep their job pipeline in Glintium POS: each job records a description, the customer details that came with it — a name, and a phone number or the requesting Glintium account — plus any job address, photos attached to an app quote request, the quoted price, schedule and outcome, and any invoice the shop raises (its number, amount and notes). Jobs are entered at the shop’s counter or arrive as quote requests from App users (see “Quote requests” above). We process job records on the shop’s behalf to run its pipeline and to deliver quotes, outcomes and invoices (including reminders for an unpaid invoice) — in-app to the requesting account, by SMS to a phone number the shop recorded, or by email to an address the shop enters for the invoice. A phone number or email address on a job is kept for the shop to contact the customer and re-send its invoice. Job records are part of the shop’s business records; to correct one, contact the shop. Invoicing stays between you and the shop — invoices state the shop’s own payment details (such as its bank account), and Glintium never processes payment.
  • Receipts. If a customer asks for a receipt, the shop enters the customer’s email address (or, on some plans, mobile number). We use it once to send that receipt and do not store the address or number itself. If the shop has review invites switched on and one rides the receipt SMS, we keep a one-way hash of the number — never the number — so we can honour the once-a-month limit and the opt-out list.
  • Review invites (shop side). Shops on certain plans can have Glintium invite customers to review them on Google after a sale. The shop sees honest send counts only; the invite log holds the customer reference (account id or hashed number) and channel. A customer’s opt-out applies across every shop and is not overridable by the shop.
  • Barcode lookups. When a shop scans a product barcode we don’t recognise, we look the number up in public product databases (currently Open Food Facts). Only the barcode number is sent — no personal information.
  • Optional training photos (merchant opt-in). A shop can choose to contribute barcode–photo pairs of products from its catalogue to a training dataset for possible future product-recognition features. This is off by default, contains product images only (no customer data), is stored separately from user-facing media, and is never shown publicly. A shop can turn it off at any time in the app.

Purchases recorded on Glintium POS appear in the network exactly like connected-store purchases: attributed to a buyer only via the loyalty scan or hashed-phone match above (and then shown under that buyer’s sharing audience) — otherwise anonymously, with no identity attached.

5. How we use information

  • To verify sign-in and operate your account.
  • To match buyers to users and build your follow graph and feed, and to suggest people you may know.
  • To show purchases to the buyer’s network according to the buyer’s sharing preference.
  • To power product likes and the public product chat (comments) you choose to take part in.
  • To generate the public, shareable product page when you share a product — showing product details and an anonymous buyer count, with no buyer identity and without naming the shop.
  • To keep the Service safe — reviewing reports, moderating content, and enforcing our Terms.
  • To deliver and display direct messages between users who are permitted to message each other.
  • To show shops near you and rank results by distance when you turn on “Nearby” — using your device location for that request only, never stored.
  • To run Glintium POS for shops — the till, reports and GST summaries over their own sales records — and to run shop loyalty programs, including the shop’s view of its own members and the attribution of purchases you choose to claim with a code scan or phone number.
  • To keep shops’ appointment books — including bookings made on a shop’s public booking page — and to send booking confirmations and reminders on the shop’s behalf.
  • To deliver quote requests from App users to the shop they chose, and to deliver the shop’s quote and outcome back — in-app, or by SMS where the shop recorded a phone number.
  • To send a purchase receipt when a customer asks for one, using the address or number provided only for that send.
  • To send post-purchase review invites on behalf of shops that have the feature enabled — throttled, quiet-hours-limited, and always with a working opt-out that applies across all shops.
  • To build an optional product-recognition training dataset from shops that opt in — product images and barcode numbers only, no customer data.
  • To operate, secure, debug and improve the service.

Purchases that match no Glintium user are shown anonymously, with no identity attached. We do not sell personal information, and we do not use it for third-party advertising.

6. Data minimisation & security

We minimise what we hold: your phone number is stored only as a SHA-256 hash, never in clear text, and your contacts’ numbers are hashed on your device and matched in real time without being retained. Data is stored on access-controlled infrastructure (Amazon Web Services) and transmitted over encrypted connections. Access tokens for connected stores are stored securely and removed when a store is disconnected.

7. Sharing with third parties

We share information only with service providers that help us run Glintium, including:

  • Amazon Web Services — cloud hosting and database; Amazon Location Service to look up the map coordinates of shops (from their business address — not your location) so we can show them as “nearby”; and Amazon SES to deliver email receipts.
  • Twilio — sending one-time sign-in codes, SMS receipts and SMS review invites.
  • Expo — delivering push notifications to the mobile apps (receives your device push token, never message content beyond the notification itself).
  • Stripe — Glintium POS subscription billing for merchants. Card details go directly to Stripe and never touch Glintium; we hold only the merchant's Stripe customer and subscription references.
  • Linkly — the EFTPOS integration service that connects Glintium POS to a shop's own bank terminal, when the shop chooses to pair one. At a card sale the till sends Linkly the amount and a transaction reference and reads back the result (approved, declined, and the terminal's receipt text). No customer identity and no card details pass through Glintium or are sent to Linkly by us — the card is read by the shop's terminal and processed by the shop's bank, as it always was.
  • Square, Shopify, Lightspeed Retail (X-Series) and Clover — the commerce platforms merchants connect.
  • Open Food Facts — the public product database we query (barcode number only, no personal information) to suggest product names in Glintium POS.

We may disclose information where required by law.

8. Retention

We keep account data while your account is active and connected-store data while the store remains connected. When you ask us to delete your account, or a merchant disconnects or asks us to delete their data, we delete or irreversibly anonymise the relevant information. Your uploaded contact hashes are not retained — they are matched in real time and discarded; the resulting contact matches (which Glintium users you already know) are removed with your account. Sales and appointment records on Glintium POS are the shop’s business records and are kept while the shop is active; your loyalty memberships and stamps are deleted with your account — or earlier, per shop, when you leave that shop’s program. When a Glintium POS shop closes, it comes off Glintium immediately and, after a 30-day window in which the owner can reopen or export their records, the shop and all of its records — sales, bookings, jobs, and the loyalty cards and receipts customers held at that shop — are permanently deleted, with no anonymised copies retained. Invitation records keep the invited number only while relevant: an invitation that isn’t taken up loses its raw number 30 days after expiry (a one-way hash is retained solely to honour opt-outs).

9. Your rights & choices

  • You can change your sharing audience (Everyone / Followers / Close Friends), manage who you follow, and edit your Close Friends list in the App at any time.
  • You can disconnect a store at any time from the Glintium business page.
  • You can leave any shop’s loyalty program from your stamp-cards screen in the App; leaving deletes your membership and remaining stamps at that shop.
  • You can delete your account at any time in the App (Settings → Delete account) or, without the App, via glintium.com/delete-account. Deletion is immediate and irreversible.
  • You can request access to, correction of, or deletion of your personal information by emailing team@glintium.com.

Merchant customers who wish to exercise data rights should contact the merchant (the data controller); we will assist the merchant in responding.

10. Children

Glintium is not directed to children under 16, and we do not knowingly collect their personal information.

11. Changes

We may update this policy as the product evolves. Material changes will be reflected here with a new “last updated” date, and merchants will be asked to re-confirm the current disclosure the next time they connect a store.

12. Contact

Questions or requests: team@glintium.com. Glintium is operated by Famouslinker Pty Ltd (ABN 78 666 959 084), Australia. This policy is governed by the laws of Australia.