Legal · Privacy

Privacy Policy

What Motifuse collects, why, where it goes and how long it stays — written against what the code does, and pruned of anything this deployment cannot actually do.

What happens to my files Exercise a right

Last updated: 14 August 2026
Data controller: Motifuse Solutions
Privacy contact: contact@motifuse.com
Named keys: Cookie Policy

Plain English

The short version

What this policy says, in ordinary words. The numbered clauses below are the authoritative version — this is here so you know which of them apply to you.

Most tools never send anything
The work happens in your browser, so there is nothing for us to receive, store or lose. Where a feature does need a server, the interface says so before you use it.
See it product by product
Nothing is sold, nothing trains a model
We do not sell personal information, and nothing you submit is used to train an AI model — not by us, and not by us on your behalf.
Where AI is used
Optional tracking is genuinely optional
Analytics and advertising load only after you consent, and every key they set is named on the Cookie Policy. Declining leaves the whole tool directory working.
Analytics and advertising
You can ask for any of it back or gone
Access, correction, deletion, portability or account closure — requested by email and handled by a person, because there is no self-service export yet.
Your rights

This summary is not the agreement. Where the summary and the numbered clauses differ, the clauses are what applies. They are below, and each one has its own link.

The whole thing in four steps

Where your data goes

Every clause below is a detail of one of these four. If you only read one section of this policy, the one about files is the one that matters.

1What arrivesWhat you type or upload, what your browser sends as part of any web request, and what optional analytics report if you allowed them.Read the clause
2What it is used forRunning the feature you asked for, operating your account, taking payment, replying to you, and keeping the platform working and safe.Read the clause
3Where it goesYour device where possible; our servers where a feature cannot run locally; a named provider where one is genuinely needed.Read the clause
4When it leavesOn a retention period the platform enforces, when you delete it, or when you ask us to remove it.Read the clause

The distinction that matters most

What happens to a file, product by product

File handling differs by product and by mode, and that difference matters more than any other statement in this policy. 3 of the 4 paths below never send your file anywhere at all.

What happens to files in each product and mode
Product and mode	Does the file leave your device?	What is stored
Public tools	No	Nothing. Some tools keep a working draft in your own browser storage.
Reconova browser mode	No	Nothing. Profiling, cleaning, deduplication and export all run in the tab.
DocForge local batches	No	Nothing. Templates stay in your browser unless you sign in and save them.
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. They are not read for any purpose other than performing the operation you asked for, they are never shared with other customers, and they are not used to train AI models.

Answerable for all of this

Who controls your data

The data controller is Motifuse Solutions, a sole proprietorship in Kerala, India, registered with India’s Ministry of Micro, Small and Medium Enterprises as a Micro enterprise. Its proprietor is Rakesh P R, and that is who decides what data is collected and why.

There is no separate data-protection officer. That address reaches the person who runs the service directly.
No separate organisation processes your data on their behalf beyond the providers listed in this policy.
The full registered address is provided on request where one is needed for a legal or regulatory purpose. It is not published here because a home address on an indexed page is permanent.

Make a privacy request

1.Who controls your data

A named individual operating a registered sole proprietorship, not an anonymous entity.

The data controller is Motifuse Solutions, a sole proprietorship in Kerala, India, registered as a Micro enterprise under Udyam Registration Number UDYAM-KL-10-0064594. Its proprietor is Rakesh P R. The enterprise is located at Ottappalam, Palakkad District, Kerala 679302, India.

There is no separate data-protection officer. That address reaches the person who runs the service directly.
No separate organisation processes your data on their behalf beyond the providers listed in this policy.
The full registered address is provided on request where one is needed for a legal or regulatory purpose. It is not published here because a home address on an indexed page is permanent.

2.What you give us

Everything in this clause is something you typed, uploaded or chose.

Information you provide directly
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.
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 the payment provider 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.

3.Collected automatically

What arrives as a by-product of a web request, and what is recorded when you sign in.

Information collected automatically
What	Detail
Request data	IP address, user agent, referring page and timestamps, as part of serving pages and API routes and applying rate limits.
Session records	When you sign in, the session record holds a hashed session token, your account email, a shortened description of the device and browser, and a salted one-way hash of the sign-in IP address. The hash lets an unfamiliar sign-in be recognised; it cannot be turned back into your address.
Operational logs	Which action ran, how long it took and any error code. These record counts and codes rather than the contents of your datasets or documents.
Error reports	Sent to the monitoring provider when something breaks, containing technical context such as the route, browser and stack trace. Where an error triggers a session replay, text and form inputs are masked and media is blocked before anything leaves your browser.
Anonymous tool counter	A first-party daily total storing only the tool slug, the date and a count, for 180 days. Optional operation totals add a fixed event name and a broad duration bucket. Skipped entirely when Do Not Track or Global Privacy Control is set.
Analytics and advertising signals	Only on eligible public pages, and only after you consent.

4.Why it is used

Seven purposes, and four things that are not done with any of 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 the 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.

5.Where it is processed

India, plus wherever the named providers operate — and, wherever possible, your own device.

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 those regions.

The most privacy-preserving option is usually available: the browser-mode tools listed in the file table run entirely on your device and involve no transfer at all. Where that option exists, it is the default rather than an upgrade.

6.How long it is kept

Periods the platform enforces, not periods it intends.

Retention by data type
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.
Workspace sessions	About 30 days	Session tokens are stored as SHA-256 hashes and expire, or end when you sign out.
Anonymous daily tool counters	180 days	The first-party counter stores only {slug, date, views}; optional operation totals add a fixed event name and duration bucket. Expiry is set by RETENTION_DAYS in /api/tool-usage.
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.

Records the law requires us to keep — invoices in particular — are retained for the statutory period even after an account is closed.

7.Who else receives it

Named providers, what actually reaches each, and which are conditional.

Service providers and what reaches them
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.
Cloudflare R2	Public image and private product-file storage	Blog images and profile photos, plus private Store release assets addressed by product, version, and asset keys. Paid files are delivered only through short-lived signed links.
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.
Paddle (conditional)	Merchant of record for Digital Store payments	Purchaser identity, country, tax and payment details entered at checkout. Motifuse receives transaction, customer, tax, refund and chargeback status; card details are handled by Paddle.
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	Auto Ads requests and related identifiers on public pages. Loads only with your consent.
OpenAI 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.

For a Digital Store purchase, the approved payment provider identified at checkout processes payment data independently. If Paddle checkout is enabled after approval, Paddle acts as reseller and Merchant of Record and processes checkout data under its own Privacy Policy. Motifuse receives only the transaction and purchaser records needed for fulfilment, accounting, fraud handling, and support.

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, personal information is disclosed only where 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.

7A.Digital Store purchases and downloads

The purchase record is durable; each private download link is temporary.

A Store checkout creates a short-lived purchase session. When the approved provider confirms a completed transaction through a verified notification, Motifuse stores the order identifier, product, purchaser email in normalized form, provider customer and transaction identifiers, currency, total, status, tax-related transaction data, timestamps, and the entitlements and licenses created from that order. Card or bank credentials are not received by Motifuse.

Paid release files are stored in a private Cloudflare R2 bucket under random, product-scoped keys. A signed-in account with an active entitlement can request a download; that request is logged against the entitlement and returns a single-object link that expires within minutes. A verified account may claim a guest purchase only when its verified email exactly matches the purchaser email.

Order, entitlement, webhook and audit records are retained for accounting, fraud, support and legal purposes. Download telemetry is limited to the account, order, product, release or asset, timestamp, and a one-way request fingerprint; resume content and downloaded file contents are not analytics fields.

8.Cookies and consent

Every key is named individually on its own page rather than summarised here.

Motifuse sets a small number of first-party cookies and browser-storage keys. Third-party analytics and advertising set cookies only after you consent; until then Google’s tag operates in cookieless Consent Mode.

Every key — name, kind, purpose, category and duration — is listed in the Cookie Policy, which also carries the control for changing your choice. That page is written to be checked against your own browser rather than believed.

9.Analytics and advertising

Consent-gated, route-restricted, and with one exception that is stated rather than rounded off.

Google Analytics measures aggregate usage on eligible public pages, with IP anonymisation enabled. It sets cookies only after you consent, and its measurement is disabled on private routes.
Google AdSense and its vendors may serve, measure, cap and protect Auto Ads on public pages, and only after you consent. The AdSense script is not fetched unless you opt in.
Where a Google-certified consent platform is enabled for visitors in the EEA, the UK or Switzerland, that platform manages advertising and analytics consent instead of our own banner.

10.AI features

Named surface by surface, and only on an action you trigger.

Career tools
Resume analysis and scoring, job-description matching, cover letters and interview answer structuring send the text you supply to the AI provider when — and only when — you trigger the action. Each is labelled in the interface before you use it.
PDF Studio document questions
The document-question feature sends text extracted from your PDF and returns an answer checked against that text. It runs only when you ask a question.
Reconova assist
Optional help with explaining a column, suggesting a transformation or matching fields by meaning. Values are redacted before anything is sent, and it requires a paid workspace.

What involves no model at all

DocForge document generation is deterministic. No model sees your template or your data rows.
Reconova's profiling, cleaning, deduplication and matching are deterministic. The optional assist features are separate, labelled, and off unless a deployment enables them.
Calculators, converters, formatters, developer utilities and the PDF tools other than document questions involve no model at all.

Nothing you submit is used to train AI models — not by us, and not by us on your behalf. Every AI-assisted feature is labelled in the interface before you use it, and none of them runs on its own.

11.Your choices and rights

Six things you can do without asking, and six you can ask for.

Things you can do right now

No request, no waiting, no identity check.

Change or withdraw cookie consent from the Cookie Policy or the footer's Privacy choices link.
Use a browser-mode tool, 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 to ask us for

One email covers any of these. Say which you want and the account it concerns.

Access to the personal information held about you
Correction of anything inaccurate
Deletion, or closure of your account
Restriction of certain processing
A portable copy of what you supplied
Objection to processing, where your local law provides it

Use the contact form contact@motifuse.com

These are handled by a person. There is currently no self-service export or account-deletion feature, and this policy does not pretend otherwise.
Enough information may be needed to confirm your identity before acting on a request.
Records the law requires us to keep — invoices in particular — are retained even after an account is closed.
Depending on where you live, you may also have the right to complain to your local data-protection authority.

12.Children

Stated policy. Not an implemented control, and the difference is stated.

Motifuse is a general-audience service and is not directed to children under 13.
The minimum age to hold an account is 13, and personal information is not knowingly collected from anyone younger.
Paid plans and commissioned projects require the legal capacity to enter a contract — 18 in India — so an account holder between 13 and 18 can use the free tools but subscribes only through a parent or guardian.
Where local law sets a higher age for consenting to data processing than 13, that higher age applies and a parent or guardian must consent on your behalf.

13.International use

The site is reachable everywhere; the law is not the same everywhere.

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.

14.Changes to this policy

Revised in place, with the date moving only when the substance does.

This policy is updated when features, providers, laws or practices change, and the date at the top shows the current version.
Where a product is switched off for a deployment, the sections describing it are removed from this page rather than left standing — so what you are reading describes the service as it is running for you.
There is no automated change-notification mechanism. Material changes are made by revising this page.

For privacy questions or requests, use the contact form and select the privacy category, or email contact@motifuse.com directly.

This page is formatted to print as a document.

Questions about this document

Privacy questions, access and deletion requests, and any complaint about how your data is handled all go to the same address, and reach the person who runs the service rather than a queue.

Ask about this policy contact@motifuse.com

Last updated 14 August 2026. Changes are made by revising this page; the date moves only when the substance does.

Keep reading

Every key by name, how the platform is protected, the agreement this sits under, and the rules for content passing through it.