TableJSON
TableJSON

Privacy

Privacy

Last updated: 28 October 2026

TableJSON is operated by Venkata Naidu. This page covers the playground and API at tablejson.com: the PDFs you send, the logs the server writes, the cookies this site does and does not set, and the advertising from Google AdSense. Questions go through the contact page.

Files you upload

When you extract a table or build an invoice workbook, the PDF is sent to the TableJSON server for that request. A multipart upload is written to a temporary file in the server's temp directory by the upload library, then read into memory so the text layer can be parsed. When the response finishes, that library deletes the temp file. TableJSON does not put the PDF, the JSON, or the workbook into a database or a document library. There is no account page where old uploads can be opened later.

A PDF sent as a public URL is downloaded into memory for the request. That path does not write the file out. Private addresses, including localhost, are refused.

If the process is killed in the middle of a request, a temp file can remain until the host clears its temp directory. That is a crash leftover, not a retained copy. Logs can include the time, path, status code, size, IP address, and a short error string. They are not a copy of the PDF. Do not upload a file you are not allowed to process. A bank statement is still sensitive for the seconds it is in flight, which is why the statement guide says so in plain language.

The playground keeps the file in your browser only for the session, so it can show a preview and post the bytes. Closing the tab drops that. Download JSON or the workbook if you want a copy. We do not get that download back.

Accounts, keys, and email

The playground does not need an account or an API key. Direct API calls and Zapier use a key you configure. RapidAPI authenticates through RapidAPI. Keys are secrets. Do not send one by email unless we ask you to rotate it. The contact form lives only on the contact page. It opens your email app and does not post the message to this server.

Cookies

TableJSON itself does not set account cookies, session cookies, or analytics cookies. There is no login and no first-party tracker. The pages do load Google's AdSense script, adsbygoogle.js, for publisher ca-pub-1210860150241703. That script is served by Google and may set or read cookies, including on advertising domains, to deliver and measure ads and to limit how often you see the same one. Those are Google's cookies, not cookies named by this site.

Advertising and Google AdSense

We use Google AdSense to show ads. Google, as a third-party vendor, uses cookies to serve ads based on your visits to this site and other sites on the Internet. The ads you see are chosen and measured by Google under their own rules. We do not sell the contents of uploaded PDFs, and ad targeting is not fed from the tables you extract.

Google's advertising policies and the description of how Google uses data are here:

How to opt out of personalized ads

You can turn off personalized advertising, or manage the cookies behind it, without emailing us. These are Google's and the industry opt-out pages:

Blocking third-party cookies in your browser also stops most of these cookies. An ad may still appear. It just will not be personalized from a profile. The European Interactive Digital Advertising Alliance has a similar page at youronlinechoices.eu if you are in that region.

Other sites

RapidAPI, Zapier, and your email provider are their own services once you leave tablejson.com. Their privacy terms apply there. A link in a guide does not move your PDF to that site.

Contact

Privacy requests go through the contact page. Include the time of the request and the route you called. Do not include the PDF unless we need it to debug.