Privacy

API Tool Calls is run by Cowerx. Tools run in your browser when they can.

We note which kind of site sent a visit, such as a search engine. Your browser sends the referring address to our server. Our visit counts keep only its category, not the address.

On this website, the word counter, image compressor, image converter, image resizer, JPG to PDF converter, PDF to JPG converter, barcode generator, password generator, fancy font generator, typing test, spin the wheel, GIF maker, character counter, JSON formatter, PDF merger, screen recorder, voice recorder, mic test, webcam test and invoice generator process their inputs in your browser without uploading those inputs; your text, files and generated passwords stay on your device.

The camera, microphone and screen are used only in the browser and never recorded to our server. Access starts only after you press a button. The invoice generator saves drafts only in localStorage on your device; Clear draft removes them.

The typing test may save best scores on your device in localStorage; it never sends them to API Tool Calls.

The auction organizer saves its list and budget in localStorage on your device. The APA citation generator saves your reference list there. The barcode scanner saves up to 50 recent decoded scans there. Text to speech saves your pronunciation corrections there. These saved items have no automatic expiry. You can remove them in the tool or clear this site’s browser storage.

The QR maker on this site runs in your browser. When an agent calls the MCP QR tool, its text or Wi-Fi details are sent to our server to make the SVG.

Every MCP and API tool call runs on our server and sends its arguments there. This includes tools whose web version runs in your browser. Some web tools also send inputs to our server. These include the résumé check, YouTube transcript tool, public-page tools, proofreader, company facts, recall check and full Data Finder plan. Some home and cost calculators send your entered measurements, observations, choices and prices too.

The résumé check sends your résumé text to our server, writes it to a temporary file for the check and deletes it right after, even if the check fails. The YouTube transcript tool sends the video link and caption language to our server. Our server asks YouTube for the public captions. We don’t keep the captions. MCP tools that use our JavaScript calculators also write their arguments to a temporary server file. That file closes after the calculation or an error.

The Markdown reader, Page Checker, SEO Checker and APA URL lookup send the page address to our server. Our server requests the public page from that website and may follow redirects. SEO Checker also requests robots.txt, a sitemap and some linked pages. Company facts requests the business’s public pages. Those websites receive the requested addresses from our server. The recall check searches our local recall data. Data Finder’s preview runs in your browser. Its full plan sends your use case, geography, volume, resale choice and selected topics to our server.

Run Loop Maker sends your chosen start point, distance, preferences and any stops to our server. Typed place searches also go to our server, with a nearby location when one is available. Address lookups may use OpenStreetMap’s Nominatim. Place searches may use openrouteservice or Photon by Komoot. Routing may use our own route server, FOSSGIS’s Valhalla service or openrouteservice under our key. These services receive the address searches or coordinates needed for the request. Cached address and place-search results expire after 24 hours. They are held in server memory.

Run Loop Maker’s map loads tiles directly from OpenStreetMap. Tile requests reveal the area you are viewing, along with your IP address and browser request information. See the OpenStreetMap Foundation privacy policy. Opening a route in Google Maps or Apple Maps sends its start and waypoints to that provider. The live run-progress calculation stays in your browser.

The APA citation generator sends DOI lookups directly to Crossref and ISBN lookups directly to Open Library. These services receive the identifier you enter and your browser’s request information.

Some browser tools download model files from this site. Translation, subtitle generation, text to speech, image text reading, receipt scanning, image upscaling and background removal process their content in your browser. Model downloads can reveal your chosen language, speech model or voice. The BAH calculator requests a data file for the first three digits of your ZIP code.

Some requests send tool inputs in the query part of the address. Since 10 October 2026, server access logs keep the page address without its query part. Older log lines may still hold it until the server’s log rotation removes them. Key and billing records stay while the key exists. Third parties handle their own records under their policies.

Some tools can use your own OpenRouter key. It goes through our server to OpenRouter for key checks and tool requests. Our server does not save the key. The browser keeps it for this tab in session storage. If you tick Remember on this device, it stays in localStorage until you press Forget key or clear this site’s browser storage. Connecting through OpenRouter also sends connection details to OpenRouter. OpenRouter’s privacy policy covers what it does with the request.

Two tools send text to a language model provider: the proofreader sends the text you give it, and company facts sends the text and URLs of the business pages it reads. With your own OpenRouter key, that text goes to OpenRouter. OpenRouter may pass the request to the model provider it selects. Without a key, it goes to Google’s Gemini API under our key, within a small free daily allowance; Google’s Gemini API terms cover what it does with the request. We don’t keep that text. No other tool sends your text to a model provider.

If you buy an agent key, Stripe handles the payment and your card details; we never see your card number. We keep the key as a one-way hash, your Stripe customer, subscription and checkout IDs, and each key's monthly call count.

For free MCP calls and some web and API calls, we store the caller’s IP address, UTC date and call counts in a local database to enforce limits. Some limits also record the tool name or a shared AI-platform label. Free language-model requests have separate daily call and cost counts. Allowance records with IP addresses, dates and call counts are deleted after 7 days, on the first traffic write of a new UTC day. Daily totals without IP addresses stay. We do not store QR content there.

We count daily visitors, page views, tool calls, key checkouts, and keys sold. For visitor counts, we hash your IP address and browser's User-Agent with a random daily salt. After the UTC date changes, the next traffic-counting operation deletes old salts, visitor hashes and per-visitor engagement rows, keeping totals. A new daily salt prevents these visitor hashes from linking counts across days. Our own counting uses no cookies.

We use Google AdSense on pages other than the YouTube transcript page, barcode scanner and error page. Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites. Google's use of advertising cookies enables it and its partners to serve ads to you based on your visit to this site and/or other sites on the Internet. You may opt out of personalized advertising by visiting Google Ads Settings, or opt out of some third-party vendors' use of cookies for personalized advertising at aboutads.info. See how Google uses information from sites that use its services.

Our pages are served through Cloudflare, which adds its Web Analytics script. Cloudflare says that script sets no cookies and does not track you across sites.

We don't sell your data.

Questions? Email support@cowerx.dev.