Privacy Policy

1. This policy, the Wix Privacy Policy, and the Tabless terms

Tabless is a Wix Service, and the Wix Privacy Policy applies to it. This policy supplements it: it writes what is specific to Tabless — what the extension reads, who else sees it, and the permissions it asks your browser for — and changes nothing else. Section 13 lists what the Wix Privacy Policy brings with it.

Read them together. Where a matter specific to Tabless is addressed in both, this policy is the more specific and governs for Tabless.

What you may use Tabless for and what you are responsible for are in the Tabless Terms of Service. Where both documents touch your data, this policy governs.

2. What Tabless processes

Page content

After you allow Tabless to read a site, it captures each page’s title and address, and converts the page itself into text — a plain-text rendering of what the page shows, produced inside the tab. The page’s own markup, such as its styles and the scripts that make it work, is not part of that rendering and does not leave your browser. The conversion works from the page’s body, or from the whole document if the page has no body. It includes what the page provides for screen readers — image descriptions, the labels of links and controls, and text kept out of sight for them — and it carries the label of a form field or a text editor, never what is typed into it. Alongside it, Tabless collects the structured description a page publishes about itself — the standard machine-readable block many sites include so that search engines can describe them, which is data rather than page logic. It is read from anywhere in the document, including parts of the page you do not see, and rendered as text in the same capture. Sites use it to state things like a product and its price, an article and its author, or a review and who wrote it, so it can carry personal data that is not visible on the page. The rendering leaves out content the page hides from you, which it detects from the page’s styling and accessibility attributes. Treat that as a reduction, not a guarantee, and not a sensitive-data filter: Tabless does not identify or redact personal information, and anything the page displays to you can be captured — including information the page shows only because you are signed in. Long pages are shortened to a size limit, so a capture is not necessarily a complete record of the page. A tab you wove earlier can reread its source pages as section 3 describes. When you weave a tab, or rebuild one, that text rendering is what reaches our service, and our service passes it to the AI provider. The service can also send samples of extracted table rows to the AI provider to check that the woven tab reads the intended data. A row Tabless reads for a table can also carry the address of a link in it — usually the row’s own page, such as a listing’s — taken from the link itself rather than from the text the page shows. Tabless reads only web addresses this way, and leaves out any sign-in details written into one. Our service receives each address whole. The AI provider is shown it without its query string and fragment — the parts after a “?” or a “#”, where a site may put a session or tracking identifier.

Your list of open tabs

When you are signed in, the panel’s home screen lists your open web tabs so you can pick which ones a new table should use: each one’s title, site, window and whether Tabless may already read that site. That list stays on your device; making it reads no page and asks for no site access. While it works on your instruction, Tabless sends our service a list of open web tabs: each one’s title and address, a number Chrome gives it, whether it is the active tab in its window and whether it is asleep, in the order you last used them. If you picked tabs for the first build of a table, that list holds only the tabs you picked, and the build reads no other tab; if you picked none, and whenever you change a table later, it holds all your open web tabs across browser windows. The list is sent before any page is read, without a question first, and our service passes the titles, addresses, numbers and active tabs on to the AI provider, so that the model can tell which tabs your instruction is about. It carries no page contents and no time of use beyond that order. Tabless then asks you before it reads a page, as section 6 describes, and reads page contents only on sites you have allowed.

What you type

The instruction you give Tabless, and anything else you type or choose in its panel while it works: your answer to a question it asks you, a line you add while it is weaving, and the changes you ask for to its plan or to a tab you wove earlier. When you choose “This is wrong” on a value or “Something’s wrong” under a table, Tabless writes that request for you as a change, from the table’s saved description only — the column’s name, the row’s position on its page and that page’s site, or the table’s name — and sends it like a change you typed. It never puts a value from the table or text from a page into that line, though the change it starts can read pages again, as any change can. All of it is sent to our service and the AI provider as part of the run, and section 5 says how long it is kept. Each request also carries the conversation so far in the panel — what you typed earlier and what Tabless replied — so that a follow-up such as “only the second one” can be understood. That is at most the 40 most recent turns and 32,000 characters, and it is sent again with every request in the same conversation, including a line that only talks to Tabless and asks for no tab. When you choose Continue the chat in History, the table’s saved conversation returns to the panel. Its earlier messages and replies are sent again with your next request to our service and the AI provider, within the same 40-turn and 32,000-character limits.

Your Wix sign-in

Tabless asks you to sign in with your Wix account. It opens Wix’s own login page in an ordinary browser tab; the extension does not see what you type there, and it never holds a Wix password. Because it is an ordinary tab rather than a window of its own, it uses the same browser session as the rest of your browsing: if you are already signed in to Wix in this browser you may not be asked again, and signing in to Tabless signs you in to Wix here too. When Tabless’ panel opens and you are not signed in to Tabless, it first tries to sign you in without a click: it opens the same Wix page in a background tab, which closes when the sign-in completes, when Wix shows its login form, or after 15 seconds at most. If you are signed in to Wix in this browser, that signs you in to Tabless without asking you; if you are not, nothing is entered and the panel shows its sign-in button. If it finds no Wix session, or its try does not complete, it does not try again for up to 10 minutes. The one exception, after a try that found no Wix session: while its panel is open and waiting for you to sign in, a Tabless web page you have signed in to can tell it that you are signed in, and it then tries once more, as section 6 describes. It never tries after you signed out of Tabless yourself, until you sign in again. When you have signed in, our service issues Tabless a sign-in token of its own, which the extension keeps in Chrome’s local extension storage and presents on each later request so that our service knows whose request it is. The sealed refresh credential is sent only to our service; the server uses the Wix token inside it to renew or revoke your grant at Wix. That token is short-lived. Beside it the extension keeps one longer-lived credential whose only purpose is to obtain a fresh token without sending you back to a login page. It contains a Wix refresh token sealed so that only our service can open it. It lasts 32 hours and is replaced every time it is used. The signed claim itself cannot be withdrawn before it expires; revoking the Wix grant it carries prevents it from obtaining usable Wix access. Signing in grants Tabless session-bound access to call Wix services as you. The grant depends on your Wix session and can end when you sign out of Wix, when the account is blocked or deleted, or when Tabless revokes it. Both credentials sit in the extension’s own storage, where no website you visit can read them. Requests from the extension to our service carry that token and no cookie. Tabless sends no cookie to our service and has no permission to read cookies. Picture requests described in section 3 may carry cookies for their host according to your browser’s rules. A page Tabless opens or reloads for you, as section 3 describes, is loaded by your browser with that site’s own cookies, as any tab is. Any cookies set while you sign in belong to Wix’s login page rather than to the extension, and are covered by the Wix Cookie Policy, referred to in section 13. Signing out of Tabless clears its local credentials and asks our service to revoke the Wix grant. It does not sign you out of wix.com. If revocation fails, clearing the local credentials does not prove the grant was revoked. Signing out of Wix ends the session the grant depends on. Uninstalling clears the local copy but does not itself revoke the grant.

Your Wix account

Extension sign-in uses your Wix user and account identifiers to authenticate your requests and check account allowance. They are carried in the extension’s sign-in credentials, together with the sealed refresh token described above. Extension sign-in does not request your profile or email, and those identifiers are not sent to the AI provider. The account website separately reads your email and available profile name and picture to show your account, and Wix manages its session and billing records.

Access logs

We keep technical records of requests to our service, to assess and improve product quality, to find what fails, and to measure how much each account uses Tabless. For each step of a run they record the run it belongs to, by a random run identifier; a pseudonym of your Wix account, which is a code our service derives from your account identifier with a key only our service holds, so the record does not show the identifier itself; when it happened; whether it succeeded, how it ended and, if it failed, why, in our own words; and how long each part of it took, including how long Tabless waited for you to answer an approval; and how much of the AI model the step used, counted in tokens, and which model it was. For each model step they also record whether your AI allowance let it run and, if not, why — the allowance was used up, you were signed out, the check could not be made, or the service was misconfigured — with the allowance’s limit and when it resets when those are available. Usage-report lines carry the usage key, token count and whether reporting the usage to Wix succeeded. Each time you sign in, they record that you did, with that pseudonym. When you run a row action or an approved record update, the extension tells our service that it started and how it ended — confirmed, possibly sent, or failed — and which kind of action it was, and they record that with the pseudonym, so that we can count how actions are used and how often they work. That event carries no row, page, site, text or run identifier. Each report sent to our service is recorded, whether or not it could be delivered, with its source, its run and request identifiers and, for a signed-in report, the pseudonym, never with its note. Each time the extension reads your plan — when its panel opens, when it regains focus, when it becomes visible again, when you open its account menu, when you sign in and when a build ends — they record your plan, your subscription’s status (active, pending or unpaid), how much of the allowance is used, its limit and when it resets. The logging platform adds technical details of the request to each record, such as the network address it came from and the browser that sent it. When our monitoring is switched on, it also records each run, and each tool the model asks Tabless to use, by the same run identifier, with the tool’s name and roughly how long it took, so that we can measure how often they succeed. None of these records includes page content, what you typed or the model’s reply. Section 5 says how long each is kept. The record described next is a separate thing, written only if you have turned on sharing.

What you share, if you turn sharing on

Tabless has one setting, called “Help improve Tabless”, and it is off until you turn it on. Tabless reads it when a run begins, and the run keeps that answer until it ends, so switching it during a run changes the next run rather than that one. In a run that begins while it is on, each step writes one record of what the model said and what it asked Tabless to do: the model’s own replies, in full, and the name and arguments of each call it made — for instance which part of a page it decided the rows of a table were in, or which columns it chose to read. The page Tabless captured is never part of that record, and neither is anything you typed. That is a narrower protection than it sounds, and we would rather say so than let the setting sound safer than it is: the model’s reply is its own account of the page it has just read, so it can quote or describe what that page showed you — including what it showed only because you are signed in — and the arguments the model chooses are drawn from that same page and from what you typed. Treat a shared record as capable of containing anything the run was about. The record carries no account identifier and nothing else that names you. It does share one thing with the access logs described above: the random identifier of the run it came from. Those logs carry the pseudonym of your Wix account, and the network address and browser each request came from, so while both are kept a shared record could be matched to them, and through the pseudonym to your account; we do not do that. Section 5 says how long it is kept, section 8 explains how it sits with the Chrome Web Store’s Limited Use terms, section 9 gives the legal basis, and section 10 says what turning the setting off does and does not do.

Written columns

If you allow a written column to be filled, Tabless sends the row key and the cells named as inputs to that column to our service and the AI provider to write text, such as a message draft. This approval is kept for that table and column definition until you revoke it; changing the definition asks again. New rows can be filled under the same approval. Your own device-local columns are not included in these inputs.

Preparing a record update

Preparing a generic record-update recipe sends the read identifier, your column name and the selected source-field label to our service and the AI provider. It does not send the contents of your own columns. The extension resolves those values locally when preparing and applying an approved update. Page content inspected during recipe preparation still follows the build disclosure above.

Linking an inbox

You can link one of your own columns in a table to an inbox — a page of your messages that is already open, on a site Tabless may already read — so that Tabless can propose “Replied” for a record when that person answers you. Linking starts a build that reads that page as any build does, so what it shows, including the messages, reaches our service and the AI provider as Page content above describes. The request names the table’s read and your column only by their labels — and, when you link the inbox again, the inbox’s own read and the table’s profile column — and never carries your own column values. The model works out which parts of the page are the messages, who wrote each one, when, and in which direction, and reads your own profile address on that site off the page. The table’s saved description keeps those labels and that address, and is sent again when you later change the table, like any saved description. After that, Tabless reads the page again when you choose Refresh inbox or link it again, and — only if you turn on automatic refresh for that inbox — when the tab’s title changes or at a record check described in section 3. Each is one read of that open tab in your browser, which uses no AI and sends nothing to our service. It does not click, scroll or open a tab. When a message from exactly a record’s profile follows the last message you sent, Tabless proposes Replied for that record. Keep Replied writes only your own cell, and Reject drops the proposal. If you turn on automatic keeping for that column, Tabless writes Replied into your own cell without asking you, and you can change it back. Either way it writes only your own cells, and it never types into, submits or sends anything on the inbox page or any other site. You can turn automatic refresh and automatic keeping off for each inbox at any time. Section 3 says what it keeps on your device.

Building like an earlier table

When you choose to build like an earlier table, Tabless sends its title and page-column names with your request to our service and the AI provider. It does not send that earlier table’s rows, cell values or source addresses, or the names or contents of your own columns.

AI allowance and subscriptions

Tabless calls Wix Premium services as you, using the account grant described above. Before each model step, it checks your account’s remaining AI allowance. It reports the tokens used under a build-and-step usage key, including usage from a step that fails. Wix receives the account identity, Tabless feature name, usage key and token counts, not the prompt, page content, tab list or model reply through these calls. To show your plan in the extension’s account menu, our service also reads from Wix, as you, your Tabless Premium subscription and how much of your allowance is used, its limit and when it resets; the extension keeps the last answer until you sign out or close the browser. A step can spend more than the allowance remaining when it started; later steps check the allowance again. Wix also manages subscriptions, payment and billing records when you use those features.

Reports

Voluntary Help reports, sent through Help → Report, and the Report button on a failure in the panel, send the Tabless team what you write, up to 3,000 characters, with the extension’s version and build identifier. A report about a failed build, change or refresh also carries the failure’s code and, when a browser tool failed, that tool’s error code, whether it was a build, a revision or a refresh, when it happened, and the identifiers of that run, its step and its request, which the form shows you before you send it. If you choose “You may contact me”, your Wix user ID is included so the team can reach you; otherwise it is not. Tabless also sends automatic technical reports when a build, a change or a refresh fails in a way it did not expect, without asking you: the failure’s code and, when a browser tool failed, that tool’s error code, the operation and its time, the extension’s version and build identifier, and the run, step and request identifiers. It attempts a report for the same failure only once in 24 hours and at most five automatic reports an hour, keeping a local record of attempts before sending so failed or uncertain delivery does not cause repeats. An automatic report carries no note and no contact choice. Automatic reports are on until you turn off Send failure reports in the extension’s account menu, which stops them from the next failure. Page content, prompts, model replies, table values and sites are not included automatically, and no file or screenshot is attached; a report holds such things only if you write them into your note. Our service adds the pseudonym of your Wix account described under Access logs, and delivers the report to a private channel in the Tabless team’s internal support tool, where the team reads it to find and fix what failed, and may use its run identifier to look up that run’s access logs.

3. What Tabless does not process

• No profile of you. Tabless needs a Wix account. It uses the account to know whose request this is and, through the pseudonym in the access logs described in section 2, to count how much each account uses Tabless. We do not build a profile of you, and we do not use what Tabless reads to decide what to show or sell you.
• No advertising or cross-site tracking in the extension. The extension uses no ad identifiers and no third-party crash-reporting or analytics service, and loads no third-party fonts. Its own failure reports go to our service, as section 2 describes under Reports. Tables can show pictures found on source pages: your browser requests each picture directly from its original host when it is displayed, including as you scroll, without a page referrer. The host receives your network address and ordinary browser request information, and may receive cookies for that host, subject to your browser’s cookie rules. Tabless does not proxy or re-encode the picture bytes through our service or the AI provider. If a build extracts a picture-address column while checking a table, that address can reach our service; sample addresses shown to the AI provider omit their query string and fragment, as with links in section 2. It does open and reload pages on sites you have allowed, as “Reading a woven tab’s sources” below describes, and your browser loads those as it would any tab you open, with your own cookies for that site. We keep the technical access logs described in section 2 for product quality.
• Sign-in storage. The extension keeps an authentication token in Chrome’s local extension storage to authenticate requests to our service. This token is stored as extension data, not as a cookie. Uninstalling the extension removes that local copy. This storage is separate from any cookies used during Wix sign-in.
• Your browsing history. Tabless does not read it, and asks for no permission to. It can see the tabs you have open now — that is what Chrome is describing when it warns about reading your browsing history, and section 6 explains why the two are not the same thing — but the record of the pages you visited in the past is not available to it at all.
• No access to your bookmarks, downloads, saved passwords or saved autofill data through their browser APIs. Tabless does not record keystrokes on the pages you visit, and it does not continuously watch where you browse. These limits do not exclude sensitive information displayed by a page you allow Tabless to read: that information can be captured and sent for processing as section 2 describes.
• Reading a woven tab’s sources. When you open a tab you wove earlier, its tables automatically read current data from their source pages, without a new instruction. If a source page has been closed, Tabless reopens it in a background tab — but only on a site you have already allowed; on any other, the woven tab asks you to allow the site first — and checks whether it requires sign-in. Coming back to the woven tab or interacting with it can trigger the same checks, and refreshing a table reads its source again. A refresh asks no AI model; if it brings new rows into a written column you allowed, those rows’ inputs are sent to fill it, as Written columns in section 2 describes. If Chrome has put a tab to sleep to save memory, Tabless reloads it before reading it, whichever kind of read it is. Apart from the written-column fill just described, these reads of a woven tab’s sources happen within your browser and do not send the data to our service or AI provider. Rebuilding a woven tab by asking for a change to it sends the change you type, together with the saved description of that tab — its title, the addresses of its source pages, which parts of them it reads and how it filters and sorts them — to our service and AI provider, and can involve reading page content again. When you press a value in a table to see where it came from, Tabless reads that one cell again from its page — only in a tab that is already open, on a site you have already allowed — and shows it to you; it opens no tab, and what it reads is not stored or sent anywhere. You can also turn on record checks for a table with “Check every 15 minutes”. While that table’s tab stays open, Tabless rereads its source pages every 15 minutes, only from tabs that are already open and only on sites you have already allowed; a check itself opens no page, asks for no site access, uses no AI and changes nothing on any site (on a table with an automation turned on, a change it finds can start that automation, as section 7 describes), and what it reads stays on your device, except that the open table shows the rows a check read: if that brings new rows into a written column you allowed, those rows’ inputs are sent to our service and the AI provider to fill it, as Written columns in section 2 describes. If you also watch that table, a check that finds a change you chose to hear about shows the notification described below. Checks stop when the table’s last tab closes, when you remove access to one of its sites, when you choose Stop checks, or when you clear the extension’s data. On a linked inbox, Refresh inbox, or automatic refresh if you turned it on, reads that one open tab again, as section 2 describes. Apart from that, Tabless does not continuously monitor your browsing.
• What Tabless stores on your device. Tabless automatically saves each tab it weaves in your browser’s storage, including its layout and controls, source page addresses, every line you typed or chose in the conversation that produced it — your instruction, your answers to its questions, lines you added while it was weaving and each change you asked for — its title, and when it was saved or updated. For the current browsing session it keeps the conversation in the panel — what you typed, the model’s replies, and the answers to its questions — together with the rows read the last time you refreshed a woven tab, the plan or question it is waiting on you for, any request to read a site that is waiting on your answer or that you have said no to, and a note of any text on a page that tried to give the model instructions, with an excerpt of that text; this session copy is cleared when you close the browser. It also keeps the two sign-in credentials described in section 2, whether you have turned on sharing, a few settings such as your colour theme, and timing measurements of its own operations, which include the titles of the tabs it wove and are kept until you uninstall. Tabless also has a diagnostic recorder, which is off unless you switch it on yourself: while it is on, it records each tab it weaves — what you typed, the full text of every page it read for that tab, and what our service sent back — and keeps those records in your browser’s storage until you clear them or uninstall, even after you switch it off. You can copy a record out yourself; nothing it holds is sent anywhere. What leaves your device is only what sections 2 and 4 describe. The copies stored by the extension on your device are removed when you uninstall; this does not delete records already held by our service.
• A table’s conversation. When a run on a table settles, Tabless also keeps the newest 200 entries of its conversation with that table on your device: your messages, Tabless’s replies and its folded work rows. This copy stays after you close the browser, so you can continue it from History. It is deleted with the table or when you clear the extension’s data, and never leaves your device on its own. It holds no separate copy of the pages read beyond what a reply may quote. Continuing it sends the earlier messages and replies again as section 2 describes.
• Request logs and separate reports. For a request to build or change a table, by default our service writes neither your instruction nor any other content you type for that request, nor the page it read, nor the model’s reply to any log, and keeps no record of that content once your request has finished. The exception is the setting described in section 2: in a run that begins with it on, the model’s replies and the arguments it chose are written to our logs, one record per step of that run. The page Tabless captured and what you typed are never written to a log in either case. Technical access logs are separate again, and are retained for 30 days for product quality, as section 5 explains. Voluntary Help reports are separate: what you write in the note is delivered to the team through the internal support tool. Automatic technical reports carry failure details without a note. Our service’s own report log holds its source and run and request identifiers, never your note. Section 2 describes those flows.

Additional device storage. Tabless keeps row drafts, sent text, action status and timestamps, your own column values and earlier values, source record snapshots and pairings, and checked-update attempts including the record address, field, before and after values and outcome. You can also fill your own columns by pasting CSV or TSV text into a table. Tabless matches each pasted row to a record the table already read and shows you the result before anything is saved; that preview is held only in the extension’s memory and is gone when you apply or cancel it, preview again, delete the table or the extension restarts. What you apply is saved as your own column values, exactly as if you had typed them, and nothing you paste is sent to our service or the AI provider. Row state is removed when its table is deleted; it is not an automatically expiring record. It also keeps per-site action limits and action counts, recipes needing repair, written-column approvals, watched-table settings and change baselines, record-check settings with the rows each check last read, and which of a table’s reads you confirmed look right. For a linked inbox it keeps, per inbox, up to 1,000 messages it has seen — each one’s identifier, the profile and author addresses, whether you sent or received it, and its time, but no message text — together with the proposals it made (the record and its name, the value before and after, the two messages behind it, and whether you kept or rejected it) and the conversations it could not attribute, with the reason. These stay until the table is deleted, you clear the extension’s data or you uninstall. It keeps none of the inbox page’s rows and no message text. During a browser session it keeps action progress, watch progress and the sites most recently read. Watching a table rereads it when one of its source pages changes its title and, if record checks are on for it, at each check. You choose for each watched table whether new rows notify you and which columns’ changes do. A notification is made on your device from the table’s own rows. It can show the table title, a row name and changed column name with up to 60 characters of the value it now holds, for example “Dana Levi: Status → Rejected”, a new row’s name, or how many rows changed or were added. Chrome shows it through your operating system’s notifications, which may keep it under their own settings; nothing about it is sent to our service or the AI provider. These records stay on the device except for the specific transmissions in sections 2 and 4.

Copying, downloading and printing a table. When you choose to copy a table, download it as CSV or XLSX, or print it, Tabless puts the table’s values — what it read, saved drafts and your own column values — on your clipboard, in a file your browser saves where you choose, or in your browser’s print dialog. It happens on your device, nothing is sent to our service or the AI provider, and Tabless keeps no extra copy; what happens to the copy afterwards is up to you and the place you put it.

4. Who else sees it

Producing your result requires an AI model, and we do not run one ourselves. The page content, the list of your open tabs, what you type, the conversation so far and, when you change a woven tab, its saved description travel over an encrypted connection to our service, and from there over an encrypted connection to Fireworks AI, Inc. ("Fireworks"), a company in the United States that runs the model on our behalf.

Fireworks acts as our processor, under its Data Processing Addendum, and may use what we send it only to return the result to us. It is contractually barred from using that data to train, fine-tune or otherwise improve any shared or foundation model, from selling it, and from sharing it for advertising. Section 5 explains its retention policy, including temporary prompt caching and service metadata.

To run the model, Fireworks in turn relies on its own cloud and GPU infrastructure providers. It publishes the current list at its trust centre, and is required to hold each of them to protections no weaker than its own.

The other recipients described here are Wix services for sign-in, allowance and billing, picture hosts contacted by your browser, sites receiving actions you approve, and the Tabless team’s internal support tool, which carries the reports described in section 2 to the team. We do not sell your data. We may disclose data where the law requires it, or where it is necessary to protect the rights, safety or security of our users or of the Service.

Because Fireworks operates in the United States, data reaching it is transferred there. That transfer runs on the European Commission’s Standard Contractual Clauses (Module Two, controller to processor), together with the UK Addendum and the Swiss Addendum, which form part of the Data Processing Addendum linked above.

The written-column inputs and recipe labels, a linked inbox’s labels and your profile address on that site, and the earlier table’s title and page-column names described in section 2, also reach our service and Fireworks. Picture hosts receive the browser requests described in section 3. A site where you run an action receives the submitted text or values under that site’s own terms and privacy policy.

5. How long it is kept

On our service, page content, the list of your open tabs, what you type in a table request — including the earlier lines of yours that a request carries again — and a woven tab’s saved description exist only for as long as it takes to answer you. They are held in memory while your request runs and are discarded when it finishes; they are not written to a database or to a file, and they are not written to a log. That last part holds whether or not you have turned on sharing: the setting in section 2 never covers the captured page or what you typed. A request also carries the model’s earlier replies. That copy is not logged either. A reply from a run that began with sharing on was already kept once, when it was given, as section 2 describes; a reply from a run that began with sharing off was never kept, even if you turned sharing on before that run ended. The woven tabs, instructions and conversation stored in your browser are described in section 3. Voluntary Help reports are separate: their notes are delivered and retained as described below.

We have a zero data retention (ZDR) arrangement with Fireworks for our requests: prompts and generated responses are not logged or written to persistent storage. Fireworks’ published Zero Data Retention policy explains that content is held in memory during inference; when prompt caching is active, some prompt data can remain in memory for several minutes beyond the request. Fireworks also logs service metadata, such as token counts, to deliver its service. Zero data retention therefore does not mean that all data disappears immediately when a request ends.

We keep access logs for 30 days. Report-delivery metadata — the report’s source and run and request identifiers and, for a signed-in report, the pseudonym of your Wix account, without its note — is written to the same technical logging system and follows the same 30-day platform retention. We use these technical records to assess and improve product quality and to measure how much each account uses Tabless. They do not contain page content, what you typed or the model’s reply. That period is set by the logging platform rather than by our service: a record becomes due for deletion on the day boundary 30 days after it is written, and the platform removes it as part of its routine maintenance rather than at a guaranteed instant. The monitoring records described in section 2 are kept for 30 days, a period our monitoring platform sets, and hold no content either.

Our code does not delete a report once it is delivered: it stays in the Tabless team’s internal support tool for as long as that workspace keeps messages, a period this policy does not set. The extension’s local automatic-report ledger records attempt times and failure fingerprints. On the next automatic-report attempt, entries from the last 24 hours are used to enforce the limits and older entries are removed when the ledger is written again; it is not a timer that deletes each entry when it turns 24 hours old.

If you turn on sharing, each shared run writes the record described in section 2 to our logging system, as its own kind of entry, separate from the access logs above. We keep it for 30 days, which is the same period the extension tells you about when you turn sharing on. That period is set by the logging platform rather than by our service: the record becomes due for deletion on the day boundary 30 days after it is written, and the platform removes it as part of its routine maintenance rather than at a guaranteed instant. Nothing in our code removes an individual record before then, and nothing in our code can remove one early; section 10 explains what that means for you.

Our service keeps no account record of its own: it learns whose request this is from your sign-in token each time, and keeps no balance or profile for your account; records associated with a run can include the access logs, monitoring records and report-delivery metadata described in section 2, and a shared record if you enabled sharing; the access logs identify your account only by the pseudonym section 2 describes. Your Wix account itself, and how long Wix keeps it, are covered by the Wix Privacy Policy, as section 13 says.

6. The browser permissions Tabless asks for

Chrome shows you the permissions an extension requests before you install it. These are the ones Tabless asks for, and what each is actually used for. Some it asks for at install; the rest it asks for later, in Chrome’s own dialog, at the moment it would first use them — those are marked below.

Read your browsing activity

To read the titles and addresses of your open tabs — the list section 2 describes, which is sent to our service and AI provider — and the title and address of each tab Tabless reads, opens or checks. Chrome describes this permission as reading your browsing history; what Tabless uses it for is the tabs you have open now. It is the only reason that warning appears: Tabless does not ask for the record of pages you visited in the past, as section 3 says.

Run scripts on pages

Tabless adds nothing to the pages you browse, and runs nothing on a page until you allow its site. The first time it reads a page, Tabless places its page reader into that tab, and that reader is what converts the page to text as section 2 describes. The reader then stays in the tab, idle, until the tab is closed or loads another page: it shows nothing, watches nothing, and responds when Tabless asks it to read the page or run the approved action steps described in section 7. Tabless controls live in the extension’s own side panel and pages, not on your pages. A tab you wove earlier can reread its source pages as section 3 describes.

Access to a site — asked for one site at a time

Tabless does not hold access to the websites you visit. It asks for one site when you first let it read a page there: you allow it in Tabless’ panel, and Chrome then asks you in its own dialog. One approval covers every page at that address — the same host name, such as mail.example.com, though not its other subdomains — not just the tab it came from. That approval is Chrome’s, and it lasts until you remove it at chrome://extensions → Tabless → Site access. Until then Tabless reads pages on that site without asking you again, whether for a new instruction or for a woven tab rereading and reopening its sources. If you say no instead, Tabless does not ask about that site again for the rest of that request. Its reach at any moment is the set of sites you have allowed. It has to work this way round because the sites are yours, not ours: the systems a person points Tabless at are their own stack, discovered when they name them, so no list we could ship in advance would fit anybody. Chrome’s narrower alternative — access to whichever tab is in front of you, for as long as you are looking at it — cannot carry a product whose whole job is the tabs that are *not* in front of you, and whose woven tabs reread several sites when you open them with no click to hang a grant on. The one site Tabless always has access to is its own service, which is where your instructions are answered.

Pages that may send a message to Tabless

This one is not a permission at all, and it points the other way: it admits Tabless’ sign-in landing page at https://www.wix.com/_api/tabless/oauth/land, for the sign-in handoff, and three pages of Tabless’ web app: https://app.tabless.ai/welcome, https://app.tabless.ai/plan and https://app.tabless.ai/account. Each of the three can tell the extension that you have signed in there, so that a panel waiting for you to sign in can try the sign-in section 2 describes, and the account page can also ask it for the browser-data wipe. The signed-in message carries no token, cookie or account data, and the extension’s answer tells the page nothing. It grants Tabless no access to other sites, and Tabless checks what arrives on its merits rather than trusting it for having come from there. Chrome shows no warning for it.

Show Tabless in Chrome’s side panel

Tabless lives in Chrome’s side panel, which is what the toolbar button opens, and which is where it asks you the questions in section 2. Chrome shows no warning for this one and it reaches nothing outside the extension.

Store data in the browser

To keep, in the extension’s own storage, the two sign-in credentials described in section 2, whether you have turned on sharing, settings, action limits and counts, written-column approvals, watch and record-check settings, and a short record of automatic failure-report attempts, so it can limit them — and, for the current browsing session only, the conversation in the panel and the rows of the last refresh, the plan or question waiting on you, notes of page text that tried to instruct the model, and the requests to read a site that are waiting on your answer or that you have said no to, and when a sign-in try without a click last did not sign you in. The tabs you have woven, their row state and linked-inbox records, checked-write records, Tabless’ timing measurements and the diagnostic recorder’s records are kept in a database the browser gives every extension, which needs no permission. Chrome does not show you a warning for this one at install time, so it is listed here: Tabless asks for it, and section 3 says what all of it holds.

Keep its database from being cleared

The database described in the previous entry needs no permission to use, but without one Chrome treats it as something it may throw away: when your disk runs low, Chrome can delete it, and every tab you have woven goes with it, with no warning and no way to get it back. This permission tells Chrome not to, and lifts the limit Chrome otherwise puts on how much that database may hold. It adds no new kind of data and no new use for it: what that database may hold more of is the same woven tabs, row state, checked-write records, timing measurements and diagnostic records, kept for as long as section 3 says and removed when you uninstall. It sends nothing anywhere. Chrome shows no warning for this one either.

Manage tab groups — tabGroups

To put a woven table’s eligible source tabs in a Chrome tab group named after the table. Tabless looks for that group by title in the table’s window and does not send group information to our service or the AI provider. Chrome warns that it can view and manage your tab groups.

Display notifications — notifications

To notify you when a table you chose to watch changes, whether a reread found the change, which a change in its source page’s title starts, or a record check did. You choose for each table whether new rows and which columns’ changes notify you. A notification may show the table title, a row name and a column name with up to 60 characters of the value it now holds, a new row’s name, or how many rows changed or were added. Clicking it opens the table. Chrome warns that the extension can display notifications.

Run record checks — alarms (asked for when you first use it)

To time record checks. Tabless asks for this permission, in Chrome’s own dialog if Chrome shows one, only when you first choose “Check every 15 minutes” on a table; if you refuse, checks stay off. It sets one timer per table with checks on, every 15 minutes, and removes it when the checks stop. When that table is also watched, a check that finds a change you chose to hear about shows the notification described above. The timer sends nothing anywhere. It adds no warning at install.

7. Pages to think twice about

Tabless reads through your logged-in session, so it can see whatever you can see: your bank, your medical records, your email, your employer’s internal systems. Page content read to weave or rebuild a tab leaves your browser and reaches our service and Fireworks. A woven tab can also reread its source pages locally when you open or use it, as section 3 explains. Linking an inbox is a build read: the messages the page shows when you link it reach our service and Fireworks.

Email and messaging pages hold other people’s messages as well as yours. If you build a table from one or link it as an inbox, the messages it shows reach our service and Fireworks as section 2 describes; refreshing it afterwards, by hand or automatically, is read in your browser and sends them nowhere. Tabless asks you to confirm before it first reads an email or messaging site, and automations do not act on email or messaging sites.

A row button can run saved steps on the row’s page in your browser, including clicking, typing and submitting a form or message. It runs after you click the row button or confirm a batch whose rows and text you reviewed. A batch runs rows one at a time; daily limits for each site and action kind restrict how many run. These clicks replay saved steps without an AI call at click time. The receiving site processes the submitted text or values using your signed-in session. Review the destination and text before you act, and do not use Tabless to access or share content you are not entitled to use.

Automations. You can also set up an automation: a rule that, when a watched table finds a change you chose, runs a saved action on a site you have allowed, without asking you each time. Before it is saved, Tabless shows you the whole rule — the change that starts it, the site and page it acts on, the action and the text or values it will submit — and you confirm it; changing the rule asks you to confirm it again. Its first three runs still ask for your OK, and it runs without asking only after them. It runs one row at a time, within the daily limits for each site and action kind, and only while your browser and the table’s tab are open. Every run is recorded in a run log in the extension that you can read, and one switch pauses every automation at once. An automation stops if its saved steps no longer match the page, if you remove access to the site, or if you pause or delete it. An automation submits only values you set in the rule, values read from pages, or a written-column value you have already kept for that row; it never submits text the AI wrote after you confirmed the rule. Automations do not send messages to people, make payments, send money, delete records or act on the pages listed above, including email and messaging sites. An automation sends the same values to the receiving site that the same action would if you clicked it.

While building an action, Tabless may ask separately to try it on a page. Approval is for that build, tab and site. A try may open controls, such as a message dialog, but does not type or submit. Preparing a checked record update reads the current field value locally and shows the old and proposed values for review. Approval is tied to that update; the extension checks the page again before applying it and reads it back to check the outcome. Undo requires a separate review and approval, and can be refused if the record has changed.

8. Chrome Web Store Limited Use

Tabless’ use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Specifically: we use that data only to provide and improve the single user-facing feature Tabless exists for; we do not transfer it except as section 4 describes; we do not use it for advertising or for creditworthiness or lending purposes; and we do not allow humans to read it, except with your consent, for security purposes, to comply with applicable law, or where the data has been aggregated and de-identified.

Transcript sharing and voluntary Help reports are separate flows that rely on your consent for human reading. Sharing is off until you turn it on and covers the model’s replies and calls, not the captured page or your instruction, although those replies can quote page content. Help reports deliver the note you choose to send; it can include page or prompt text if you put that in it. Automatic technical reports are separate again: they contain failure details without a note, captured page content, prompts or model replies. We use and read those technical details for service diagnostics under the legitimate interests described in section 9, rather than treating them as a request for consent. Human reading of those reports is limited to investigating technical failures and service security; it does not authorize reading page content outside the exceptions listed above.

9. Our legal bases for using your data

If you are in the EU or the UK, we must have a specific legal basis for each thing we do with your personal data, and must tell you which one it is. Ours are these.

Running Tabless on a tab you choose — performing our contract with you

Listing your open tabs, reading the pages you allow, taking what you type, sending them to the model and returning the result is the service you asked for. We cannot deliver it without doing these things, so we do them to perform the Tabless Terms of Service, not on your consent. Reads, written-column fills, approved actions and record updates happen as part of carrying out your instructions or loading and using a tab you wove earlier, as sections 2, 3 and 7 explain.

Your account — performing our contract with you

Knowing whose request this is, so that only you can use Tabless as you, is part of that same agreement.

Keeping the service working — our legitimate interests

We use the access logs, monitoring records and automatic technical reports described in section 2 to assess and improve product quality, including finding failed or slow requests and why they failed. We also use the access logs to measure how much each account uses Tabless, counted by the pseudonym section 2 describes, so that we can plan capacity and set fair usage limits and prices. Our interest is in keeping Tabless working reliably for everyone using it, at a cost we can sustain. These records hold no page content, nothing you typed and no result. You can object to this use — see section 10.

Improving Tabless from a run you shared — your consent

If you turn on sharing, we keep the record described in section 2, and we read it, to find out where Tabless goes wrong. We do that on your consent and on nothing else. That is why the setting starts off, why it is a switch rather than a step in a flow you have to get through, and why it is offered in both states — a consent you can only give is not a consent. Withdrawing it is as easy as giving it, and takes effect on the next run; it is not retrospective, which section 10 explains.

Voluntary Help reports — your consent

When you choose to send a Help report or a report from a failure, we deliver your note and the disclosed report details to the Tabless team so a person can read and investigate them. We rely on your consent for that voluntary report and human reading. Sending a report is optional and is separate from transcript sharing; refusing either does not prevent you from using Tabless. Section 5 describes retention after delivery.

Everything else — not consent

Apart from transcript sharing and voluntary Help reports, no other processing in the extension described here runs on consent. Turning sharing off or choosing not to send a report changes nothing about your ability to use Tabless. The extension’s local sign-in storage is described in section 3. The tabless.ai website is separate and asks for consent before it loads any third-party analytics; decline there and it makes no third-party request at all. It does count page views on its own server, which involves no cookie and nothing that identifies you. When you read a blog post, your browser also sends our server the part of the post’s address that names it, and the server adds one to that post’s read count, kept in Wix Data. No network address, cookie or visitor identifier is stored with the count. Your network address is used only briefly, in the server’s memory, to limit repeated requests. Where you have accepted analytics, or where the website does not ask for consent, a marker in that browser tab’s session storage stops the same tab from counting a post twice; otherwise there is no marker. A post shows its count once it is above 500.

10. Your rights

Depending on where you live, you may have the right to access, correct, delete, port, or object to our use of your personal data, and to complain to your data protection authority. Records about you can include technical access logs while they are retained; your Wix account itself is covered by the Wix Privacy Policy. The pages Tabless reads are not retained by our service. You can object to our use based on legitimate interests, which is product quality and measuring how much each account uses Tabless, as section 9 describes.

Withdrawing consent to sharing has a limit worth stating plainly. Turning the setting off stops the collection from the next run: a run already under way finishes as it began, and no run started after that writes a shared record. It does not erase the records already written, and we cannot erase them for you on request either: nothing in our code can remove an individual record before its period ends. They carry no account identifier. The one thing they share with any other record is the run identifier section 2 describes, which ties a shared record to that run’s access logs, and those logs carry the pseudonym of your account, so while both are kept a shared record could be traced to your account through them. They age out on the period in section 5, and nothing else removes them. If that is not a trade you want to make, the remedy is to leave sharing off, which is where it starts and where it stays unless you move it.

Write to us at maksimn@wix.com and we will help as far as the data we hold allows. Uninstalling the extension stops future page reads and requests from that browser. The extension also makes no page reads or requests while your computer is off. Requests already sent may still finish on our service or at our AI provider, and records already held remain subject to the retention rules in section 5.

The controller of your personal data is Wix.com Ltd., Yunitsman 5 St, Tel Aviv, Israel, together with its affiliated companies, as the Wix Privacy Policy sets out. Wix.com, UAB is the Wix company that publishes Tabless on the Chrome Web Store. Israel is a country the European Commission has decided offers an adequate level of protection for the personal data of EU residents, and that decision is the basis on which your data is held there.

For the purposes of Article 27 GDPR, Wix’s representative in the European Union is Wix Online Platforms Limited, 1 Grant’s Row, Dublin 2 D02HX96, Ireland. For the purposes of Article 27 UK GDPR, its representative in the United Kingdom is Wix.Com (UK) Limited, Tower Bridge House, St Katharine’s Way, London E1W 1DD, United Kingdom.

You can reach Wix’s Data Protection Officer team at dpo@wix.com, send a rights request to privacy@wix.com, and complain to your local supervisory authority for data protection at any time.

Clearing this browser. Delete account at https://app.tabless.ai/account requests removal of this browser’s supported Tabless extension data: saved tables and rows, history, conversations, timings, settings, sign-in credentials and the site access you granted (an optional permission for record checks, if you granted it, stays until you remove it or uninstall), plus the web app’s welcome-guide markers. It attempts to revoke the extension’s Wix grant. It does not delete your Wix account, other Wix products, Wix’s usage or billing records, or our retained logs, or reports already delivered to the Tabless team. Subscription checks require you to cancel a renewing, pending or unpaid Premium subscription first; a paid subscription already set to end can proceed, with the remaining Premium access given up as the confirmation explains. The page reports partial failures or an unreachable extension rather than claiming removal. It currently targets the supported development extension installation and the supported Store extension installation in this browser; another browser or an unsupported Store installation is not cleared. Uninstall that installation to remove its local extension data; uninstalling alone does not revoke the Wix grant.

11. Children

Tabless is not directed at children and is not intended for use by anyone under 18. We do not knowingly collect personal data from them.

12. Security

Connections between the extension, our service and Fireworks are encrypted in transit. Access to the service is restricted to the people who operate it. No system is perfectly secure. Section 5 describes retention, including temporary prompt caching at Fireworks.

Fireworks, the only third party in that path, is audited annually to SOC 2 Type II and holds ISO 27001, ISO 27701 and ISO 42001 certification. Its current reports are listed at its trust centre.

13. What the Wix Privacy Policy adds

This policy is supplemental, and the Wix Privacy Policy supplies everything it does not, including:

• your Wix account, and everything Wix does with it outside Tabless;
• how data may be transferred out of your country — an adequacy decision, the Standard Contractual Clauses, the UK International Data Transfer Addendum, or the EU–U.S., UK and Swiss–U.S. Data Privacy Framework;
• Wix’s undertaking that a third-party AI provider it shares personal data with is contractually barred from using that data to train or improve its models;
• how to exercise your rights, and how a complaint about them is handled;
• how long Wix keeps data after an account is closed;
• cookies, which the Wix Cookie Policy covers;
• automated decisions that can suspend or block an account, and your right to have one reviewed by a person;
• the security measures Wix applies across its services; and
• how that policy is updated, and how you are told.

This list names those clauses so that you can find them. It does not paraphrase them and does not change what they say — read them in the Wix Privacy Policy. Where a clause there and a clause here cover the same ground, this policy is the more specific and governs for Tabless: sections 2 to 6 set out what Tabless reads, who receives it, how long it is kept, and what it never touches.

14. Changes to this policy

We may update this policy. The current version, with its effective date, always lives at this address. If a change materially affects what happens to your data, we will signal it in the extension or on its Chrome Web Store listing before it takes effect.

15. Contact

Questions about this policy, or about what Tabless does with your data: maksimn@wix.com. We aim to reply within three business days.