YALineo
EN
Install

Back to home

YALineo privacy policy

Version of November 13, 2026, for YALineo 0.34.4.

YALineo is a browser extension that draws the lineage of a Databricks workspace. It runs entirely in your browser. There is no YALineo server.

This policy covers the extension, the presentation website and email exchanges with YALineo. It follows Québec's Act respecting the protection of personal information in the private sector (Law 25) and takes the European GDPR into account.

Person in charge of the protection of personal information. The founder of YALineo, Abdouramane Youssouf. For a question, an access or correction request, or a complaint: contact@yalineo.com.

What it reads. Metadata of your Databricks workspace (catalog, schema, table and view names, lineage links, owners, descriptions, tags, write and read dates, names of jobs, pipelines, dashboards and queries), through read-only SELECT statements on the system tables, with your permissions, sent only to your workspace. In analyst mode, the lineage comes from the Unity Catalog lineage API (GET /api/2.0/lineage-tracking/table-lineage, the source of the Lineage tab of Catalog Explorer), table by table, with your permissions, still sent only to your workspace. To show notebook names instead of numbers, YALineo lists your workspace folders (GET /api/2.0/workspace/list on /Users/<you>, /Shared and /Repos/<you>, names and ids only, never notebook content) and reads your address with SELECT current_user(). For the FinOps side, YALineo also reads, through SELECT statements, the Databricks billing of this workspace (system.billing.usage and system.billing.list_prices: quantities used, list prices, ids of jobs, pipelines, warehouses, clusters, Agent Bricks agents, serving endpoints and apps, the account they run as), the outcome of job runs (system.lakeflow.job_run_timeline), when you have access the machine hours of each cluster per instance type (system.compute.node_timeline, for the Calculator: cluster id, instance type, driver or worker, duration, never the machine's addresses or metrics) and the compute time and row counts of queries with the Genie space that ran them (system.query.history, never the query text nor the questions asked to Genie). To show Genie space names instead of ids, YALineo reads their list (GET /api/2.0/genie/spaces, names and ids only). Like the rest of the map, this data stays between your browser and your workspace. Your Databricks authentication: in session mode, requests run from the Databricks tab you already have open; YALineo never reads, copies or keeps the session cookie. In token mode, the personal access token stays on the device (session memory by default, disk only if you choose "Remember") and is sent only to your workspace. On Databricks pages, the chip script reads the page address and the color of the top bar. To show a cost next to jobs, pipelines, warehouses, notebooks, dashboards, Genie spaces, serving endpoints, apps and tables, it goes through the page's links and reads their address (never their text); it keeps only the id (the name for an app) of those leading to such objects, measures their size to place the badge, and looks the cost up in the map already loaded on your device, without any request; a setting hides these costs, and the switch of the chip card pauses YALineo on every Databricks page. It never reads the page content. In session mode, a small script observes the calls the Databricks web app makes to its own API and keeps, in the page's memory only, the headers of its last accepted calls, including an authorization header if the app sends one (six sets at most per API prefix, /ajax-api and /api, plus, for each, the last set accepted for YALineo; and, in all, up to 64 distinct anti-CSRF values to count them) and the anti-CSRF value the workspace sends back in its answers, so YALineo's reads are accepted the same way; at each read, YALineo also looks for an anti-CSRF value and the workspace id in the page's readable cookies, meta tags, page variables and address. Those values never leave the page, and the diagnostic holds no value but technical facts, among them header names, call counts, response statuses, the source tried (cookie, tag, page), the kind and method of the app's calls (the kind is the first two parts of the call's path, which can include a resource name, such as a serving endpoint, an app or a clean room), and for the anti-CSRF token its shape (such as uuid-36) and age, never its value. On your request only: "Estimate the volume" in the settings counts, per catalog, the links and tables your settings would read (numbers, no table names); the Analytics view reads, for the table or job you pick (or, for a guided question such as "What rose the most?", the one the answer puts first), its costs, runs and reads day by day and how many jobs or people read or wrote it (never their names); these answers stay in the open page and are not saved. The description workshop reads, for the table you open, the name, type and comment of its columns (system.information_schema.columns). Since 0.22, "Read the columns" in the data catalog and the glossary reads the same for the loaded catalogs, kept with the map (same retention), and "Read the published glossary" in the glossary reads the glossary table you name. Its "sheet to validate" is a file you download to your device (names of the tables handled, owners, proposed descriptions and tags): YALineo sends it to nobody, you choose whether to pass it on.

What it keeps. Everything is kept on your device, except what your browser's sync carries: the addresses of the extension's pages (the studio, the settings), which can hold the workspace address, table names or filters (see below): the map, with the costs of the chosen period and of the period before it (to compare each card) (by default in session memory, erased when the browser closes; a map too big for session memory goes to disk and stays there until the browser's next start or "Erase now" (the browser counts that memory in its own way: in Chrome, a map of a few MiB can already exceed it, less if other YALineo data fill it, for example other maps, previous versions or estimates); if you choose "Keep", on disk with up to 9 previous versions, until you erase it), the settings (workspace address, connection mode, warehouse, chosen catalogs, imported architecture rules, followed tables, display preferences such as the theme, the style chosen (since 0.34), the side bar open or folded, its sections unfolded, and the metro map or graph) until "Erase everything", a health journal, kept on the device until "Clear the journal" (Health page) or "Erase everything" (for the last 8 refreshes, their date and time, the mode, the outcome, the duration, the number of tables and links, and, per step, the duration, the number of rows and the error code; the last 25 errors with their date and time, step, code and message; the last session connection with its date, see above), in whose messages YALineo masks web addresses, tokens, emails and the names it recognizes (full catalog.schema.table names, names in backticks), though not completely: names or identifiers of your data (catalog, schema, table or column names, storage paths, the workspace address written without https), an email or part of one, or a resource name the Databricks app called can remain in forms it does not recognize (for example a name quoted alone or in two parts, a name part that starts with a digit or holds an accented letter, the fourth part of a name, or the name or domain of an email), and the Calculator's estimates (their names, notes and workloads, including the workloads taken from the FinOps side with their names and measures: like the map, in session memory by default, on disk only if you choose "Keep") and its settings (cloud, region, plan, discounts, the prices you enter) until "Erase everything". Since 0.23, each estimate also keeps the prices it used (value, origin, date), its total and, for a measured workload, the end of its measures and its workspace, so it reopens as saved; and the follow-up of the findings on the "To review" page (the state you choose, its date, your note and a fingerprint of the evidence seen, per workspace) follows the rule of the map: session memory by default, disk only if you choose "Keep", erased with the workspace or by "Erase everything". Since 0.24, the analyses you save on the Costs side keep their name, settings (measure, split, grain, chart), filters (products, workload types, tags, run-as users, catalogs, schemas) and dates, per workspace and 50 at most, never an amount; and the Calculator's projects ("Cost a data project": the sources, volumes, viewers, questions, durations and prices you enter) are kept with the estimates. Both follow the rule of the map. Since 0.25: the names of one-time runs (the run_name of system.lakeflow.job_run_timeline, for jobs absent from system.lakeflow.jobs) are read with the map and kept with it, same rule; "Read my account's prices" (Calculator) reads, on your request only, your account's list prices (system.billing.list_prices), kept in the page's memory only, never stored, forgotten by "Erase everything"; an estimate file you export holds the estimate as saved (names, notes, kept prices and, for a measured workload, its key, the workspace id and its measures), so sharing the file shares them, and a file you import is read in the browser, then kept like the other estimates; the Calculator's assistant is off by default, its setting (on or off, the endpoint name) stays with the other settings, and when you click "Propose" your description (2,000 characters at most) and fixed instructions are sent, through a SELECT ai_query(...) statement, to the model you named, served by your workspace and billed by Databricks to your account, through no YALineo server; if that endpoint serves an external model (OpenAI, Anthropic, Google…), Databricks forwards the description to that provider, so choose an endpoint without tools, since an agent with tools could act; Databricks may keep that statement in the query history and in the endpoint's inference tables if they are on; YALineo keeps no description and adds nothing to an estimate without your click. Since 0.27: the usage profile you choose in the settings ("Complet" by default, or business, data steward or owner, developer, architect, FinOps, data scientist, BI analyst: it only puts a padlock on the pages outside your role, it is not an access control) and the width or folding of the right panels are kept with the display preferences until "Erase everything"; they never leave your browser; "Check over 365 days" (the "Why?" of a missing link) reads, on your request only, the lineage links of one table in system.access.table_lineage and system.information_schema, and the answer stays in the page's memory; "Copy the calculation" (Simulations) puts in the clipboard, on a click, your figures, the answer, the steps, the prices used (including the ones you entered or your account's) and the sources, never a token or a header. The stations you move on a drawing stay in the page's memory only, never in storage. The public prices the Calculator uses are bundled in the extension: it downloads nothing. The Analytics explorer's view and the table followed on the map are part of the studio's address, so the back and forward arrows return to them; the table name, the explorer's filters and search may hold table names, owners or tag values, and like any address it stays in your browser history (and its sync, if it is on, turned on by you or by your organization), nowhere else. Since 0.22, the business glossary (terms, definitions, synonyms, domains, owners, links to tables and columns, rejected terms) is kept with the workspace settings (2 MB at most) until "Erase everything", or until "Erase terms" on the glossary page (0.29), which removes from this device the whole glossary or the terms of one source (nothing is erased in Unity Catalog; the erase password asked then is compared on the spot and forgotten, never kept nor sent); an Excel or CSV file you import is read in the browser and only the terms you keep are saved, never the file; the glossary's SQL statements (proposals by the AI of Databricks with ai_query, publication to Unity Catalog) are text you copy and run yourself, YALineo never runs them; an ai_query statement sends the names, descriptions and column names of the tables chosen to the model you name, served by your Databricks workspace: a Foundation Model APIs model, billed by Databricks, or an external model, to whose provider Databricks passes that text, through no YALineo server; the column inventory you read on request is kept with the map, same retention. The descriptions and tags you validate in the workshop are kept with the workspace settings until "Erase everything"; the Genie text you paste, and what you type before validating, stay in the page's memory only and go when it closes; YALineo never writes them to Unity Catalog, it prepares the SQL the table owner runs. Since 0.30: "Copy the context" (the studio's status line) puts in the clipboard, on a click, the name of the page, the workspace, the date of the data, the periods, then the text the page shows (table and owner names, amounts...), cut at 40,000 characters, with no token or header; you choose where to paste it. The map's "PNG" and "HTML" create a file you download to your device: the picture of the map as drawn (the schema, line and reader names shown), with, for the HTML page, the map's date, the periods and the table followed; the HTML page holds no script and loads nothing. The export center of the "Export" page creates, on your click, files you download to your device (an HTML report, CSV files, an Excel workbook) or a tab your browser prints to PDF: they hold the rows of the pages chosen, with the names of tables, jobs, owners and the workspace address; they are sent nowhere, and sharing a file shares that information.

Since 0.31: the studio's display settings also keep, until "Erase everything", the reading chosen for the map (domains, freshness or use), the map overview (shown or not), the filters folded or shown, and the first steps of "Get started" (done or not, the card hidden or not): true or false values, no table name; they never leave your browser. The studio's trail keeps, in the page's history, the last three pages opened (their view and the asset of their sheet) and where each was scrolled: like the studio's address, it stays in your browser history. "Your day at a glance", the command palette, the map's halos and the overview are computed in the page from the map already read: no extra query.

Since 0.32: the display settings also keep, until "Erase everything", the shortcuts chosen for Ctrl K and their order (names of YALineo pages, calculations and actions, never a table name), the folded cards of the Simulations and the progress of "Learn" (the modules done and their quiz score); they never leave your browser. The right-click menu acts in the page; "Copy the name" and "Copy a SELECT query" put in the clipboard the table's name, or a SELECT * ... LIMIT 100 query on it that you run yourself in Databricks if you decide to: YALineo does not run it. The "AI: Genie and agents" page calculates in the page, from your figures and the Calculator's prices: no extra query. Your figures stay in the page's memory while the studio is open. "Add to an estimate" keeps it with your other estimates, under the same retention rule. "Report (HTML)" and "Estimate file" create a file you download to your device; "Copy the summary" puts the text in the clipboard; "Prepare a mail" opens your mail program with the summary and no recipient: you choose whom to send it to, and nothing leaves YALineo. The courses, the dictionary and the paths of "Learn" ship with the extension: reading them sends no request. Their links open, on your click, the official pages of Databricks, Microsoft, AWS or Google in a new tab. The Diagnostic badge checks, in the page, the read-only guard, the network allow-list, the last read, recent errors and the map's freshness, from what YALineo already keeps: no extra query.

Since 0.33: the language chosen in the settings (French, English, or the computer's) is kept with the preferences; the extension's service gives it to the chip and the badges on Databricks pages, sending it nowhere else. The folded sections of the settings page, the Analytics page and the glossary are kept the same way (names of YALineo sections, never a table name), until "Erase everything". The saved analyses of the Analytics page (thirty at most per workspace) keep the question, the explorer view, the period, the asset analysed, the assets compared and their colours, and the filters chosen, never an amount: the figures are read again when one is opened. They follow the rule of the estimates (session by default, on the device if you keep the plan), are erased by "Erase everything" or by forgetting the workspace, and live only as long as the window for the example and an imported file. Comparing assets and changing the period read again, through the Analytics queries already described, the daily costs, runs and reads of the assets chosen: no new query. "PNG", "SVG" and "Page (HTML)" create a file you download to your device; the HTML page holds no script and loads nothing. "Ask for a session" in "Learn" opens your mail app to contact@yalineo.com with a message template and your progress in the path (its name, the number of modules done): no data from your workspace is attached, and you decide whether to send it. The "AI: Genie and agents" page adds cache write tokens and the Unity AI Gateway log volume to its calculations, still in the page and without a query.

Since 0.34.4: your team's columns in the glossary (their names, and their values from an imported file or typed) are kept with the glossary, under the same rule and within the same 2 MB, and "Erase terms" (the whole glossary) removes them too. The calculations you save in "Size and tune" stay in the memory of the studio's page: they go when it closes or reloads, and are never written to storage. The Excel, Word and PDF files of calculations, estimates and projects are made in the browser and sent nowhere; sharing a file shares what it holds.

What it sends. To your Databricks workspace: the read statements described in the README, nothing else. To anyone else: nothing. No analytics, no automatic error reports, no install identifier, no sale or sharing of data. Only when you click Support, your mail app opens to contact@yalineo.com with a diagnostic giving the YALineo version, the browser, its version and the system, the language, the number of workspaces with their mode and cloud, the retention choice, then, from the journal, the last session connection and, with their dates to the minute (UTC), the last 4 refreshes and the last 8 errors, all cut at 1,800 characters, with the journal's masking and its limits; you review it and decide whether to send it. Optional system notifications (off by default) are shown locally by your operating system. A "Tutorial", "How it is calculated" or "Security and evidence" link opens yalineo.com in a new tab, like any link; the extension sends it nothing, the address only holds the language and the name of the tutorial, of the part of the method or of the page. Only when you click "Give feedback", your mail app opens to contact@yalineo.com with a message template to fill in and the version number; nothing from your workspace is attached, and you decide whether to send it. Only when you click "Buy me a coffee" in the extension (or "Buy the creator a coffee" on the website), the creator's Ko-fi page (ko-fi.com/yalineo) opens in a new tab; the extension sends it nothing. If you leave a tip, the payment happens at Ko-fi and Stripe, under their own privacy policies; the creator only sees what Ko-fi shows creators for each tip (for example the amount, the display name and your message).

The website. It is served by Cloudflare Pages (Cloudflare, Inc., United States), which processes technical connection data (IP address, browser, page requested, time) to deliver the pages and protect the site from attacks. YALineo adds no analytics, no advertising and no tracker. The site sets no cookies and opens without any sign-in or code. If you write to us (for example to request a demo), we receive what you send (name, company, address, message), use it only to answer and set up the demo, and keep it in our mailbox (Gmail, Google LLC, which receives what Cloudflare forwards from contact@yalineo.com) for at most 24 months after the last exchange, then delete it. It is never sold or shared.

Outside Québec. Cloudflare (hosting, email forwarding) and Google (email) process this data outside Québec, notably in the United States. Before choosing them, YALineo assessed the privacy factors: only the data strictly needed, encryption in transit, contractual protection commitments from these providers. The Databricks metadata read by the extension stays between your browser and your workspace; only what this policy describes leaves: the addresses of the extension's pages (the studio, the settings) in your browser's sync if it is on (turned on by you or by your organization), and what you choose to send, a support diagnostic sent to contact@yalineo.com (so through Cloudflare and Google), an email draft you address yourself, a copy to the clipboard, the files you export, the pre-flight's comment in your repository, an ai_query statement or the Calculator's assistant to the model you name.

Pull-request pre-flight. The command-line tool runs in your own continuous integration with your own secrets, sends the same read statements to your workspace and writes a comment in your repository. YALineo receives nothing.

Erasing. "Erase now" erases the map of a workspace; "Erase everything" erases maps, history, settings, tokens and journal; uninstalling removes all extension storage.

Your rights. You can ask for access to the information YALineo holds about you, for its correction or deletion, and withdraw your consent. You can also ask to receive it in a structured, commonly used technological format. Write to the person in charge: contact@yalineo.com. We answer within 30 days. If the answer does not satisfy you, you can file a complaint with the Commission d'accès à l'information du Québec. In the European Union, you can also contact the data protection authority of your country.

Governance. The person in charge is the only one with access to the emails received; anyone joining YALineo would be bound to confidentiality and trained first. Emails are kept at most 24 months after the last exchange, then deleted; the extension sends nothing to YALineo on its own, so YALineo keeps from your workspaces only what you send it yourself, a support diagnostic (names can remain despite the masking) and what you write in or attach to the email, kept with it at most 24 months after the last exchange. Every confidentiality incident is recorded in a register; if it presents a risk of serious harm, the Commission d'accès à l'information and the people concerned are notified. Any new system or service touching personal information gets a privacy impact assessment before it goes live. Complaints: write to the person in charge; acknowledgement within 7 days, reasoned answer within 30 days.

Publisher and host. Publisher: YALineo, Abdouramane Youssouf, Québec (Canada), contact@yalineo.com. Host: Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, United States.

Contact and changes. contact@yalineo.com. Each version of this policy is dated at the top and listed in CHANGELOG.md; an important change is announced on the site.