Privacy Policy

NAMA OS (“NAMA”, “we”, “us”, “our”) is a SaaS platform for travel businesses, operated by Nama Digital Technologies Private Limited (CIN U62011KA2026PTC224623), A 902, Vaishnavi Nakshatra, 9/36-38, Tumkur Road, Yeswanthpura, Bengaluru North, Bengaluru 560 022, Karnataka, India.

This Privacy Policy applies to all users of the NAMA OS platform accessible at getnama.app and any related subdomains or APIs.

This policy covers personal data collected when you register for an account, use the platform, interact with our customer support, or visit our website. It does not cover data practices of third-party services you may connect to NAMA OS.

When you register or manage your account:

• ▸Full name
• ▸Email address
• ▸Phone number
• ▸Company / agency name
• ▸Role within your organisation
• ▸Profile photo (optional)

Data you enter or import while using the platform:

• ▸Customer / traveller names, email addresses, and contact details
• ▸Lead enquiries and communication history
• ▸Itinerary details: destinations, dates, accommodation, transport
• ▸Quotations, invoices, vouchers, and booking documents
• ▸Vendor profiles and contracted rates
• ▸Financial records including payment amounts and status
• ▸Imported CSV files (leads, rate cards)

Automatically collected when you use the platform:

• ▸IP address and approximate geolocation (country/city)
• ▸Browser type and version
• ▸Device type and operating system
• ▸Pages visited and features used
• ▸Session duration and login timestamps
• ▸Error logs and performance metrics

When you use NAMA OS communication tools:

• ▸Emails sent and received via the platform (SMTP/IMAP)
• ▸WhatsApp messages routed through the platform
• ▸Chat history with NAMA Copilot (AI assistant)
• ▸Support messages sent to our team

• ▸Authenticating you and maintaining your session
• ▸Displaying your CRM, leads, itineraries, bookings, and documents
• ▸Running AI-assisted features (lead scoring, itinerary suggestions, copilot)
• ▸Generating PDFs (invoices, quotations, vouchers)
• ▸Processing payments via integrated payment gateways

• ▸Account registration confirmation
• ▸Password reset and security alerts
• ▸Onboarding drip sequence (Day 0 welcome, Day 1 tips, Day 3 social proof, Day 7 re-engagement)
• ▸Follow-up reminders generated by automations you configure
• ▸Invoices and quotations sent to your clients on your behalf
• ▸Infrastructure alerts (Sentinel) if you configure thresholds

• ▸Understanding which features are used most
• ▸Identifying and fixing bugs and performance issues
• ▸Product usage and performance information used to maintain the service

When AI-assisted intake, EKLA, Copilot or other AI features are enabled, NAMA may send message text and relevant business context to an external AI provider to perform the requested task. This can include automatically routed WhatsApp messages, not only text entered into an AI prompt by a user.

Messages can contain names, phone numbers, travel details and other personal data. The processing path does not guarantee that personal data is removed before an AI request. The provider used depends on the enabled feature and configured service or agency-provided API key.

AI providers and any downstream inference providers have their own retention and processing terms. Contact us for the provider and settings applicable to your account. This policy does not grant permission to use Meta-derived customer content for public-model training, unrelated AI improvement or cross-agency benchmarks.

We rely on the following legal bases:

• ▸Contractual necessity - processing required to deliver the service you subscribed to
• ▸Legitimate interests - security monitoring, fraud prevention, product analytics
• ▸Consent - marketing emails and optional feature usage analytics (you can withdraw at any time)
• ▸Legal obligation - retaining financial records as required by law

NAMA uses several services to store and process data, rather than a single database:

Application services run on Railway and the frontend uses Vercel. Files and media may be stored in Cloudflare R2 or the configured object-storage service. Upstash Redis is used for cache, rate-limit, token-revocation and coordination data. These services may process data in different locations.

• ▸Database storage encrypted with AES-256 at rest (managed by Neon / AWS)
• ▸Sensitive credentials (SMTP/IMAP passwords) are Fernet-encrypted before database storage
• ▸API keys and secrets stored as environment variables, never in source code

• ▸All data transmitted over HTTPS (TLS 1.2+)
• ▸HSTS headers enforced on all NAMA OS domains
• ▸Internal service-to-service calls use Railway private networking or HTTPS

• ▸Role-based access control (RBAC) with roles R0 NAMA Owner, R1 Super Admin, R2 Org Admin, R3 Sales Manager, R4 Ops Executive, R5 Finance Admin, R6 Sub Agent and R7 Client Portal
• ▸Authenticated API requests use Bearer access tokens; the browser keeps the access token in memory and uses HttpOnly cookies for session renewal and page-access checks. Public, webhook and internal-service endpoints use their own access rules
• ▸Admin-only features protected by page-level role guards
• ▸Audit logs maintained for permission changes and sensitive operations

In the event of a data breach affecting your personal data, we will notify you and, where applicable, the relevant supervisory authority within 72 hours of becoming aware, as required by GDPR.

We do not sell, rent, or broker your personal data or your customers' data to any third party. Data is shared with the above sub-processors solely to operate the platform on your behalf.

If you are located in the EU/EEA, UK, or a jurisdiction with equivalent data protection law, you have the following rights:

Email your request to:

We will respond within 30 days. We may ask you to verify your identity before processing the request.

These cookies are required for the platform to function:

Store your preferences to improve your experience:

• ▸Currency preference (stored in localStorage, not a cookie)
• ▸Onboarding progress (localStorage key: nama_onboarding_v2)
• ▸Dashboard checklist state (localStorage)
• ▸Product tour completion state (localStorage)

These preferences are stored in your browser's localStorage and are never sent to our servers.

We use Sentry for error monitoring. Sentry may store a cookie or fingerprint to correlate error sessions. No advertising or cross-site tracking cookies are used.

We do not use Google Analytics, Meta Pixel, or any advertising trackers.

You can control cookies through your browser settings. Disabling the session cookie will prevent you from logging in. Clearing localStorage will reset your preferences and onboarding progress but will not delete any server-side data.

Your data is retained for as long as your account remains active or as needed to provide the service. We will not delete your data due to inactivity without prior notice.

• ▸This part covers a NAMA OS user, meaning a staff member of an agency, asking us to delete their own account data. A request is recorded first and an administrator reviews it. The automated deletion process runs only for requests that have been approved.
• ▸The process follows a registry that classifies every database table our inventory check flagged as possibly holding user-linked data. Each table gets one of these treatments: delete (the row is removed), scrub (the row is kept and the name, email, phone or similar fields are overwritten), clear the pointer (a tenant-owned row is kept and its link to the user is emptied), retain (kept as is, with a recorded reason), or not user data.
• ▸Deleted: the user's copilot conversations and messages, push subscriptions, in-app notifications addressed to them, team chat membership and presence, team memberships, role assignments and permission overrides, single-use password-reset markers, phone mappings, and blog or free-tool sign-ups made with their email address.
• ▸Scrubbed (row kept, identity overwritten): the user account itself (name, email, phone, profile and preference data cleared, and the account deactivated), logged emails addressed to them (recipient address, subject, text and HTML bodies overwritten, and stored template variables cleared; the row itself is kept), pending invitations to their email address, the author name on lead comments (the comment text stays with the lead), the actor name on lead amendment history, "assigned by" names on notifications, approver and uploader names on approval and upload records, their agent booking profile, and NAMA's own sales and demo-booking records that list their email address as a prospect.
• ▸Pointers cleared: on tenant-owned records such as leads (assignee, creator, executive and similar fields), the record stays and the link to the departed user is emptied. Where a field cannot be empty, the record is retained and the link points only to the scrubbed account.
• ▸Team chat messages are kept with their text. The sender link is cleared where the field allows it; otherwise it points to the scrubbed account.
• ▸Retained for legal and accounting reasons: bookings, invoices, payments, ledger and journal entries, tax records, contracts and payouts, and audit-trail records. Any user link on these resolves only to the scrubbed account record.
• ▸Audit log: the audit log is kept. We clear the IP address stored against the user's actions. The user's email address stays in the audit log in clear text, because it is part of a tamper-evident hash chain and rewriting it would make the log fail verification. We keep it on the basis of security and legal audit retention. Sweep results are also written to the audit log with table names and row counts only.
• ▸Completion: a request is marked completed only when every step ran without error and a follow-up check finds nothing left that the registry says should be deleted, scrubbed or cleared. If a step fails, the request stays approved with a note naming the table and the error type, and the next run retries it. When a request completes, the email address stored on the request record is replaced by its SHA-256 hash.
• ▸The automated process runs within the requesting user's own agency. For NAMA platform users who have acted across agencies, links and records in other agencies are outside that automated process and need separate review.
• ▸We aim to respond within 30 days and will identify the scope addressed, lawful retention and any work still outstanding. Applicable legal response obligations remain unchanged.
• ▸Backup retention and removal depend on the configured storage provider and deployment. Contact us for the applicable schedule; this policy does not guarantee a universal additional 30-day backup purge.

• ▸Agencies that use NAMA OS own their customer, traveller, contact, vendor and conversation records, including contacts, conversation threads and messages, bookings and visa applications. These records are not erased when a staff user's deletion request is processed. For those records the process only clears or retains the link to the staff user, as described above.
• ▸Customer-as-subject erasure is a separate matter. A customer or traveller who wants their own data erased should ask the agency that holds it, because the agency's administrators control those records. NAMA OS does not currently run an automated erasure flow for customers or travellers. If you are unsure which agency holds your data, contact us using the details in section 12.
• ▸Personal data of people other than the requesting staff user, such as applicants, partners or end consumers, is not covered by a staff deletion request.
• ▸Agency administrators: if the departing user is the named signatory or contact on the agency company record, an administrator must replace them. If an email configuration uses the departing user's own mailbox, an administrator must rotate it. Integration credentials and webhook secrets belong to the agency and are retained.
• ▸Raw provider and background-job payloads (webhook events and queued job data) may mention a user without being keyed to them. The automated process retains them, and we have not yet confirmed a retention purge for them.
• ▸The bounce and complaint suppression list is retained so that mail to an address that asked not to be contacted does not resume.

Financial records may need to be retained after account closure where applicable accounting or tax law requires it. The required period and access restrictions depend on the record and legal obligation; contact us for the basis and scope of any retention.

Audit and automation logs are used for security and debugging. Audit log handling on a deletion request is described above: the IP address is cleared and the email address stays inside the hash chain. For other logs, retention and deletion depend on the configured service and operational process. A uniform automatic 12-month purge has not been established for every log store.

NAMA OS is operated from India. Hosting, storage, monitoring and AI providers may process data in the United States and other countries, including locations from which staff access data remotely. The applicable countries depend on deployment regions, provider account settings and AI routing; a storage region does not necessarily restrict all processing or support access.

Provider and location information:

• ▸Providers publish their own data-processing terms, location controls and transfer safeguards. These must be checked against the services and account configuration actually used
• ▸Contact hello@getnama.app for the providers, processing locations and applicable transfer safeguards for your account

NAMA OS is a business platform intended for use by individuals who are at least 18 years of age. We do not knowingly collect personal data from anyone under 18. If you believe a minor has provided us with personal data, please contact hello@getnama.app and we will delete it promptly.

We may update this Privacy Policy from time to time. When we make material changes, we will:

• ▸Update the "Last updated" date at the top of this page
• ▸Send an in-app notification and/or email to registered account owners
• ▸Provide at least 14 days' notice before material changes take effect

The effective date of this update is shown at the top of this page. Continued use of NAMA OS after that date constitutes acceptance of the revised policy.

For all privacy-related questions, data access requests, or deletion requests:

We aim to respond to all privacy requests within 5 business days and to resolve them within 30 days.