Privacy policy
Applies to every tool published under the Sagnato name ("the tools"), provided by Isak Vidinghoff. The sections below say what each tool reads, writes and keeps.
In short
- The tools run on the platform you use them in, on that platform's own hosting (monday code for the monday.com apps, Apify's platform for the Apify actors). We run no servers for them.
- The tools do not send us your content. They work on it inside the platform, on your instructions, and anything they keep stays in that platform's storage. We see your content only if you send or share it with us, for example in a support email or a run you share on Apify.
- Apart from the platform they run on, the tools use no analytics, advertising, AI or other services, and set no cookies. We do not sell or share data.
monday.com apps: Auto ID, Dates to Timeline, Item Checklist
These apps use monday.com's permission to read and write boards (boards:read, boards:write) and touch only what their job needs:
- Auto ID reads the ID column you choose on the board where the automation runs, and writes the new ID to that column. It keeps one counter per board, column and prefix (the last number it gave out and when the counter started) in monday.com's app storage.
- Dates to Timeline reads the date, number and timeline columns you choose on the item that changed, and writes the result to the column you choose. It keeps nothing.
- Item Checklist shows and saves the checklist of the item you have open, and, if you choose a Numbers column, writes the checklist's progress there. It keeps each item's checklist, each board's checklist template and the chosen progress column in monday.com's app storage. That storage is shared across your monday.com account and is not limited by board permissions, so don't put confidential text in checklist steps.
- Storage. monday.com's app storage is separated per account and per app. We can reach it only with monday.com's developer tools, and we use them only to delete data at your request or to look into a fault you ask us to fix.
- Logs. Auto ID and Dates to Timeline write one short technical log line per automation run to monday code's logs: which action ran, for which account number, and whether it succeeded, never board content. We read these logs to fix faults; monday.com deletes them on its own schedule.
- Uninstalling and deleting. Uninstalling an app stops it from running; what monday.com does with an uninstalled app's storage is set by monday.com. You can clear checklists yourself at any time from the item. To have an ID counter or saved checklists removed, write to us: within 30 days we will remove what monday.com's developer tools let us remove and tell you the result.
Apify actors: AI Crawler Access Checker, Website Screenshot
Both actors run on Apify's platform, in the account of the person who starts them. They read only public web pages at the addresses you give them, and they keep nothing of their own: everything they produce is saved in your Apify storage.
- AI Crawler Access Checker reads up to four small files from each site you list: robots.txt, llms.txt, llms-full.txt and the home page. It writes one result row per site (with a verdict for each AI crawler) to your run's dataset, plus a short report file (REPORT.md) in your run's key-value store.
- Website Screenshot opens each page you list in a headless Chromium browser and saves the screenshot or PDF file in your run's key-value store, one result row per page (address, status, file link, size, any error) in your run's dataset, and a short report file. It does not sign in, does not send cookies of yours and fills in no forms.
Both actors identify themselves with our crawler name in each request (SagnatoBot; earlier runs used VelquistBot), check robots.txt before opening each page you list, open one page per site at a time, and refuse addresses that name a private or local network (Website Screenshot also checks what each name points to). Like any browser, Website Screenshot also loads the images and scripts of the page it opens. Pages are requested directly from Apify's servers; neither actor uses Apify Proxy or any other proxy service. The sites you list see an Apify server address and our crawler name, not you.
No other third parties are involved and no AI service is called. We do not receive your input or your results, unless you choose to share a run with us through Apify. Apify shows us usage figures for each actor (such as the number of runs and users) and any issue you post on an actor's page, which we use only to keep the actors working and to answer you.
Your results stay in your Apify account for as long as your Apify plan keeps run storage, or until you delete them. To delete them sooner, delete the run or its dataset and key-value store in Apify Console (Storage). You can delete an issue you posted on the actor's page yourself, or write to us and we will ask Apify to remove it.
This website
sagnato.com has no cookies, no analytics and no forms. It is hosted on Cloudflare Pages, which handles your IP address to deliver the pages and keeps standard technical logs under its own terms.
Support emails
If you email us, we use your email address and message to answer you and to fix faults you report. Our legal basis is our legitimate interest in answering you. Mail to support@sagnato.com is handled by our email providers (a forwarding service and a mailbox). If they handle mail outside the EU/EEA, they rely on the EU's standard contractual clauses or an adequacy decision. We delete support emails no later than 24 months after the last message in the conversation.
Your rights
You can ask us for a copy of what we hold about you, ask us to correct or delete it, or object to how we use it, at support@sagnato.com. We reply within 30 days. Because the tools do not send us your content, there is usually nothing to hand over beyond the support emails you sent us. You can also complain to the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, imy.se).
For the data a tool handles inside a platform, the tool acts on your instructions, and the platform's own privacy terms apply to its storage and logs. We read those logs only to fix faults. For support emails, Isak Vidinghoff is the controller.
Changes
Changes to this policy are posted at this address with a new date.
Last updated: 20 November 2026