Contact Private Finance Kit

Do not send bank statements, workbook exports, passphrases, passwords, PINs, OTPs, CVV values, recovery seed phrases, or private family records through the contact form. The form should be used for general feedback, not for handling private finance files.

For product feedback, describe the issue using general terms and screenshots with sensitive values hidden.

• Do not attach plaintext PDFs or spreadsheets
• Do not share account numbers, card numbers, or passwords
• Mask names, phone numbers, and financial values in screenshots
• Keep encrypted files and passphrases separate

A useful report describes the page, browser, device, file type, expected result, and what happened instead. For parser issues, use fake rows or masked examples instead of private statements.

If the issue involves a file, describe the format and rough size. Do not attach or paste the real file. Local-first tools are designed so InCase File does not need private records to understand most bugs.

• Page URL or tool name
• Browser and device, such as Chrome on Windows or Safari on iPhone
• File type, such as PDF, CSV, TXT, XLSX, or ZIP
• A fake example that reproduces the issue
• Screenshot only after hiding private values

Feature requests are welcome when they fit the local-first rule. Good requests explain the real workflow: what file or information a user starts with, what they need to understand, what output would help, and which sensitive data must stay private.

Requests that require storing bank credentials, emailing plaintext files, collecting passwords, or uploading private finance documents are intentionally out of scope for the core product.