Legal
Privacy Policy
What data Motifuse collects, why, where it is processed, how long it is kept, who else receives it, and the choices you have.
Last updated
Who this covers
This policy applies to motifuse.com: the free public tools, the blog and guides, the marketing pages, customer accounts and workspaces, the premium products (Reconova, DocForge, and SpecTrace), private custom tool projects, and the contact and support channels.
The short version
- Most public tools never send your input anywhere. The work happens in your browser and there is nothing for us to store.
- Where a feature does need a server — an account, a cloud job, a comparison, a contact message — the interface says so before you use it.
- We do not sell personal information, and we do not use your files, datasets, or documents to train AI models.
- Optional analytics and advertising load only after you consent, and never inside a workspace.
- Everything stored for cloud processing has a retention period the platform enforces, and you can delete it earlier.
What you give us
| Category | What it includes | When |
|---|---|---|
| Account details | Email address, and optionally your name, company, profile photo, and a password. | When you create a workspace, or one is provisioned from an accepted quote. |
| Contact messages | Your name, email address, enquiry category, and the message you write. | When you submit the contact form or email us. |
| Project and product content | Datasets, document templates, spreadsheet rows, uploaded documents, project names, references, notes, and review decisions. | When you use a premium product in a signed-in workspace. |
| Private tool requests | The requirements, business context, and contact details you supply on the request form. | When you request a custom tool or a quotation. |
| Billing information | The plan you chose and the payment provider's reference. Card and bank details go to Razorpay directly and never reach Motifuse. | At checkout and on renewal. |
| Feedback | Beta feedback and bug reports, including anything you choose to write into them. | When you submit feedback. |
Collected automatically
- Standard request data — IP address, user agent, referring page, and timestamps — as part of serving pages and API routes, and to apply rate limits.
- Operational logs recording which action ran, how long it took, and any error code. These record counts and codes, not the contents of your datasets or documents.
- Error reports sent to our monitoring service when something breaks, containing technical context such as the route, browser, and stack trace.
- Anonymous usage counters for tools, so we can see which ones people actually rely on.
- Analytics and advertising signals — but only on eligible public pages, and only after you consent.
Files and results
File handling differs by product and by mode, and that distinction matters more than any other statement in this policy.
| Product and mode | Does the file leave your device? | What we store |
|---|---|---|
| Public tools | No. | Nothing. Some tools keep a draft in your browser's own storage. |
| Reconova browser mode | No. | Nothing. Profiling, cleaning, deduplication, and export all run in the tab. |
| Reconova secure cloud | Yes, when you explicitly choose secure upload. | The uploaded file, intermediate artefacts, outputs, and reports — each with its own retention period. |
| DocForge local batches | No. | Nothing. Templates stay in your browser unless you sign in and save them. |
| DocForge cloud batches | Yes. | The template version, the data rows for that job, the generated PDFs, and per-row results. |
| SpecTrace | Yes, always — there is no browser-side mode. | Uploaded document versions, extracted content, comparison findings, and the decisions you record. |
| Resume and career tools | Yes, for text extraction. | The extracted text is returned to your browser. The uploaded file is not kept as a stored document. |
Your files are yours. We do not read them for any purpose other than performing the operation you asked for, we do not share them with other customers, and we do not use them to train AI models.
Why we use it
- To run the feature you asked for — generate the documents, compare the versions, clean the dataset, send the message.
- To operate accounts: sign you in, keep you signed in, and apply the entitlements your plan grants.
- To take payment and issue invoices, through our payment provider.
- To reply to enquiries, support requests, security reports, and copyright notices.
- To keep the platform working and safe: rate limits, spam prevention, abuse investigation, and error diagnosis.
- To understand aggregate usage and decide what to build or fix next.
- To meet legal, tax, and accounting obligations.
We do not sell personal information. We do not build advertising profiles from your files, datasets, or documents, and none of that content is shared with advertising or analytics providers.
Where data is processed
Motifuse is operated from India and served globally through a hosting provider’s network. Depending on the feature, data may be processed in the regions our hosting, database, storage, payment, email, analytics, advertising, AI, and monitoring providers operate in. Privacy laws differ between regions.
The most privacy-preserving option is usually available: Reconova browser mode, DocForge local batches, and every free public tool run entirely on your device and involve no transfer at all.
How long it is kept
| Data | Kept for | Detail |
|---|---|---|
| Work done on your device | Not retained by us at all | Browser-mode processing sends nothing to a server, so there is nothing for us to keep. Local drafts stay in your browser until you clear them. |
| Reconova cloud inputs | 24 hours | Uploaded source files and intermediate artefacts for a cloud job. (RETENTION_HOURS.input) |
| Reconova cloud outputs | 72 hours | Cleaned datasets and exports produced by a cloud job. (RETENTION_HOURS.output) |
| Reconova reports | 7 days | Run, validation, and duplicate-cluster reports. (RETENTION_HOURS.report) |
| DocForge cloud outputs | Set by your plan | The interface shows the exact deletion time for every batch, and one action deletes outputs earlier. Free is local-only and stores nothing. |
| SpecTrace documents | Set by your plan | Retained for the period your plan allows, and deleted when you delete the project. Guest work is deleted after 7 days. |
| Workspace sessions | About 30 days | Session tokens are stored as SHA-256 hashes and expire, or end when you sign out. |
| Contact messages | Kept while relevant | Stored so we can reply and so the form can detect duplicate and spam submissions. Ask us to delete a message and we will. |
| Account and billing records | While your account exists, then as required | Subscription and payment records are kept while the account is active and afterwards where accounting or legal obligations require it. |
Backups and operational logs may hold copies for a short additional period before they age out. Records we are legally required to keep — invoices in particular — are retained for the statutory period even after an account is closed.
Who else receives it
| Provider | Role | What it receives |
|---|---|---|
| Vercel | Application hosting and delivery | Requests to the site, including IP address and user agent, as part of serving pages and API routes. |
| MongoDB Atlas | Primary database | Accounts, subscriptions, projects, job records, contact messages, and site content. |
| Amazon Web Services (S3) | Private object storage and malware scanning | Uploaded files and generated outputs for cloud processing. SpecTrace uploads are scanned by AWS GuardDuty Malware Protection for S3 before anything reads them. |
| Cloudflare R2 | Object storage for images | Blog images and profile photos uploaded through account settings. |
| Cloudflare Turnstile | Bot and spam prevention on forms | Technical signals from your browser when you submit a protected form. |
| Razorpay | Payment processing | Payment and billing details you enter at checkout. Card details are handled by Razorpay and are never received or stored by Motifuse. |
| Hostinger Mail | Transactional email delivery | Your email address and the content of the message being sent — sign-in links, receipts, and notifications. |
| Google Analytics (conditional) | Aggregate usage analytics | Page views and interaction events on eligible public pages. Loads only with your consent. |
| Google AdSense and Google Ads (conditional) | Advertising and conversion measurement | Ad requests and related identifiers on ad-eligible public pages. Loads only with your consent. |
| Google Gemini API (conditional) | AI text generation for labelled career tools | The text you supply, sent only when you trigger an AI action. |
| Sentry (conditional) | Error and performance monitoring | Error reports containing technical context such as the route, browser, and stack trace. |
Providers marked conditional receive data only in specific circumstances: with your consent, on an action you explicitly trigger, or where configured for a particular deployment. Beyond these, we disclose personal information only when the law requires it, to protect rights and safety, or as part of a business transfer — in which case this policy continues to apply to the data transferred.
Analytics and advertising
Eligible public pages may show advertising, which is what keeps the public tools free. Advertising and analytics scripts do not load on workspace, admin, authentication, checkout, or customer-journey routes — those are ad-free by design, not by preference.
- Google Analytics measures aggregate usage on public pages, with IP anonymisation enabled, and only after you consent.
- Google AdSense and its vendors may serve, measure, cap, and protect ads on ad-eligible public pages, and only after you consent.
- Google Ads conversion measurement runs where configured, and is deliberately kept off private routes.
- Where a Google-certified consent platform is enabled for visitors in the EEA, UK, or Switzerland, that platform manages advertising and analytics consent instead of our own banner.
You can additionally manage personalised advertising in your Google Ads Settings.
AI features
A small number of career tools — resume analysis, job-description matching, and letter drafting — send the text you supply to Google’s Gemini API when, and only when, you trigger the action. These features are labelled in the interface before you use them.
Nothing you submit is used to train AI models — not by us, and not by us on your behalf.
Your choices and rights
Things you can do yourself, right now
- Change or withdraw cookie consent from the footer's Privacy choices link.
- Use a browser-mode product, so that nothing is transmitted in the first place.
- Delete projects, datasets, templates, documents, and outputs from inside each product.
- Clear local drafts and site data through your browser.
- Sign out to end your session immediately.
- Limit personalised advertising through your browser, device, or Google settings.
Things we handle for you
Contact us to request access to, correction of, deletion of, restriction of, or portability of personal information we hold, or to close your account. Depending on where you live, you may also have the right to object to certain processing, or to complain to your local data-protection authority.
These requests are handled manually — there is currently no self-service export or account-deletion feature. We may need enough information to confirm your identity before acting, and we may have to retain records the law requires us to keep, such as invoices.
Children
Motifuse is a general-audience site and is not directed to children under 13. We do not knowingly collect personal information from children under 13. Creating an account, subscribing, or purchasing services requires the legal capacity to enter into a contract, which in India is 18. If you believe a child has provided personal information, contact us so it can be reviewed and deleted.
International use
The site is accessible worldwide. By using it, you understand that your data may be processed in countries other than your own, including ones whose privacy laws differ from those where you live. Where a transfer of this kind requires a safeguard under your local law, the relevant provider’s standard terms apply between them and us.
Changes and contact
This policy is updated when features, providers, laws, or practices change. The date at the top of the page shows the current version. Material changes affecting account holders may additionally be notified in the workspace or by email.
For privacy questions or requests, use the contact form and select the privacy category, or email contact@motifuse.com.