Privacy details and data handling notes
Read moreThis section provides additional clarity about privacy on Anku AI Tools: what data may be processed, why it may be processed, and how you can reduce what you share. Many tools are designed to run locally in the browser, including offline writing, image, developer and converter workflows.
Browser-first tools and what that means
Many tools can work directly in your browser. Browser-first tools are helpful because they can reduce the need to upload files or text to a remote server.
Some advanced tasks on tool websites, such as perfect OCR or complex document conversion, can involve more processing than a browser can reliably provide. On this site, the writing interface uses local templates and text analysis for fast drafts.
A good privacy practice is to test with sanitized sample inputs first, then decide whether you want to process full content.
- Prefer browser-first workflows when possible.
- Avoid uploading confidential documents.
- Use minimal examples for testing.
- Verify outputs before publishing or professional use.
Types of data you might see on typical tool sites
Tool sites often process basic technical signals like browser type, device type, and performance metrics. These signals help improve site speed, find broken flows, and prevent abuse.
They may also store preference data (like last-used settings) to improve UX. This is usually done using cookies or local storage.
The goal is to keep these signals minimal and focused on reliability rather than tracking people across the web.
- Performance and diagnostics (aggregate trends)
- Preference saving (optional UI settings)
- Security and abuse prevention (rate limiting)
- Support troubleshooting (when you report an issue)
Your choices and best practices
You control what you submit. The safest approach is to avoid sensitive personal data entirely and to use sample inputs when trying a tool for the first time.
You can also control cookies and site data through browser settings. Clearing site data may reset preferences but can reduce stored state.
If you have questions about a specific page or tool, contact support with the exact tool URL. That helps identify which workflow applies.
- Don’t paste passwords, OTPs, private keys, or confidential files.
- Clear cookies/site data when needed.
- Use the sitemap to browse public pages.
- Contact support with the tool URL for accurate answers.
Public pages note
Tool pages are public and indexable, and they may appear in search results. This is intentional: each tool is built as a dedicated page for a specific intent so people can land directly on the right utility.
If you manage indexing from Search Console, submit /sitemap.xml and monitor queries. Update the most visited tool pages with clearer FAQs and examples based on real searches.