Data & Privacy
Juneki is designed to inspect the numbers without keeping the original file. Here is exactly what stays in your browser, what may be stored after an audit, and how to remove it.
Profit Audit CSV/XLSX files are read and checked in your browser. The public synthetic demo is separate from the authenticated paid workflow; it never reads customer files.
Original file bytes, raw workbook cells, formulas, macros, passwords, and external links are not uploaded, persisted, or logged.
After you choose Analyze, an authenticated account with a verified one-time audit entitlement may store the derived Profit Audit report: findings, calculations, confidence and coverage, product/order aggregates, time window, file name and format, row/section counts, mapped roles, and the fact that raw upload retention is false.
PDFs and CSVs are generated on demand and are not retained by Juneki. Compare results and approvals stay in the browser tab and are not stored by the app.
Retention
Saved derived audit results remain until you delete them. There is no raw-file retention period because raw files are not stored. Payment records needed to verify access are retained as billing state; payment details stay with the hosted provider.
Your control
The saved audit view has a permanent-delete control. Deletion is owner-scoped and removes the stored derived run; it does not recover a file that stayed in your browser.
Access & processing
Saved results require your authenticated session and verified audit entitlement and are isolated by account owner. Juneki uses its hosting database and Polsia-managed email/auth infrastructure; no spreadsheet is sent to a third-party file or AI processor in this workflow.