Security

How we handle your contracts

Last updated: 16 October 2026

Soluqube is operated by Nikhil Laky, a sole proprietor trading as Soluqube, Indore, Madhya Pradesh, India. Soluqube is built and run by one founder. This page states what the product does with a contract you upload today, and what it does not do.

What happens when you upload a contract

You upload one PDF at app.soluqube.com while signed in. The upload limit is 4.5 MB.
The server reads the file in memory, checks that it is a PDF, and extracts the parties, price, performance obligations, term and the page and excerpt each value came from, with the position of that text on the page (from the PDF's text layer) so the cited line can be highlighted.
You review and confirm the extracted terms. Only then is the allocation and schedule calculated.
You download the results (Excel workbook, CSV or JSON). They are built in memory for that download.

What we store, and what we do not

Uploaded contracts are not stored in our database. The PDF and the extracted terms are processed in memory for that request. There is no table for uploaded files, and the upload code does not write the file to disk or to file storage.
Account data is stored. When you sign up we store your email, name, company, role, a scrypt hash of your password, and your last sign-in time. A sign-up also creates a lead record (email, domain, company, role, source).
Error logs from the hosting platform may record request metadata and error messages. Vercel keeps them for a limited period under its log-retention policy; we do not copy them elsewhere.
Contracts you send by email (for example for the free 3-contract workpaper or the design-partner pilot) are handled by the founder by hand, not by the app. They are kept in the founder's Google Workspace account while the workpaper is prepared and supported, then deleted. We delete them earlier on request.

Where it runs

Hosting: the app and this website run on Vercel.
Database: Neon Postgres, used for accounts and sign-up lead records only.
Email: form submissions on soluqube.com are emailed to the founder through Google Workspace SMTP.
Analytics on soluqube.com: Vercel Analytics and Google Analytics.
Payments: Stripe, if and when you pay online. We do not see or store card numbers.

How accounts are protected

Passwords are hashed with scrypt (random salt per password). We never store the password itself.
The session cookie is HttpOnly, Secure (in production), SameSite=Lax, and expires after 7 days.
The app sends a Content-Security-Policy, Strict-Transport-Security, X-Frame-Options (SAMEORIGIN), X-Content-Type-Options (nosniff) and a Referrer-Policy on every response.
All traffic is served over HTTPS.

What we do not claim

We hold no SOC 2 report, ISO certification or other third-party attestation.
There is no self-hosted or private-cloud version today.
Uploaded contracts are not used to train any model.
We do not have a 24/7 support desk. The founder answers within 1 business day.

Your controls

Redact names and counterparties if you prefer. Prices must stay visible: the app refuses contracts with redacted prices, as well as scans without a text layer, invoices and currencies other than USD and INR. Amendments are flagged for manual review and not accounted for.
To test without any confidential data, use a public contract from SEC EDGAR.
We sign a mutual NDA on request. A data processing agreement (DPA) is available on request.
To delete your account or ask what we hold about you, email nikhil@soluqube.com.

Reporting a security issue

Email nikhil@soluqube.com. We acknowledge within 2 business days.

See also: Privacy Policy · Terms of Service