Who this policy covers
This policy covers the Orrumi website, business workspaces, staff tools, customer enrollment pages and Google Wallet loyalty-card features in our invited-adult test service. It applies to visitors, business owners and staff, and people joining a participating business’s loyalty program.
“Orrumi”, “we” and “us” refer to the operator of this service. Orrumi Demo Services is a sample operator name for testing, not a verified legal entity. The contact section identifies which details are placeholders and provides the email to use.
The participating business decides why it runs its loyalty program, which supported customer fields it requests, the rewards it offers, and its permitted communications. Orrumi processes program information to provide those tools. We separately use business-account, support and security information to administer and protect the service. Each party’s legal responsibilities depend on its actual role and applicable law; the business’s own notice and program terms also apply.
Information you provide
- Loyalty signup: name, Indian mobile number, email address and city, only where the business’s signup form requests them. Each field can be required, optional or hidden. We also record your program selection, acceptance of the displayed program terms/data notice, adult confirmation and separate Wallet-offer preference.
- Business accounts: email, authentication identifiers, verification and sign-in information. Clerk handles passwords and authentication factors. Google sign-in can supply the identity/profile details you authorize. Orrumi’s business database stores the identity reference and workspace permissions, not a copy of your password.
- Business setup: business and location names, category, contact phone, support email, website, address, city, state, PIN code, country, time zone, confirmed store coordinates, logo and card artwork. We also keep setup preferences such as the selected business goal, typical-spend band and starter design.
- Staff administration: invited staff email, role, invitation status and dates, who issued the invitation, and the resulting workspace access.
- Program and message content: card designs, earning rules, reward descriptions, exclusions, fulfillment details, published versions, announcement drafts, reusable templates, selected audiences and schedules.
- Support: your email address, correspondence and the information you choose to include when requesting help or exercising a privacy choice.
Please provide only information needed for the service. The current loyalty forms do not request date of birth, government ID, payment-card details, health records or unrestricted customer notes. We do not operate a payment or bank-account collection feature. Business branding uploaded for publication is public material; do not upload customer records or confidential documents as artwork.
Activity and technical information
We create membership and card identifiers, private access credentials, enrollment timestamps, program-version records, stamp balances, recorded visits, earned rewards and redemptions. Staff actions, corrections, reasons, actor identifiers and timestamps form an audit trail. Repeated-request identifiers help prevent duplicate operations; the signup request digest is not a browser fingerprint.
Wallet processing creates provider identifiers, creation/update status, retry/error status and a record when a save attempt is reported. Announcement processing records the audience, eligibility and consent checks, reservation times and provider outcomes. A save click is not confirmed installation; provider acceptance is not proof that a notification was seen.
Website, authentication and infrastructure services may process IP addresses, browser/device information, request paths, timestamps and diagnostic/security logs as needed to deliver and protect requests. We do not use those records to build an advertising profile. The current app does not add advertising pixels or session-replay software.
How we use information
- Authenticate business users, enforce workspace roles and prevent one business from accessing another business’s records.
- Create and operate the loyalty membership you request, recognize your card at the counter, record qualifying activity and determine rewards under the applicable program rules.
- Issue and update your Google Wallet pass, display business and program information, and recover from failed or duplicate technical operations.
- Help a business understand its own recorded memberships, joins, visits and rewards through reports and descriptive segments, such as recent or inactive members.
- Send eligible, separately opted-in Wallet offers; enforce communication limits; record and respect preference changes.
- Provide support, investigate errors or misuse, resolve disputes, maintain security and meet applicable legal obligations.
We do not sell personal information or share it for third-party targeted advertising. The current service does not use customer records to train AI or make credit, employment, insurance or similarly significant decisions. Reports count program memberships and recorded activity, not a verified number of unique people. We do not create a shared customer directory across businesses or merge customers using an unverified phone or email.
We process information for the service you request, your separately chosen promotional communications, and other purposes permitted or required by applicable law. Merely visiting the website, scanning a signup QR, entering a phone number or saving a Wallet card is not consent to promotional messaging.
Wallet and public information
When you request a Wallet pass, Orrumi shares your displayed member name (or a generic member label), card/member identifier, scan credential, stamp progress and available rewards with Google, together with business branding, program details and relevant store information. Selected Wallet announcements are also sent through Google. The current pass payload does not include your phone number, email address or city. A pass object may be created before you finish Google’s save flow.
Public program pages and published artwork expose the business name, chosen support contacts, location, program terms, rewards and branding. Treat their URLs as public. Private customer access and scan credentials should be kept private; do not publish a card’s usable QR code or Wallet save link.
Google controls Wallet display, account/device permissions and notification presentation. We may supply a business’s confirmed store coordinates for nearby relevance. This does not provide Orrumi with your background GPS location or a record of your movements. Deleting a pass in Wallet does not automatically close the membership, erase our records or change the business’s saved offer preference.
Camera and location permissions
The staff scanner asks for camera permission when a staff member starts scanning. QR decoding happens in the browser; the app sends the decoded credential for an authorized lookup, not the camera video. A selected QR image is also decoded locally and is not uploaded by that scanner. Audio is not requested. You can stop the camera or revoke permission in browser settings.
Business setup can request the operator’s current location after they choose that option. For address lookup, coordinates rounded to four decimal places are sent to Geoapify. The operator can enter an address manually instead and must check the store location before publishing it. This permission is for setting up a business location, not tracking loyalty customers.
How long information stays
Retention depends on the purpose of the record, ongoing membership and reward obligations, security needs, disputes and applicable law. We do not treat the end of a browser session as the end of a loyalty membership.
- Accounts, memberships and program records: kept while needed to operate the account/program and address outstanding benefits or requests. The current demo does not run automatic inactivity-based deletion; closure and deletion require a reviewed request.
- Access and invitations: customer browser access expires after 30 days, and an unused staff invitation expires after 48 hours. Expiry disables access or acceptance; it does not automatically erase the underlying record.
- Ledger, consent, message and audit records: may need restricted retention to explain transactions, honor withdrawals, prevent abuse, resolve disputes or meet law. A profile-deletion request may therefore result in erasure or de-identification of some fields and retention of limited evidence.
- Drafts, artwork and support: kept as needed for the current service, request or published card. Public artwork may remain referenced by an existing pass. Unused material is reviewed for removal rather than subject to a promised automatic purge date.
- Logs, backups and provider copies: follow the applicable operational and legal retention requirements and provider deletion cycles. A backup or offline Wallet copy cannot be guaranteed to disappear immediately.
We explain any continuing retention relevant to a verified deletion request. The production data/log/backup schedule is not yet finalized. We do not claim that the demo already implements every required statutory retention or erasure workflow. Downloaded CSVs are separate copies under the recipient business’s control.
Security and processing locations
Orrumi uses business-scoped authorization, role checks, private customer sessions, validation of submitted information and audit records. Customer access and scan credentials are represented by hashes in the database. Published brand artwork is intentionally public. These controls reduce risk; no internet service or device is completely secure.
Our providers may store or process information outside India. We do not promise India-only storage. The actual region, provider contracts, transfer safeguards and any government restrictions must be checked for the deployed service. We use service providers for the purposes described and must meet applicable requirements for overseas processing.
If a security incident affects personal information, we will assess it, take appropriate containment steps and make notifications required by applicable law. Report suspected exposure promptly using the contact email without sending a usable QR or private access link.
Your choices and requests
Wallet offers: the promotional choice is separate and initially unchecked. You can change it on your authorized member page. Declining or withdrawing offers does not remove earned rewards or prevent normal earning/redemption. Withdrawal stops eligibility for pending/future promotional dispatch; a message already sent or accepted by Google may remain visible. Google’s device notification controls are additional, separate controls.
Your information: contact the participating business or email kaustabhworkspace@gmail.com to request access, a copy, correction, closure, deletion, withdrawal of consent, or an explanation of processing. Include the business/program and the nature of your request. A request to stop processing needed to operate a membership may require closing that membership; we will explain the effect on access and outstanding benefits.
We verify authority before revealing or changing private records. Customer phones and emails are unverified in this pilot. Knowledge of a number, email or visible card ID alone cannot authorize an export, recovery, transfer or account merge. We may ask for proportionate evidence using an existing authorized session or a reviewed support process; do not send identity documents unless specifically and lawfully needed.
Except for the in-page offer preference, these requests are handled through support rather than an automated customer rights portal. We aim to acknowledge requests within seven business days and address grievances within one month, subject to any shorter applicable deadline. If we need further information or cannot fully act, we will explain the reason and available next steps.
Applicable statutory rights, including nomination or escalation to a competent authority, are not waived. Where the relevant DPDP provisions and complaint mechanisms are in force and applicable, you may use them after the required grievance process. You can contact us now even where a statutory mechanism has not yet commenced.
Adults-only testing
The current pilot is for invited people aged 18 or older. We do not intentionally recruit children or offer a parental-consent flow. The adult confirmation is a declaration, not verified age assurance.
If you believe a child has provided personal information, contact us so we can review, restrict further use and handle deletion or other necessary action. Businesses must not use this pilot for child-targeted programs or sensitive health/identity tracking.
Changes and applicable law
We will update this policy when the service or relevant requirements change and show the new revision date. Material new purposes or sharing arrangements require appropriate notice and, where required, a fresh choice before processing. An updated policy does not retrospectively create consent.
India’s Digital Personal Data Protection framework has staged commencement. This policy does not represent that all provisions are already in force, that Orrumi is certified compliant, or that testing is exempt from privacy law. Applicable rights and obligations govern, alongside the service’s Terms & conditions.
Contact and grievances
Email kaustabhworkspace@gmail.com for support, privacy requests, or grievances. Include the business/program name and a brief explanation. Do not email passwords, verification codes, private Wallet save links, or photographs of your card’s QR code.
- Operator · demo name
- Orrumi Demo Services
- Grievance contact · demo name
- Ananya Das
- Postal address · fictional sample
- Demo House, Example Lane, Guwahati, Assam 781001, India
These names and the postal address are fictional placeholders for this test site. Use the email above, not the sample postal address. They do not identify a registered company or an appointed grievance officer.