Jalur Gemilang Official Malaysian Government Website Here's how you know

Official government websites end with .gov.my

If the link does not end with .gov.my, exit the website immediately even if it looks similar.

Secure websites use HTTPS

Look for a lock () or https:// as an added precaution. If not present, do not share any sensitive information.

Sign in
.gov.my accounts only

One link. One read. Then it's gone.

Share passwords, API keys, and files with colleagues across agencies through a link that self-destructs after one view. Collect sensitive forms the same way — submit once, burned.

Domain-gated to .gov.my
Self-hosted, no third-party cloud
Envelope-encrypted file storage
Atomic burn-check, no race conditions
ONE PRIMITIVE, TWO DIRECTIONS

Send a secret. Or collect one.

01

Secret Share

Paste a password or API key, or drop in a file. Set an expiry and a view limit, add a password if you want. Get a one-time link. The recipient opens it, views or downloads once, and it's permanently destroyed.

  • Text encrypted directly in Postgres
  • Files envelope-encrypted into RustFS
  • Burns on GET — reload and it's gone
02

Secret Request

Build a small dynamic form — text, file, date, select, email — and send a one-time link. The respondent fills it in, submits once, and that link is burned. You retrieve the answers through your own dashboard.

  • Generic field types, not hardcoded Q&A
  • Answers encrypted, stored as jsonb
  • Burns on POST — submit-once, always
HOW IT WORKS

Three steps. Then it's out of your hands.

  1. Paste or upload

    Text goes straight to encrypted ciphertext. Files are envelope-encrypted before they touch RustFS.

  2. Set the limits

    Choose an expiry window, a max view count, and an optional password before you generate the link.

  3. Share, then it burns

    One conditional UPDATE checks and burns atomically. First open wins, every other attempt gets rejected.

BUILT FOR GOVERNMENT USE

No shortcuts on how it's secured.

Every session starts with a one-time code sent to a verified .gov.my address — no passwords to leak, no third-party identity provider. Storage is self-hosted end to end: Postgres for metadata, RustFS for encrypted file payloads.

  • .gov.my domain suffix check on every login, OTP-only
  • Envelope encryption — data keys never stored in plaintext
  • Self-hosted RustFS + Postgres, nothing leaves your infra
burn_check.sql
UPDATE secret_links
SET burned_at = now(),
    use_count = use_count + 1
WHERE token = $1
  AND burned_at IS NULL
  AND expires_at > now()
  AND (max_uses IS NULL
       OR use_count < max_uses)
RETURNING *;
Zero rows back means reject. No race conditions.

Stop emailing passwords. Start burning them.

Sign in with your .gov.my email — no separate account, no password to remember.

Sign in with .gov.my email