Why TazzoGram exists
The problem this product was built around, and who it is for.
Every company that has documented a process has the same problem. The diagram was drawn once, by someone who has since moved on, in a tool nobody wants to reopen. The process changed six months ago. The diagram did not. So the diagram quietly becomes fiction, and everyone stops trusting it.
The reason is not laziness. It is that updating a diagram is disproportionately expensive compared to the size of the change. Moving one approval step costs you an hour of dragging boxes and re-routing arrows. So nobody does it for small changes, and the small changes are exactly what accumulate into a diagram that is wrong.
What TazzoGram changes
TazzoGram turns the diagram into text. Once a process is Mermaid code, changing it is a sentence, not an afternoon: "add a compliance review between Legal approval and signature". Text also means the two things drawings never gave you: a real diff (what exactly changed between version 4 and version 5) and a real history (who changed it, when, and the business reason they gave).
Start from what you have
You do not redraw anything to get started. TazzoGram reads your existing file, including a photo of a whiteboard or a PDF someone emailed you.
Change it in your own words
Describe the change the way you would describe it to a colleague. TazzoGram rewrites the code and explains back what it did.
Keep a real trail
On Practice and Firm, each accepted change can be committed to your organisation's own GitHub with a business-language message, so the history reads like decisions, not file saves. Our team connects it for you.
Who this is for
TazzoGram is built for the people who own processes rather than the people who own drawing tools: business analysts, process and quality teams, operations leads, compliance and audit functions, consultants who inherit a client's undocumented process and have to make sense of it fast.
That is the niche deliberately. Developer-facing diagram-as-code tools already exist and assume you are comfortable in a code editor and a git client. Drawing tools already exist and assume you have the patience to draw. TazzoGram sits in the gap: the rigour of diagram-as-code, reached through business language instead of syntax, with the confidentiality controls a real company needs before it will let any of this near a language model.
The confidentiality point, stated up front
Business process diagrams are full of things you cannot casually send to a third party: customer names, internal system names, supplier names, org structure. PROTECT, TazzoGram's Redaction Glossary, replaces those terms with neutral codes before anything is sent, and puts them back afterwards. This is not a setting buried in a menu. It is the centre of how the product is designed, and it has its own section: The Redaction Glossary.
The screen, explained
Everything at the top of the left panel, in one picture.
The top of the left panel holds the controls that decide what you work on and how your confidential words are kept safe. The picture below is that strip as it looks today, with each control numbered.
The top of the left panel as it appears today, after a change. This example shows PROTECTED · 12: twelve confidential words are hidden before anything is sent to the AI, and the list is kept in this browser (Local Mem.).
| # | Control | What it does |
|---|---|---|
| 1 | Open file | Opens the diagram you want to work on: a photo, a PDF, a .bpmn, .drawio, .svg or Mermaid file. See Opening a diagram. |
| 2 | Open folder | Reads every diagram in a folder, only to find words worth protecting. It never opens or converts a diagram and never uses a ticket. See Building your protected list. |
| 3 | PROTECT | Shows whether your confidential words are hidden from the AI. PROTECT means nothing is protected yet, PROTECTING… means a file is being read for confidential words, in your browser, and PROTECTED · 12 means twelve words are hidden. Click it to see or edit the list. See The Redaction Glossary. |
| 4 | MAX | The highest level of PROTECT. Tick it to hide every word of the open diagram from the AI, everyday words too, not only names. Those words are added to your protected list. |
| 5 | Local Mem. and its number | Your protected list lives in this browser, on this device. The small number is how many words are on it. If it reads 0, nothing is being hidden. See Where your list lives. |
| 6 | Original and Modified | Ready after your first change. Choose Original to see the diagram as it was before, and Modified to come back. |
| 7 | Starter Kits | Ready-made diagrams by industry and standard. A kit opens for free, with no ticket used. |
| 8 | Code Panel | The text behind the diagram, folded away until you want it. Open it to read, copy or edit the code. Click Edit before typing in it, so one stray key cannot wipe it. |
Making room for the diagram
The diagram is the part that matters, so the left panel steps aside
when you want it to. Click the « button on the edge
between the two panels and the left panel shrinks to its narrowest
useful width. Click » to bring it back. You can also
drag that edge to any width you like. Log out sits in the top bar,
next to your e-mail address and the language list.
Opening a diagram
What TazzoGram can read, and what happens to each format.
There are two buttons at the top left, and they do very different things.
Open file (single file)
Opens one diagram to work on. A .mmd, .bpmn, .drawio or .svg file is first read for confidential words by PROTECT, in your browser. Anything later sent to the AI goes with those words hidden.
Open folder (whole folder)
Reads every diagram in a folder and adds words worth protecting to your list. It never opens or converts a diagram, never sends anything and never uses a ticket. Works in Chrome and Edge.
Formats, and what each one costs to read
Mermaid, .bpmn and .drawio files open for free, right in your browser. Pictures, PDFs and most .svg files have to be read by the AI, and that uses one ticket.
| Format | Cost | Notes |
|---|---|---|
.mmd .mermaid .md | Free | Already a TazzoGram diagram. It opens right away, with nothing to convert. |
.bpmn .drawio | Free | Every step, decision, lane and arrow is read exactly as drawn, and the file is not sent anywhere. If a file has pictures inside, or arrows not joined to any shape, TazzoGram asks you before letting the AI read it for one ticket. |
.sql .ddl | Free | A database script with CREATE TABLE lines opens as an ER diagram: tables, columns, keys and links, read in your browser and not sent anywhere. On an ER diagram, Save As can also write a .sql script back. |
.svg | Free or one ticket | Free when it was saved from TazzoGram or draw.io: it opens exactly as you saved it. Any other .svg is only a drawing, so the AI reads it: one ticket. Your labels still arrive exactly as you typed them, and names you protect are hidden before the file is sent. |
.jpg .png .heic | One ticket | A photo of a whiteboard or a screenshot works. The AI reads the picture, so small or blurry labels can come back wrong, and names inside a picture cannot be hidden. |
.pdf | One ticket | Read like a picture, page by page. A very long PDF is refused, so send only the pages with the diagram. |
.vsdx (Visio) | Not opened | In Visio, choose File > Save As > SVG, then open the .svg here. Visio saves one page per file. |
The practical takeaway
If you have a Mermaid, .bpmn or .drawio file, open that
instead of a screenshot: it is free, exact, and it never leaves your computer.
The Redaction Glossary
Why it exists, what it actually does, and what it does not protect you from.
This is the feature that decides whether a real company can use TazzoGram at all. A process diagram is not neutral content. It routinely contains the names of your customers, your suppliers, your internal systems, your cost centres and your people. Sending that to a third party model, unfiltered, is a conversation with your legal and security teams that most business analysts would rather not have.
What it does
In the app it is called PROTECT. It hides the WHO and the WHAT of your process (people, companies, clients, suppliers, code names, e-mail addresses, internal web addresses, reference codes) and leaves the HOW visible (the steps, decisions and ordinary process words), because the AI needs those to understand your process.
The Glossary is a list of pairs. On the left, a real term from your business. On the right, a neutral placeholder. Before anything is sent anywhere, TazzoGram replaces every real term with its placeholder. When the answer comes back, it puts the real terms back before you see them.
The substitution happens before the network call, not after. That ordering is the whole guarantee.
Reading the PROTECT pill
| The pill says | What it means |
|---|---|
| PROTECT (dimmed) | Your list is empty, so your words are sent as they are. |
| PROTECTING… (pulsing) | A file you opened is being read for confidential words, in your browser. Anything that goes to the AI goes only after this reading ends, with the words it found already hidden. |
| PROTECTED · 12 | Twelve words on your list are swapped for codes before anything leaves your browser. Click the pill to see, add or delete them. |
Be honest about the limits
The match is exact text. If your Glossary contains
Banco Itaú, it will not catch Banco Itau
without the accent, or BANCO ITAU S.A., or an abbreviation
your team invented. The Glossary protects the terms on it, and only
those. PROTECT adds what looks confidential each time you open a
text-based file, but check the list and add the variants and
nicknames it could not guess.
It cannot read pictures either. A photo or a PDF is sent to the AI as it is, because the AI has to see the picture to read it, so names inside a picture are not hidden.
And it cannot redact meaning. If your process is unusual enough to be recognisable from its shape alone, placeholders will not change that. Treat the Glossary as a strong, practical control over identifiers, not as anonymisation of the process itself.
Building your protected list
TazzoGram fills the list for you, in your browser, without using a ticket.
Typing a list of confidential words by hand for a large organisation is not realistic, so TazzoGram builds it for you.
-
Open a file, as you normally would
When you open a text-based file (
.mmd,.bpmn,.drawioor.svg), PROTECT reads it first, in your browser, and adds what looks confidential: company names (Inc, Corp, Ltd, S.A.), the name after Client, Supplier or Project, code names in capitals, e-mail addresses, internal web addresses, reference codes and names of people. The pill pulses PROTECTING… while it reads. Then the diagram opens, and anything sent to the AI goes with those words hidden. You still see the real words. -
Or read a whole folder at once
Open folder, next to Open file, reads every diagram in a folder:
.mmd,.mermaid,.md,.markdown,.bpmn,.drawio,.svgand.vsdx. It only collects words. It never opens or converts a diagram, never sends anything and never uses a ticket. Pictures and PDFs are skipped, because only the AI could read them. It suggests more words than you need, on purpose: deleting a harmless word is cheaper than finding a missed one later. Open folder works in Chrome and Edge. -
Check the list
Click the PROTECTED pill. Delete anything that does not need protecting, and add by hand what a scan could not know: abbreviations, nicknames, spellings without accents. This is a one-time job per business area.
-
Keep working
From now on the list is applied by itself to every change you Apply and every text-based file you open. You do not have to think about it again until your vocabulary changes.
Reading the number
The number on the PROTECTED pill, and on the corner of the Local Mem. pill, is how many words are on your list. It is the fastest check in the app. If you expected 65 and you see 0, your list is empty in this browser, and nothing is being hidden.
Where your list lives: Local Mem. or GitHub
The single most consequential choice in the app. Read this one properly.
Your protected list has to live somewhere, and that choice has real consequences in both directions. Neither option is simply better.
Local Mem. is on every plan, and it is what the pill next to PROTECT shows. GitHub is part of the Practice and Firm plans. It keeps one shared list in your organisation's own GitHub account, so our team sets it up with you rather than leaving you to do it alone.
Local Mem. (the default, every plan)
Where it lives: only in this browser, on this device. It is never transmitted anywhere.
Strength: the strongest possible confidentiality position. Your list of sensitive terms really does never leave your machine.
Cost: it is trapped there. A different browser, a different laptop or a cleared cache means starting from zero. Your colleagues cannot benefit from your work, and you cannot benefit from theirs.
GitHub (Practice and Firm)
Where it lives: in a repository in your organisation's own GitHub account, filed under your Division and the specific diagram. Our team connects it for you.
Strength: it survives browsers and devices, and everyone in your Business Division works from the same list.
Cost: the list of terms is now stored outside your browser, in your own GitHub. The terms themselves are still never sent to the model in the clear, but the Glossary file exists on a server.
Getting GitHub connected
This is not a switch you flip on your own. Connecting a GitHub account touches your organisation's access rules, so we do it with you and your IT team. When you subscribe to Practice or Firm, we send you the contact for setting it up, and our team agrees a date with you. Until then your Glossary works normally in Local Mem., with nothing lost. Slack is connected the same way, together with GitHub.
How sharing actually works
This is the part that trips people up. When you choose GitHub, your Glossary is not filed under you. It is filed under your Organisation or Division ID, together with the specific diagram. Everyone who resolves to the same Organisation ID opens the same file. That is the sharing mechanism: not a copy each, one list.
Three colleagues at acme.com all resolve to the Organisation ID acme-com, so all three open, edit and see the same Glossary for the same diagram.
Where your Organisation ID comes from
You do not set it yourself, and the app does not let a browser claim one. It is worked out on the server from the address you signed in with, in this order:
| Order | Rule | Example |
|---|---|---|
| 1 | An ID assigned to you by the TazzoGram administrator | Used when one Division spans more than one domain, for example acme.com and acme.com.br together, or a contractor who should share your team's list. This always wins. |
| 2 | Your company email domain | bruno@acme.com becomes acme-com. This is the default: once GitHub is connected for your organisation, two colleagues share the moment they both sign in. |
| 3 | A private bucket, just for you | Applied to personal addresses such as Gmail or Outlook. |
Why rule 3 is not negotiable
If rule 2 were applied to a personal email provider, every Gmail user
in the world would end up in one shared bucket called
gmail-com, able to read and overwrite each other's
confidential business terms. So personal addresses always get their own
private bucket instead, and can never end up sharing by accident. If a
person on a personal address does need to share with a team, an
administrator assigns them an ID under rule 1. Deliberately, never
accidentally.
Switching between the two
When GitHub is connected, moving from Local Mem. to GitHub merges rather than replaces. Whatever you had locally is combined with whatever your team already had on GitHub, and nothing is silently dropped. Where the same real term exists on both sides, your local version wins, because that is the one you were just looking at. Your local copy is also kept up to date the whole time you are in GitHub mode, so switching back is instant and loses nothing.
Stated plainly, for your security review
Once connected, shared Glossaries live in a repository inside your organisation's own GitHub account, separated by Division and diagram. Who can read that repository is decided by your GitHub permissions, not by us. TazzoGram gets only the access it needs to write to the repository you choose, and you can revoke that access from GitHub at any time. Local Mem. remains available on every plan, with no functional penalty to the redaction itself.
Security and your data
What we keep, what never leaves your browser, and what we do not claim.
What never leaves your browser
Before your diagram or your request goes to the AI, every word on your PROTECT list is swapped for a code, such as C0001. When the answer comes back, your browser puts your real words back. The AI sees only the codes.
Your PROTECT list is kept in this browser, on this device. It is not sent to us.
The limit
This covers the words on your list, written exactly as they appear there. Words inside pictures, photos and PDFs cannot be hidden, because the AI has to see the picture to read it.
What we keep, and what we do not
- We do not save your diagrams on our servers. To make a change, the diagram text goes to the AI service and comes back, with your protected words hidden.
- Our usage record keeps the name of each file you open, not what is inside it.
- We keep your e-mail address, your plan and your balance, so you can sign in and use what you paid for.
- Sign-in attempts, and the record of which features you use, are kept for 90 days and then deleted.
- If our safety check flags a change request, we keep the words of that request so we can review it.
Payments
- Card details never reach our servers. Stripe, the payment company, takes the payment on its own page.
- Before we add anything to your account after a payment, we check that the message really came from Stripe.
Behind the scenes
- Every page and every request travels over an encrypted connection (HTTPS).
- Every night we make an encrypted backup of our records. The key that opens it is not kept on our server.
- After every update, an automatic check tries to open our record files from the web. If any of them opens, the update is rolled back.
- Our admin pages ask for a code from an authenticator app, not just an e-mail address.
What we do not claim
TazzoGram has not yet had an outside security audit or a certification such as SOC 2 or ISO 27001. We will say so here when it has.
No online service is perfectly safe, and we do not promise that ours is. If you see something that looks wrong, write to us:
Asking for a change
How to phrase a request so you get what you meant.
In the left panel there is a box labelled TYPE YOUR CHANGE, with A- / A+ to make the text smaller or larger. You type what should change, press Apply, and the diagram is rewritten. Underneath, SUMMARY tells you in plain language what was actually done.
Name the steps exactly as they appear in the diagram. That is what makes a request unambiguous.
What makes a good request
Works well
- "Add a Credit check step after Order received, owned by Finance."
- "Change the Manager approval gateway so that anything above 50,000 also needs Director approval."
- "Move Archive documents to the end, after Invoice sent."
- "Rename the Ops lane to Service Delivery."
Causes trouble
- "Make it better." Nothing to act on.
- "Fix the approval." Which one, and fix what about it?
- "Add the usual compliance steps." The app does not know your usual.
- Five unrelated changes in one paragraph. Do them one at a time so you can see each result.
Undo, save points and Start over
At the top of the diagram panel, Undo takes back the last change, one step at a time. Save marks the version you like, and Restore saved brings it back, even after more changes. These are kept only while the page is open: reloading or closing the page loses them, so use Save As for anything you want to keep.
Start over clears the diagram you opened, so you can open another one. On a sample diagram it brings the original back. It does not touch anything you have already saved as a file or saved to GitHub.
Comparing before and after
The Diff button shows the previous version and the new one side by side, so you can confirm the change did what you asked and nothing else moved. For a quick look, choose Original at the top of the left panel, then Modified to come back. Get into the habit of checking it before saving. This is the single biggest advantage of a diagram that is text: you can actually see what changed.
When the AI gets it wrong
What TazzoGram checks before you see a diagram, and what happens when a check fails.
AI models are not deterministic. Send the same diagram twice and you can get two slightly different answers, and once in a while one of them has a mistake in it. Nobody can make that go away completely. So TazzoGram is built to catch those mistakes before they reach you.
| # | If this happens | TazzoGram does this |
|---|---|---|
| 1 | The answer comes back without a diagram in it | Asks again, once, on its own, before showing you any error. |
| 2 | The answer is cut off before the end | Recovers the part that arrived and shows it, and the case is logged so we can look at it. |
| 3 | A label in a photo or scan is hard to read | The AI marks that label with ⚠ and lists it at the end of the code, so you know exactly which words to double-check. Files like .drawio, .svg or .bpmn are read as exact text, so they never need this mark. |
| 4 | The code has a formatting slip the drawing engine can't read | Sends it back for a fix, automatically. You see a short "Fixing it now" message, and then your diagram. |
| 5 | Even the fix doesn't draw | Keeps the code in the editor, so nothing is lost. Click Start over to try again. |
| 6 | The file isn't a process diagram at all | Tells you so in plain words, instead of making a diagram that makes no sense. |
What you can still do
Read the Summary first, since it says what was understood. If a step is wrong, ask for the correction in the change request box, or fix the line yourself: open Code Panel, click Edit, and change the text. And if you started from a picture, a structured export from your drawing tool (.svg, .drawio or .bpmn) will always be read more accurately.
Anything you are unhappy with goes through a report, so a person looks at it with the evidence in front of them. See the box below.
Tell us when it gets one wrong. It is how TazzoGram gets better.
If a conversion or a change comes back wrong, report it to with these five things, which are what we need to reproduce it:
- What you asked for, copied from the change request box.
- What the Summary said, copied from the panel on the left.
- The code, copied with the copy button next to Edit, in the Code Panel.
- A screenshot of the diagram panel on the right.
- One or two lines on what you expected instead.
Every report is read by our team, and we aim to come back to you with an answer within two business days.
You are not troubling us by writing. A real case is worth more to us than any amount of internal testing, because it shows the model meeting your process, your words and your file. Thank you for taking the time.
Step IDs and reading the diagram
Every step gets a short, permanent name. That is what makes a process something you can audit.
The screen has two halves. On the left, the code, in the Code Panel. On the right, the diagram. They are the same thing in two forms, and Step IDs is the switch that makes the connection visible: each shape shows the short ID the code uses for it.
With Step IDs switched on, each shape shows the same short identifier used in the code, so you can point at a box and find its line instantly.
Why a short ID beats the text inside the box
The text in a box changes all the time. "Approve invoice" becomes "Approve vendor invoice", then someone translates it, then someone fixes a typo. Every document that quoted the old wording is now pointing at nothing. The ID does not change. That is why every serious process document numbers its steps, and why TazzoGram gives each one a short, permanent name.
What you get from them
- Your audit trail stays readable. SOPs, RACI tables, control matrices and risk registers can point to "step B" and still be right after the wording changes. Auditors ask about steps, not about diamonds in the middle.
- Your change requests land where you meant, first time. "Add a compliance check between B and C" can only go in one place. "After the credit check" might match two shapes, and a request that lands in the wrong place costs you a ticket to fix.
- The same step is traceable across tools. The exported
.bpmnfile uses the Step ID as the element ID, and.drawiouses it too. Step B in TazzoGram is step B in Bizagi, Camunda or draw.io, and in your version history. - You can see exactly what a change touched. Existing IDs never change when the AI edits the diagram, and a new step always gets a new ID, so a new letter on the screen is a new step.
On screen yes, in your slides no
Step IDs are for working. When you copy the diagram with the copy button on the diagram panel, the picture comes without them, ready to paste into a slide or a document. Untick Step IDs if you also want a clean screen, for example when you share it live.
Moving around the diagram
- Zoom with the
−and+buttons, orCtrland scroll. Clicking the percentage fits the diagram to the window. - Move the diagram with the four-arrow button, then drag. Click it again to turn dragging off.
- Fullscreen gives the diagram the whole window, which is the only sane way to review something large.
Copy to clipboard
Two copy buttons, two completely different results.
Same icon, different place, different result. On the diagram panel, the copy button sits between the move button and fullscreen.
| Button | What lands on your clipboard | Paste it into |
|---|---|---|
| Copy next to Edit | The Mermaid source as plain text | Confluence, Notion, GitHub Markdown, a wiki, an email, any editor. Anywhere that renders Mermaid will draw it for you. |
| Copy on the diagram panel | The rendered diagram as SVG | PowerPoint, Word, Figma, draw.io. It stays sharp at any size because it is vector, not a screenshot. |
A habit worth forming
For anything that will be maintained later, paste the code, not the picture. A picture in a slide is dead the moment the process changes. The code can be pulled back into TazzoGram and updated in one sentence.
Save As: the file formats
Getting the diagram out of TazzoGram and into the tool your organisation actually uses.
At the bottom of the left panel, the Save As button opens a short menu with seven formats (eight on an ER diagram, with .sql). Each one produces a real file in that format, not a renamed screenshot.
Save As is the only copy
TazzoGram keeps no copy of your diagram. Until you use Save As, the work exists only on your screen, and closing the page loses it, together with the tickets spent on it. So while you have changes that are not saved, the Save As button turns amber, and the browser asks before you leave the page. In Chrome and Edge, the Save As window lets you pick any folder, including a Google Drive or OneDrive folder that syncs to the cloud. Other browsers save the file to your Downloads folder.
The footer row at the bottom of the left panel. Save As comes last, after the buttons for sharing and comparing.
| Format | What you get | Use it when |
|---|---|---|
.mmd |
The raw Mermaid source, plain text | You want the version that any editor opens, that a wiki can render, and that TazzoGram itself can re-read later for free. This is the archival format. |
.drawio |
Native draw.io XML | Your team lives in draw.io, Lucidchart or diagrams.net and wants to keep editing there. |
.vsdx |
A native Visio file | You have to hand something to a Visio shop. Opens directly, no plugin. Uses generic shapes rather than true BPMN typing, which is fine for review and reading. |
.bpmn |
Real BPMN 2.0 XML | The diagram is going into a proper BPMN tool such as Bizagi Modeler or Camunda. Tasks, gateways, events and lanes are typed correctly. |
.svg |
The diagram as an .svg (Image), sharp at any size | You need it in a slide, a document or a web page: PowerPoint, Word, Illustrator, Inkscape or any browser. Works for every diagram type, not only flowcharts. Its shapes and text stay editable in those tools. TazzoGram can open it again for one ticket, but the .mmd reopens exactly, for free. |
.pdf |
The diagram as a PDF (Document), on one page the size of the diagram | Someone needs to read, print or attach it, for example in a proposal or an audit file. It opens in any PDF reader, and text and arrows stay sharp when you zoom in. Letters outside Western European languages are kept as a sharp picture instead, so they always show correctly. |
.html |
The diagram as a web page, in one file | You want to send it to someone who has none of these tools: it opens in any browser, with no internet needed. Click the diagram to see it at full size. |
.sql |
A database script, only on an ER diagram | You drew or changed a database in TazzoGram and want to build it: one CREATE TABLE per table, then the links. It only creates, it never deletes anything. |
Exports come back in
Save as .bpmn, let a colleague edit it in Camunda, and you can
open their file back in TazzoGram afterwards. The same goes for .mmd,
.drawio and .svg. The round trip works, which is
what stops this from becoming another one-way tool. A .pdf or .html saved here
opens again too: the AI rebuilds the diagram from the picture, for one ticket. The one exception is .vsdx:
TazzoGram writes it, but to bring a Visio drawing back in, save it from Visio as .svg first.
Versioning in GitHub
Why a diagram deserves a history, and what the button actually does.
Practice and Firm plans
Save to GitHub commits into your organisation's own GitHub account, so it is part of the Practice and Firm plans and our team connects it for you. On other plans the button stays visible, and clicking it tells you how to get it. See Local Mem. vs GitHub.
Save to GitHub commits the current Mermaid code with a commit message written in business language, not file-save language. Over time you end up with something no drawing tool has ever given you: a readable record of how a process evolved and why.
This is what "the diagram has a history" actually looks like. Each entry is a decision, with a name and a date against it.
Reading the button
After a save, the button briefly turns into a status badge so you know what happened without opening anything:
- A tick with a name and time means the commit went through.
- Reload and retry means your session went stale. Sign in again and repeat the save. Nothing was lost.
- Save failed means the commit did not happen. Your code is still in the editor, so copy it out before doing anything else if you are worried.
Save deliberately, not constantly
A history is only useful if each entry means something. Saving after every trivial tweak produces noise that is as useless as no history at all. Save when you have finished a change that a colleague would recognise as a change.
Quick answers
The questions that come up in the first week.
My Glossary shows a different number of terms in a different browser. Why?
Because your list is kept in Local Mem., which by design never leaves the browser it was built in. Two browsers means two separate lists. On Practice and Firm, with GitHub connected by our team, everyone in your Organisation works from one list, on any device. See Local Mem. vs GitHub.
A colleague and I are at the same company but do not see the same Glossary.
Check three things, in order: you are both on GitHub storage rather than Local Mem. (GitHub is part of Practice and Firm); you both signed in with your company address rather than a personal one; and you both have the same diagram open, since Glossaries are filed per diagram as well as per Organisation. If your Division spans more than one email domain, ask the administrator to assign you both the same Organisation ID.
Is my diagram sent anywhere when I only open it?
Mermaid files (.mmd, .md), .bpmn and .drawio files open in your browser and are not sent anywhere. Other .svg files, and the rare .bpmn or .drawio file TazzoGram cannot read by itself, are sent to the AI to be turned into a diagram, and your Glossary words are swapped for placeholders in your browser before they go. Images and PDFs are sent to the AI as they are: the AI has to see the picture to read it, so the Glossary cannot hide anything inside a picture. A .vsdx file is not opened, but Open folder can read its words for your protected list, in your browser, and never sends it. Open folder never sends anything at all.
Can I save my diagram straight into Google Drive or OneDrive?
Yes, in Chrome and Edge on a computer. Save As opens a Save window where you can pick any folder, including a Google Drive or OneDrive folder that syncs to the cloud. That folder comes from the Google Drive or OneDrive app on your computer. The file then shows up in your Drive or OneDrive like any other file, ready to share with your team. TazzoGram never connects to your Drive account and never asks for its password. In Safari and Firefox, the file goes to your Downloads folder instead, and you can move it from there. See Save As: the file formats.
I was signed out while I was still working.
Sessions end after a period of inactivity, and also have a hard limit regardless of activity. Sign in again and continue. Anything already saved to GitHub is untouched.
The conversion got a step wrong.
If you converted from an image or a PDF, try the structured export instead, since reading a picture is inherently harder than reading a file. And you can always fix it directly: open the Code Panel, click Edit, and correct the line. It is text, so that is quicker than re-running anything. For what TazzoGram already checks on its own, see When the AI gets it wrong.
Which plans are there, and how do refunds and cancellation work?
Today you can start with the Free Trial, buy Pay as You Go tickets, become an Ambassador Early Adopter, or talk to us about On-Prem. Practice and Firm are shown but not on sale yet. Prices and what each one includes are on the Plans & Pricing page. How tickets work, and how cancellation and refunds work, are in the Terms of Service, sections 4 and 6. What we do with your data is in the Privacy Policy.
Can I use TazzoGram in Portuguese?
Yes, and in 15 other languages. Pick yours in the language list at the top right of the app (it shows ENG in English). The whole screen changes at once.
What happens to a term I add to the Glossary by hand?
It is treated exactly like a word PROTECT found by itself: replaced before sending, restored afterwards. Hand-added words are how you cover the variants a scan cannot guess, such as abbreviations and internal nicknames.
Use the OPEN FILE button (top left of this screen) to begin intelligent transformations.
