Skip to content
Finndesk is now in private beta — Request early access →
Password Vault

Government portal credentials. Secure, shared, and never in a WhatsApp message.

Your group has 6 entities. Each entity has 8–12 government portal logins. Every portal has a different username format. Right now those credentials are in a spreadsheet, a WhatsApp group, or someone's head. Finndesk's encrypted vault gives your team one secure place — with full control over who can see what.

Zero-knowledge
Encryption architecture
Role-based
Access control
Every access
Audit logged

7-day free trial · Setup in 10 minutes · Cancel anytime

Why this matters

The problem Password Vault solves

Most statutory tasks in group companies go wrong due to operational gaps — spreadsheets and calendars don't talk directly to portals.

🔐

Government portal credentials are stored unsafely

Portal logins for GSTN, EPFO, MCA, Income Tax, and state portals sit in shared spreadsheets, email threads, or WhatsApp groups. When someone leaves, credentials travel with them. When someone joins, you're forwarding passwords in chat.

🔄

One person knows all the passwords — until they leave

Every group has "the person who knows the EPFO password." When they go on leave or resign, filings stop. Institutional knowledge of portal credentials should not depend on a single person being available.

📋

No audit trail for who accessed what

If a portal submission goes wrong, you have no way to know who logged in, when, and what they did. Without an audit log on credential access, accountability for portal actions is impossible.

What it does

Full capabilities

Everything included in Password Vault — built for Indian promoters.

Vault Contents

GSTN portal: login ID, password, OTP phone number
Income Tax e-filing portal credentials
MCA21 portal login per director and company
EPFO employer and ESIC portal credentials
Government portal credentials — GST, IT, MCA, EPFO and more
State Professional Tax and state VAT portals
Custom portal entries: any URL-based login
Notes field for OTP token, dongle location, backup contacts

Security Architecture

Encryption at rest
Zero-knowledge design — credentials encrypted with user session keys, not stored in plaintext on Finndesk servers
Role-based access: Admin and Manager can view, Member role cannot
Per-entity access control: restrict by company
Full audit log: who viewed which credential, timestamp
Audit log exportable as CSV
Automatic session timeout on vault access
Onboarding

Three steps to full coverage

01

Add your portal credentials per entity

For each entity in your group, store the portal credentials in the Finndesk vault. Each entry includes portal name, URL, username, password, and notes. Your team has access without needing to share credentials over chat.

02

Control who can see what

Admins and Managers can access the vault. Members cannot. Access can be further restricted per entity — so a team member who handles only one company in your group doesn't see credentials for the others.

03

Every access is logged

The audit log records every credential view — which user, which portal, which entity, at what time. If a portal session is contested, the audit trail tells you exactly who was in. Export for compliance reviews.

Common questions

Frequently asked questions

Other modules also included in your plan

7-day free trial · All modules included

See Password Vault in action

Add your first entity using a GSTIN and see your compliance calendar live in under 5 minutes.

Start free trial WhatsApp