Motifuse support
How can we help?
Choose the right contact path for product support, account questions, privacy requests, security reports, accessibility feedback and business enquiries.
Stored messages are reviewed directly by Rakesh P R, who operates Motifuse. Choose the closest category and include the relevant tool, page or account details so the enquiry can be handled efficiently.
Six paths
Choose a contact path
Two of these are better served by their own process. The rest use the form below — picking the closest category is what decides the questions it asks.
Product or tool support
A tool that fails, an unexpected result, an upload that will not go through, or a question about how a feature works.
Get product supportAccount and billing
Sign-in problems, invoices, subscriptions, cancellation, or closing an account.
Never include card numbers or passwords.
Account and billingPrivacy and data request
Access, correction, deletion, or any other request about the data held on you.
Make a privacy requestReport a security issue
Suspected vulnerabilities and responsible disclosure. Read the boundaries before testing anything.
Or email security@motifuse.com directly.
Read the disclosure processAccessibility feedback
A keyboard trap, a screen-reader problem, insufficient contrast, or anything else that blocked you.
Share feedbackBusiness or private tools
Business enquiries, and custom tools built for one organisation's workflow.
A private tool has its own request form.
Business enquiries
Often quicker
You may find the answer immediately
These are written already. If one of them covers your question you will have an answer sooner than a reply could arrive — and the form is still right below if it does not.
- FAQAccounts, plans, file processing and privacy, answered.
- PricingLive plan configuration for each premium product.
- ChangelogWhat changed recently, dated.
- SecurityProcessing boundaries, providers and disclosure.
- Privacy PolicyWhat is collected, why, and how long it is kept.
- Tool methodologyHow tools are built, tested and corrected.
Send a message
Tell us what you need
Choose the closest category — it decides what the form asks for and how the message is labelled when it arrives, which is usually the difference between one reply and three.
What to include in your message
The most common reason a reply takes two rounds is a missing detail. The category-specific fields ask for most of these already.
- The tool or product you were using
- The page URL, where one is relevant
- What you were trying to do
- What you expected to happen
- What actually happened
- Any error message, word for word
- Browser, device and operating system
What happens to your message
Only what the submission path actually does.
- Your name, email address, category, subject and message are stored so the enquiry can be answered and so the form can detect duplicate and automated submissions.
- The form is protected by server-side rate limiting, a hidden field automated senders fill in, timing signals, duplicate detection and — where it is configured — Cloudflare Turnstile.
- Your address is not added to any mailing list and messages are not used for marketing.
- No retention period is published here because none is enforced in code; messages are kept while they are relevant, and you can ask for one to be deleted.
- There is no attachment field. Please describe the problem in text rather than sending files.
Before you write
Contact questions
Eight questions that come up when deciding how — and where — to get in touch.
The closest one — the category decides what the form asks you for and how the message is labelled when it arrives, which is what avoids a follow-up asking for details you would happily have given. If nothing fits, choose the general category and describe the situation.
Use product support or the bug category, and include the tool, a small non-sensitive sample input, the result you got, the result you expected, and — most useful of all — the source that supports your expected result. A defect that can be expressed as an input and an expected output becomes a permanent regression test.
Read the disclosure process on the Security page first, then email security@motifuse.com or use the security category on this form. Both reach the same person. Please report before disclosing publicly, and stay inside the stated testing boundaries.
Not through this form — there is no upload field, because a secure attachment workflow with validation, scanning, access control and deletion does not exist here yet. Describe the problem in text, or paste a short non-sensitive sample. Please never send confidential files.
Numbered steps someone else can follow exactly, what you expected, what happened instead, any error message word for word, and your browser and device. A description of the symptom without the steps usually costs one extra exchange before anything can be reproduced.
It is stored so the enquiry can be answered and so the form can detect duplicates and automated submissions, and it is read by Rakesh P R, who operates Motifuse. Your address is not added to any mailing list and nothing is used for marketing. The Privacy Policy is the controlling document.
Choose the privacy category and send the request from the account's own email address, saying what you want — access, correction, deletion, or account closure. Account closure is handled by hand; cancel any active subscription first, because closing an account does not cancel one.
Use the private tool request form rather than this one. It captures scope properly — the workflow, the inputs and the output you need — and you receive a written scope and a one-time quote before any work starts. Requests are free and reviewed by hand.
Still not sure?
Pick the route that fits
Every one of these reaches the same person. For a suspected vulnerability you can also email security@motifuse.com directly.
- Send a general enquiryAnything that does not fit a specific category.Open the form
- Browse the FAQAccounts, plans, processing and privacy, answered already.Read the FAQ
- Report a security concernRead the disclosure boundaries, then report.Disclosure process
- Request a private toolA custom utility built for your workflow.Describe it
Keep reading
Related policies and resources
The documents behind the answers you will get.
- FAQAccounts, plans, file processing, privacy and support, answered.Read more
- SecurityProcessing boundaries, providers and responsible disclosure.Read more
- Privacy PolicyWhat is collected, why, and how long it is kept.Read more
- AccessibilityWhat works today, what does not yet, and how to report a barrier.Read more
- Tool methodologyHow tools are built, validated, tested and corrected.Read more
- ChangelogDated record of material changes across the platform.Read more