Escribal
Back to Home

Legal

Privacy Policy

Escribal · © 2026 Erik Monrreal (“the author”), publishing as EridaniDev. Last updated: 28 October 2026.

In one line: the author collects no data about you. Escribal runs on your computer, your files never leave it, and the program only uses the network when your workflow asks it to or to ask the Microsoft Store whether your subscription is still active.

1. What the author does not collect

The program carries no telemetry, no usage statistics, no automatic crash reports and no account with the author. There is no server of the author’s for the program to connect to, because none exists. The author does not receive your workflows, your data, your documents, your file paths, or anything about how you use the program.

2. Where your files are

Everything stays on your computer: the .scriba files with your workflows, the data they read and the documents they generate. The program writes them into the folders you choose inside each workflow.

When a .scriba is saved, the program replaces your user folder with a generic marker, so sharing a workflow with someone else does not reveal your Windows user name or the layout of your computer.

What does travel with the file is whatever you typed into the fields of each instruction, and that includes the passwords a document needs: the one that opens a protected PDF and the ones that protect a document or a spreadsheet. They are there because they have to be (the program writes them into the document every time you run the workflow), so whoever receives the .scriba, or the AI assistant you hand it to, can see them. Before sharing a workflow like that, take them out or change the password. Your database password is the one exception, and that is why it has a section of its own: that one is never saved (section 4).

3. When the program uses the network

There are three cases and no others:

  1. When your workflow asks for it. If an instruction downloads a file or an image from an internet address, the program connects to that address. You choose it when you build the workflow; without those instructions there is no download at all.
  2. When your workflow queries a database. If you use the PostgreSQL instructions, the program connects to the server you name, with the credentials you supply. See section 4.
  3. To check your subscription. The program asks the Microsoft Store whether your subscription is active once per working session, and again each time you open the subscription page in Settings, which shows your plans and their prices. It is a query from the operating system to Microsoft: the author takes no part in it and does not receive its result. If the store cannot answer, the program does not work and says so; it asks again only when you press Try again, and it stores nothing about that query. When you subscribe, the purchase is made by the Microsoft Store in its own window: your payment details go to Microsoft, never to the program or the author. Manage, on that page, opens your Microsoft account’s subscriptions page in your web browser.

The program’s window uses the WebView2 component that already comes with Windows, and it loads no internet page at all: its security settings only let it open files belonging to the program itself. The internal communication between the window and the engine does not leave your computer.

4. Your database credentials

  • They are not saved in the .scriba file, unlike the document passwords in section 2. The workflow carries only a connection name; the server, the database and the password are asked for by the window when you run it.
  • They travel only with that run and are erased when it ends, whether the workflow succeeds or fails.
  • No instruction can read them, so they cannot end up written inside a document, exported to a file or shown on screen.
  • The query is made in read-only mode, and that restriction is imposed by the PostgreSQL server itself, not by the program.
  • A workflow with a database cannot be run from an AI assistant, precisely so that the credentials never pass through the assistant.

5. If you connect an AI assistant

Escribal can connect to an AI assistant through a server that runs inside your computer: the assistant and the program talk to each other directly, without going through the internet or through any service of the author’s.

That said, the assistant you choose sees what you ask it to do: the instructions in your workflows, the documents it opens and what the program answers when they are run. That travels to that assistant’s provider under its own terms, not under these. Choosing the assistant, and with it its provider, is your decision. If you connect none, this section does not apply to you.

Database credentials are outside all of this, as section 4 says.

6. Cookies and websites

This policy is published as a static page. It uses no cookies, no analytics and no trackers.

7. Buying in the Microsoft Store

The subscription is bought and charged for in the Microsoft Store. Your name, your email address, your address and your payment details are handled by Microsoft as controller, under its own privacy policy, and the author does not receive them. What the author sees are the aggregated sales reports Microsoft shows him as a developer.

If you write to the contact address in section 9, the author will see your address and what you tell him, and will use it only to answer you.

8. Children

Escribal is a work tool and is not directed at children under 13. The author collects no data from anyone, and so none from them.

9. Changes and contact

If this policy changes, the new version is published at this same address with its update date. A change affecting what the program does with your data will also arrive with an update of the program.

Questions about this policy: support@escribal.com.