Skip to content
Back to Orrumi

Last updated

Data processing terms.

The responsibilities behind business customer information, from the first signup to a verified privacy request.

Document contents

Parties, scope and agreement

These Data Processing Terms describe the arrangement between a participating business and Kaustabh Mahanta, operating Orrumi. They supplement the Terms & conditions when validly incorporated into an agreement between those parties. Their publication is not a record of acceptance or proof that a required agreement has been executed.

The business ordinarily determines the purposes and permitted use of its customer-program information. Orrumi processes that information to supply the agreed software tools under the business’s lawful instructions. Orrumi separately determines purposes for its own operator accounts, service security, support and administration. Actual roles under Indian law, or controller/processor roles under another applicable law, depend on the processing and agreement rather than a label alone.

Before live customer processing, the parties must confirm the applicable contract, authorised representative, processing instructions, provider arrangements and retention requirements. A card-publication confirmation alone does not establish acceptance of these processing terms. No clause reduces a Data Principal’s statutory rights.

Information and permitted instructions

The processing concerns the business’s enrolled customers and authorised staff. Program information includes requested name, unverified phone, email and city; membership identifiers; consent and notice records; published rules and benefits; qualifying visits, points, levels, coupons and membership validity; related corrections, messages, support and operational records. Business branding and selected public contact/location information are published deliberately.

Instructions are limited to creating and operating the chosen program, staff-confirmed earning and benefit use, permitted reports/exports, separately opted-in Wallet communications, requested Wallet issuance/updates, authorised support and privacy handling, and necessary security or legal obligations. The current service supplies neither payments nor automatic customer identity verification.

The business must not instruct unlawful processing, unrelated advertising, sale of customer lists, cross-business identity matching, child-targeted programs or collection of health records, government IDs, payment credentials or other unsupported sensitive information. Orrumi must identify a suspected unlawful instruction and restrict the affected processing where appropriate. A compulsory legal disclosure is handled under the applicable law, with notice to the business where legally permitted.

Business responsibilities

  • Identify the responsible business and provide clear, accessible notice of the requested data, purposes, communications, recipients and rights before collection. Request only fields needed for the chosen program.
  • Establish the applicable lawful basis and obtain valid consent where required. Keep offers optional, respect withdrawal, and obtain any additional consent needed for a new purpose.
  • Use truthful program terms, honour earned benefits, verify staff authority and promptly remove access when it is no longer needed. Do not share individual staff logins.
  • Protect downloaded copies, limit their recipients and retention, and avoid unconsented outreach. An export permission is not a marketing permission.
  • Cooperate with verified rights, grievances, incidents and lawful retention decisions. Do not withhold personal-data erasure indefinitely merely to preserve an unnecessary identifiable profile.

Phone/email knowledge, a card ID, or a forwarded screenshot is not reliable proof of ownership. The business must use proportionate verification and preserve outstanding benefit rights when resolving closure or erasure.

Security and confidentiality

Processing must be limited to authorised people bound by appropriate confidentiality obligations. Orrumi’s implemented controls include business-scoped database access, role checks, hashed customer access/scan credentials, validated commands, scoped audit records and fenced background work. The Privacy policy explains the current safeguards and limitations.

The parties must maintain reasonable technical and organisational safeguards, appropriate provider contractual safeguards, access reviews, incident detection, secure logging and recoverable backups. Actual hosting settings and retention must be verified; these terms do not assert ISO certification, an independent security audit, India-only processing or an uninterrupted service.

Suspected exposure must be reported through the contact below with minimum necessary evidence. Do not send passwords, usable customer QR credentials, private save links or unrequested identity documents.

Providers and international processing

The current service uses Neon for program databases, Cloudflare for hosting/request processing and public R2 artwork, and Inngest for background orchestration. Clerk handles business identities; Geoapify handles optional business-address lookup. Google Wallet supplies the customer’s pass/account services. The provider list describes each function. Not every provider receives every field or acts as a processor for every purpose.

Where a provider processes program information on Orrumi’s behalf, the relevant engagement must be covered by an applicable processing contract and equivalent required safeguards. Where it determines separate purposes, its independent responsibilities and notice also apply. Necessary current providers must be identified in the parties’ agreement; applicable prior-authorisation, notice and objection requirements govern a material provider change.

Processing may occur outside India. The parties must verify actual regions, applicable government restrictions, transfer conditions and vendor commitments before relying on an arrangement. Foreign-provider use does not remove Indian incident/log obligations. If GDPR applies to particular processing, the parties must separately establish the required Article 28 terms and lawful international-transfer mechanism; this India-first document does not itself supply Standard Contractual Clauses or certify GDPR compliance.

Rights, grievances and incidents

Orrumi must reasonably assist the business with verified access, correction, consent withdrawal, erasure, nomination and grievances, and with information needed for its legal/security duties. The existing private-session cases and reviewed owner workflows have technical limits; a capped export must not be treated as a complete legal response where further information is required.

On becoming aware of a personal-data incident affecting program information, Orrumi must inform the affected business without undue delay, provide known facts safely and cooperate with containment, investigation and applicable notifications. Each party remains responsible for its own statutory reporting duties. A provider’s response window does not extend a legally required deadline.

Where applicable, CERT-In reporting is separate from DPDP breach intimation. DPDP duties and Rules apply according to their commencement and scope. No current marketing channel or unverified contact detail should be treated as a guaranteed incident-notification mechanism.

Retention, return and ending service

The parties must approve a category-specific retention and deletion schedule covering active profiles, security/processing logs, consent and transaction evidence, support cases, exports, public artwork, provider copies and backups. Retention must have an identified purpose or legal requirement and cannot amount to unrestricted identifiable storage forever.

At the end of the agreed processing, return or erase permitted information on lawful, verified instructions, subject to applicable retention and necessary evidence. Restrict retained records to their permitted purposes and explain what remains and why. Existing benefit rights and dispute obligations must be reviewed without silently forfeiting them.

The current implementation supports scoped exports, reviewed profile erasure/restriction, credential revocation and durable Wallet suppression. It does not provide automatic whole-business/Clerk closure, unlimited-history exports, universal timed purging or immediate deletion of offline Wallet/back-up copies. The parties must arrange any required supported extension or operating procedure before committing to a capability beyond those limits.

Evidence, applicable law and limits

Keep evidence of the agreed version and acceptance, provider arrangements, authorised access, rights outcomes, retention decisions and incident handling. Reasonable compliance information may be requested through support, subject to confidentiality, security and the rights of other businesses/customers. This creates no permission to inspect another tenant, bypass database controls or run disruptive tests.

Indian law and applicable mandatory rights govern as described in the main Terms. These processing terms are not a legal certification, an executed vendor agreement, or authority to waive a statutory obligation. Any additional law applicable to the actual business, customers or processing must be assessed and fulfilled separately.

Processing contact and grievances

Email orrumi.cards@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
Kaustabh Mahanta
Grievance contact
Kaustabh Mahanta
Postal address
Noonmati, Guwahati-20, Assam 781020, India
A little clarity goes a long way.Back to top