← v15 index

Secrets vault · /me/a/:slug/secrets

encrypted at rest · masked on read · never in API responses · write-only
v15.1
DESKTOP · 1280px · ig-nano-scout secrets
floom.dev/me/a/ig-nano-scout/secrets
/me / ig-nano-scout / secrets

Secrets

4 set

Env vars attached to ig-nano-scout runs. Stored encrypted, passed only to your app's container at run time.

NAME
VALUE
UPDATED
IG_SESSIONID
••••••••••••••••••••7f4d
Apr 15 · used 2m ago
IG_CSRFTOKEN
••••••••••••a21b
Apr 15 · used 2m ago
EVOMI_PROXY_URL
http://core-residential•••1db7
Apr 12 · used 2m ago
IG_ACCOUNT_TZ
UTC+1
Apr 10 · used 2m ago
ADD A SECRET

Paste from .env files: drop a block of KEY=value lines in NAME and we'll split them.

Where do I get fresh IG_SESSIONID cookies? → docs
MOBILE · 375px · secrets stacked
floom.dev/me/a/ig-nano-scout/secrets
Secrets 4 set

ig-nano-scout

Encrypted at rest. Never returned via API.

IG_SESSIONID
••••••••••••7f4d
used 2m ago
IG_CSRFTOKEN
••••••••a21b
EVOMI_PROXY_URL
••••1db7
IG_ACCOUNT_TZ
UTC+1
v15.1 spec · secrets vault
  • Write-only — values can't be read back through the UI or the API, only rotated or deleted. You lose a value, you replace it.
  • One reassurance banner at the top that explains the trust model in plain language. No tooltips, no hover-reveals.
  • Table with 4 columns: NAME · masked VALUE · last used · actions (rotate / delete). Rows hover-highlight only.
  • .env paste shortcut — drop KEY=value lines into NAME and we split them into N separate secrets.
  • Failed run → direct deep link to the expired secret (e.g. run.html error "Update IG_SESSIONID" jumps straight here).
  • No groups, no environments (yet) — each app has its own flat list. Shared secrets come later if users ask for it.

Reference: Vercel environment variables, GitHub repo secrets. Calm, masked, action-oriented. Security screens should reassure by being boring, not by having ten padlock icons.