Privacy Policy
This policy describes personal and workspace data Expenu handles today, based on inspection of the product and marketing applications. We do not invent certifications, retention calendars, or processors that are not integrated.
Describes the codebase as of the Phase 7 legal publish. Business identity fields below remain placeholders until published.
Who we are
The service is operated by 9VN Communication Pvt Ltd, registered at SCR 201, 3rd Floor, 150 Meters from Venus Inn Restaurant, Towards Mausima Flyover, Bapuji Nagar, Bhubaneswar, Odisha 751009. Until a dedicated legal email is published ([email protected]), privacy questions should use the Contact form at /contact.
Expenu provides a web application for personal, family, and office expense management, plus this marketing site.
Account information
When you register in the product app, we store account identifiers such as email and name associated with your user record, and authenticate sessions with JWT access tokens.
Passwords are stored as argon2 hashes — they are not stored in reversible form and are not encrypted with AES-256-GCM.
The product app keeps the access token in browser localStorage (key: expenu_access_token) so the client can call the API. That storage is essential to signed-in use.
Contact and enquiry data (marketing)
Submissions on /contact create a MarketingLead record (not an Office customer or vendor). Fields may include name, email, optional phone and company, workspace-type interest, enquiry type, message, optional source path, and optional UTM parameters from the URL.
Optional internal email notification uses the configured email provider (Resend when EMAIL_PROVIDER=resend and keys are present). Without email configuration, the lead is still stored for follow-up.
Workspace and business information
Workspaces hold membership, roles, and workspace metadata. Access is scoped by membership — cross-workspace IDs do not unlock another tenant’s data.
Depending on workspace type, you may store customers, vendors, and related office records you enter yourself.
Financial and ledger data
We process ledger transactions, accounts, categories, budgets and Budget Buckets, recurring rules, receivables and payables (office), and reports derived from posted ledger data.
Bank import accepts statement files you upload (CSV/XLSX). Imports use preview and confirmation — ledger writes occur only after you approve.
People / family member information appears where you invite members and assign roles; visibility of transactions follows role rules in the product.
AI interactions
Optional AI features may send prompts, receipt images, or proposal context to a configured model provider (OpenAI, Anthropic, or Gemini — whichever is configured via environment). See the AI Disclaimer (/ai-policy) for confirm-first behaviour and answer safeguards.
AI proposals do not become ledger authority. Confirmed actions go through ordinary product transaction services with your review.
Uploaded attachments
Receipt and file attachments are stored on the API host under a workspace-scoped directory (ATTACHMENT_STORAGE_DIR or the default storage/attachments path). Filenames are generated server-side; user path injection is not used for storage keys.
Notifications
In-app and email notification delivery may run through the product’s notification and email pipelines when configured. Email delivery uses Resend when that provider is enabled.
Technical, device, and security information
Servers process standard request metadata needed to operate the service (for example authentication context, rate limiting, and operational logs). Redis may be used for jobs and rate limits — it is infrastructure, not a marketing tracker.
We do not claim continuous device fingerprinting or advertising IDs. See the Cookie Policy for browser storage that actually exists.
Cookies and local storage
The marketing site currently sets no first-party cookies and loads no analytics trackers. The product app uses essential localStorage keys for auth, theme, and quick-adds. Details: /cookies.
How information is used
We use data to provide the ledger and workspace features you request, authenticate users, process imports and AI proposals you initiate, respond to marketing enquiries, send transactional email when configured, and maintain security and reliability.
We do not sell personal information. We do not run third-party advertising pixels on the marketing site today.
Service providers and processors
Email: Resend, when EMAIL_PROVIDER=resend is configured.
AI model providers: OpenAI, Anthropic, and/or Gemini — only when the corresponding API keys and AI_PROVIDER configuration are present.
Other contractual processor or DPA counterparty details: [PLACEHOLDER: DPA counterparty details]. We do not invent cloud storage brand names for attachments beyond the local filesystem storage currently implemented.
Security safeguards (scoped accurately)
Workspace isolation and RBAC gate data access. Passwords use argon2. Webhook signing secrets that must be decryptable use AES-256-GCM (see apps/api crypto utility and webhook secret storage) — this is not a claim that all database fields are AES-256-GCM encrypted.
Outbound webhooks can be signed with HMAC-SHA256. Ask Expenu answers are checked by an answer-guard so financial figures not present in tool results are not freely fabricated in responses.
We do not claim SOC 2, ISO, or GDPR “compliance certification” here — those are unpublished.
Retention and deletion
Published retention schedules: [PLACEHOLDER: published retention periods].
Account or data deletion request handling SLA: [PLACEHOLDER: deletion request SLA]. Until published, request deletion or export help via /contact; workspace owners control day-to-day data inside the product.
Your rights and contact
Depending on applicable law, you may have rights to access, correct, or delete personal data, or to object to certain processing. Because governing law is not yet published, we do not invent a jurisdiction-specific rights catalogue.
Contact: [email protected] or the Contact form at /contact. Governing law placeholder: [PLACEHOLDER: governing law].
Changes to this policy
We will update this page when practices change. Material product changes that affect privacy will be reflected here; check the updated note at the top of this document.