No account, no profile, no sign-in
You are not asked to create a password, to confirm an email address, or to choose a username before you edit a cell or export a file. Tabley does not build a customer profile of table makers, because it does not have accounts to attach that profile to. There is no dashboard where past tables would be listed under your name. If a page on the wider web ever asks you for a Tabley password, it is not this product's login, because this product does not have one.
That design removes a common pile of personal data: no password database, no "forgot password" mailbox full of reset links, no list of who logged in from which country. It also removes recovery. Support cannot look up "the budget you made in March" and send it back. The words exist in your browser's storage and in whatever files you downloaded or printed. Please write to the contact address if something about the site itself is wrong. Please do not write expecting a restore of cell text from a server copy. There is not a server copy of the grid.
Because there is no account, there is also no setting inside an account for "delete my data." The way you delete the draft is a browser action: clear the site data for tabley.online, remove the local storage entry, or use a private window that drops storage when it closes. Exported files that you saved into Downloads, a school drive, or an email attachment are outside that step. Deleting the browser draft does not reach into those copies. Keeping them or shredding them is your own file hygiene.
Where the table lives while you edit
The working table is stored with the browser's local storage on the device, under a key the site uses so the same browser can reopen your draft. Local storage is a small cupboard the browser keeps for a particular site. It is not an upload. It does not, by itself, sync through Tabley to your phone if you started on a laptop. A second browser on the same computer, such as moving from one vendor's browser to another, has its own cupboard. A guest profile, a work profile, and a personal profile are different cupboards even when they share a machine.
What you should assume is stored locally is the table you see: title, caption, header mode, cell text, the styling you applied, stripe and border choices, font choices, and the other switches that reconstruct the grid. What you should not assume is a forensic log. The product is not designed as a diary of every keystroke, every export, or every IP address tied to a cell. Undo and redo are part of the editing session's behavior in the page. They are not a history file you can request from the publisher later.
Local storage survives closing a tab in ordinary browser settings. It often survives a restart. It does not survive every cleanup tool, every "reset this browser" command, or every policy on a managed school or office machine that wipes site data at logout. If a network administrator has configured the browser to discard storage, Tabley cannot override that. Export while you still have the grid on screen if the table is something you need tomorrow.
Private or incognito windows are useful when you do not want a lasting draft, and they are a trap when you do. Some of them discard local storage at the end of the session. A roster you built carefully and did not export can vanish when the window closes. The status line in the product is there to remind you that saving is local and that nothing is uploaded. Believe the second half, and do not romanticize the first half into a backup plan.
What on-device export means
When you export PDF, PNG, JPEG, CSV, Excel (.xls), HTML, or Markdown, or when you print, or when you copy tab-separated text, the work happens on the device. The browser builds the file or the clipboard payload from the grid already in memory. Tabley does not receive the cells as the price of giving you that file. There is no conversion queue you join, and no email from the site that attaches your export, because the site does not take the document in order to return it.
This matters if you are handling names, phone numbers, grades, prices that are not public yet, or notes from a meeting. Using the editor does not mean you have submitted that text to the publisher. It does mean the text is on the computer in front of you, in memory and in local storage, and that any other software on that computer with permission to read the browser's site data could, in principle, see what the browser stored. Tabley is not a shield against malware, a shared login, or a coworker who sits down at an unlocked screen. Lock the device as you normally would for other local documents.
After a file exists, privacy depends on what you do with the file. A PDF in a group chat is as widely shared as that chat. An HTML snippet pasted into a blog is public if the blog is public. A CSV imported into a spreadsheet service is then under that service's terms, not under this page. Tabley cannot pull those copies back. Choose the export with the audience in mind. A JPEG of a full contact list is easy to forward and hard to expire. A printout on a clinic desk can be picked up. The format does not add discretion the words themselves do not have.
Import is the reverse direction and it is also local. If you import a CSV file, the browser reads the file you picked so the cells can fill. That selection is not an instruction to upload the CSV to Tabley. Paste from a spreadsheet is similar: the clipboard contents go into the grid in the page. Be aware that the operating system's clipboard may keep what you pasted until something else copies over it. That is ordinary device behavior, not a Tabley library of your pastes.
What the editor is designed not to send
The table maker does not require the cell text to leave the device to perform its job. Styling, stripes, header colors, fonts, padding, borders, titles, and captions are applied in the page. Templates are part of the site you already loaded. They are starting points, not documents you fetch one by one from a personal folder on a server.
You should still understand the difference between "the tool does not upload your table" and "no network request ever happens when you use a website." Loading tabley.online itself is a network request. Your browser asks for the page, the script, the styles, and the help text, and it receives them. A normal server log for a website can include technical details such as an IP address, a time, a browser type, and the URL that was requested. Those are properties of visiting a site, not a copy of your grid. This notice does not claim that web hosting is invisible. It claims that the product is not built to transmit the contents of your cells as the contents of your table.
If that distinction is too fine for the data you have, do not type that data into a browser. Use an offline document for material that must not touch a networked computer at all. Tabley is an ordinary website with a local editor, not an air-gapped appliance. Honesty on that point is more useful than a slogan.
Help pages, including this one, are public text. Searching the site, changing language, and opening features, templates, or tips loads those pages. It does not attach your current grid to the request as a document you are publishing. Do not put secrets into the title of a table and then assume a help page somehow broadcast the title. The help page does not have your title. The local draft does.
Shared machines, families, and classrooms
Local storage is per browser profile, not per human being. If several people use one operating-system account, they share the draft. A family computer, a front desk, and a classroom cart are the cases to plan for. The next person can open the site and see the table you left, including names or grades, until the storage is cleared. There is no logout button that fixes this, because you were never logged in.
A practical routine for shared machines is short. Export the file into the place your workplace or school already uses for that kind of document. Then clear browsing data for tabley.online, or use a private window from the start and export before closing it. Do not leave a contact list on screen while you step away, any more than you would leave a paper roster face up. The about page repeats this for clinics and shops because it is an operational fact, not only a legal sentence.
Children may use the maker for schoolwork. The site does not ask their age, does not open an account for them, and does not build a social profile. A school that wants a data-processing agreement for a student information system is looking at a different category of product. Tabley does not seek student records. If a teacher pastes marks into a grid, the teacher is using a local tool and is responsible for whether that is allowed on that device under school rules. Clearing the browser afterward is part of that responsibility. This paragraph is not a claim that the site is certified for any particular education-privacy statute. It is a description of what the tool does not collect through accounts, because it has none.
Optional advertising, cookies, and ads.txt
The table tool's own job does not depend on advertising cookies. You can edit, print, and export without an account. Publishers of free sites sometimes show ads later so the hosting can be paid for. If Tabley later enables advertising with Google AdSense, the advertising script would be a third-party program loaded with the page. Scripts of that kind can set and read cookies, and can use similar technologies, to count visits, limit how often an ad is shown, and measure or personalize ads under Google's own rules and the choices your browser offers.
That possibility should be stated before it happens, not discovered in a surprise sentence. A future ad script could set cookies even though the editor does not send your table contents to Tabley. Those are different pipes. One pipe is the grid, which stays local to the editing and export path described above. The other pipe would be the ad script's relationship with your browser, which can include cookie identifiers that are about advertising, not about the words in cell B4. Enabling ads would not be a feature that uploads your CSV. It would still be a real change to the page, because a new party, the ad network, would be allowed to run code in the browser while you visit.
The ads.txt partner named for this site is the publisher id ca-pub-9824879170988442. An ads.txt file is a public note that tells ad networks which sellers are authorized to sell advertising on a domain. Naming that id here is a statement of who the authorized publisher partner is, not a statement that a particular ad is on your screen today, and not a statement that your table has been shared with that partner. If an ad script is not present, it cannot set a cookie. If it is added later, it can, and you should assume it might.
You can limit cookies in the browser regardless of what a site prefers. Blocking third-party cookies, using strict tracking prevention, or running an extension will change how any future ad script behaves. Those tools can also occasionally interfere with ordinary web features. Tabley does not require you to accept an advertising cookie in order to unlock export. If a browser prompt appears because an ad script was added, refusing personalized ads should not be the difference between a working table and a broken one. If you ever find that the grid will not export unless a cookie banner is accepted, that would be a defect worth reporting to hello@tabley.online rather than a rule of the product.
Do not paste secrets into the page and then rely on an ad blocker as your only protection. An ad blocker changes advertising code. It is not the mechanism that keeps cell text local. The mechanism that keeps cell text local is that the editor generates files on the device and stores the draft in the browser. Those facts remain the ones to trust or to reject. If you reject them for a given document, keep that document out of the site.
Email you choose to send
The contact form on the contact page does not store your message on a Tabley server. Submitting it opens your email app with a message addressed to hello@tabley.online. What happens next is email, between you and that inbox, under whatever provider you use and whatever provider receives the mail. Your name, your address, and the body you wrote are in that email because you sent them. They are not a hidden upload performed by the table editor, and they are not attached automatically to your grid. The form does not read your cells and append them.
Please do not include a full sensitive table in the email unless you actually need help with those exact words. A bug report is more useful with the browser name, the language, the steps, and a description of the grid size than with a photograph of real students or real patients. If you do attach an export, you are choosing to share that file with the recipient of the mail. The inbox is not a destruction service. Send only what you are willing to have a person read in order to fix a problem.
How long things stick around
A draft sticks around until the browser drops that site's local storage, you clear it, or a new edit replaces it. There is a single working table in that storage, not a gallery of every table you have ever made. Applying a template replaces the grid you were editing, so export first if the old one still matters. The publisher does not keep a timeline of those replacements.
Exported files stick around according to your own folders and inboxes. Tabley does not expire them, because Tabley does not have them. Copies in a school's learning system, a client's email, or a photo roll on a phone follow those systems' retention, which this privacy page does not control.
Server logs for ordinary page loads, if the host keeps them, follow the host's operational practice for security and debugging. This notice does not invent a precise number of days for those logs, because a precise number that the publisher does not actually enforce would be theater. The substantive promise is about table contents: they are not the payload of the product's save or export path.
If the site later enables an ad script, that vendor's cookies last according to the vendor's policy and your browser settings, not according to a sentence we might wish were true. Review cookie settings at the time, and read the network's notice if a banner or a help link is provided. This page will be updated when the product's privacy behavior changes in a way you could not infer from the editor itself.
Changes to this notice, and how to ask a question
Tabley may revise this page when the product changes, when an advertising script is actually added or removed, or when a sentence proves confusing in practice. The current text is the one on tabley.online. A downloaded copy of an old help page will not update itself in your downloads folder. The terms explain that the tool can change or be discontinued. A privacy change of the serious kind would be a change in whether table text is uploaded. That is not how the tool works. If it ever were proposed, the honest place to say so would be this page, in direct language, before you are asked to rely on it.
Questions about privacy can be sent to hello@tabley.online. Useful questions name the page you were on, the browser, and what you expected to happen to a specific kind of data, such as "does import of a CSV upload the file" or "what should a shared lab computer do at the end of class." Those questions can be answered from the design. Requests to recover a table from the publisher's servers cannot be answered from the design, because the servers are not holding it.
If you want the short version in one breath: there is no account, the grid stays in this browser, exports are made on your device, the tool does not send table contents to Tabley, and a future Google AdSense script could still set cookies under the publisher id listed above if the publisher turns advertising on. Use the tool when that bargain fits the data. Use something offline when it does not.