This is an earlier version (Version beab319fc240, 2026-11-20), kept for the record. It is no longer current. Go to the current version
Smart Knife privacy notice
Effective from: 2026-11-20. Version published for legal review. Plans are not currently available for purchase; sales will start only after legal review and payment configuration are complete. Information under Articles 13 and 14 of Regulation (EU) 2016/679 (the "GDPR"). The Polish version is binding. What changed since the previous version: section 15.
1. Controller
The controller of personal data is Smart Samurai, an entrepreneur entered in the CEIDG register (Krzysztof Kutniowski), ul. Stefana Czarnieckiego 23/13, 41-800 Zabrze, Polska, NIP 6482826410, REGON 540179995 (the "Seller", in this notice also the "Operator"). Contact on data matters: admin@smart-samurai.pl; support and complaints: knife-support@smart-samurai.pl, phone +48 572 042 069. The Seller has not appointed a data protection officer; [to be confirmed by the lawyer, given the scale of CV processing through AI features].
2. Where your data is
- The Service and Account data are stored on the Operator's private computer in Poland, not in a data centre: the Operator applies the safeguards in section 10, but cannot offer the physical protection and redundancy of professional hosting.
- The exception is the Account tables: Accounts (the data in the first row of the table in section 3), login sessions, MCP keys and AI provider profiles are kept in a database on a virtual server rented from netcup GmbH, Karlsruhe (DE), in its data centre, which acts as a processor (section 4). The Service on the Operator's computer reaches that database only through an encrypted tunnel (WireGuard, and TLS inside it); the database is not reachable from the internet. It is kept on an encrypted volume (LUKS, AES-256) whose key is not stored on that server: the Operator's computer unlocks it. Passwords are stored there only as hashes, sessions and MCP keys only as hashes of the token, and AI provider API keys only encrypted: the key that decrypts them stays on the Operator's computer in Poland. A copy of the database is kept on the Operator's own server in Poland. Account files (below) do not leave the Operator's computer.
- Account files (CV data, documents, files saved from the Craft apps, conversations, drafts, workflows with their run history and credentials, the repository connection) are stored encrypted (AES-256-GCM, a separate key per Account). AI provider API keys and workflow credentials are encrypted and never shown in full again after saving. The encryption key is on the same computer, so the Operator, as the server's administrator, is technically able to access the data. The Operator does not look at it. The only exception at your initiative is a support request: when you ask for a problem to be fixed or for help using the Service, the Operator may look at the data the request concerns, only as far as needed. Otherwise only where the law requires it (for example a court or authority order).
- Workflows run on the Operator's server, each run in a separate, isolated process. A workflow sends data only where its nodes say: to the addresses and services you entered in it (for example an HTTP request or an integration), using the credentials you saved, and to the AI provider of an AI node. Those recipients act under your relationship with them (section 4).
- Craft apps (where this instance offers them): third-party open-source programs by the ArtCraft team (PhotoCraft, VectorCraft, FilmCraft and others) that the Operator serves unmodified from its own server, on a separate address. They run entirely in your browser: your work stays in the browser's storage for that address (section 6) until you save it to your Account as a Craft file. Nothing is sent to the ArtCraft team. To keep the apps up to date, the server asks GitHub for new releases of the apps; those requests carry no data about you.
- netcup GmbH, Karlsruhe (DE) also relays outgoing Service e-mail; Account files (CVs, documents, conversations and other content) are not stored there. For e-mail it receives the recipient address, the Service-generated transactional message (for example, an Account name or one-time confirmation/reset link, depending on the message), and delivery metadata needed to send it. CVs, documents, AI conversations and other Account content are not sent there. The connection to the relay is always encrypted (TLS), and onward to the recipient's mail server whenever that server supports it. The relay does not keep messages once delivered; its log holds the recipient address, time and delivery status (no subject or body) and is deleted after 30 days.
- A site screenshot requested by the assistant is rendered on the server in a browser. During rendering, the image is temporarily written to the job's scratch directory, which is removed when the job completes; it is not added to your Account files or kept as an Operator copy. The result is cached in server memory for up to 30 minutes so it can be passed to the AI provider you chose. The Operator does not view screenshots. The browser also fetches resources embedded by the page (such as images, fonts and scripts) from their hosts.
- Backups, where they are made, are kept on the Operator's own storage in Poland and are overwritten after 30 days. Data you delete (also together with your Account) is gone from the backups at the latest after that time; until then backups are used only to restore the Service after a failure.
3. What data, why, on what basis, and for how long
| Data | Purpose | Basis (GDPR) | Retention |
|---|---|---|---|
| Username, display name, e-mail address, password hash (scrypt), role, status, creation and last-login dates, storage limit, date and version of accepting the Terms, chosen interface language, the release notes and edition of these texts you last confirmed in the "What's new" window | creating and running your Account | Art. 6(1)(b) (contract) | until the Account is deleted; an unconfirmed registration 24 hours |
| Login sessions (token hash, created, expiry and last-used times), a known-device marker | keeping you signed in, protecting the Account against takeover | Art. 6(1)(b) and (f) | session up to 30 days or until you log out; device marker up to 180 days |
| Content: CV profile and versions (including a photo), job offers and applications, documents (with versions and trash), files you save from the Craft apps, AI assistant conversations (with the provider address and model of the latest answer), saved assistant tasks (title, goal, steps, next step, progress notes), course progress, website/repository connection (repository, branch, the GitHub token and, if you connect Vercel, the Vercel token and the project's preview bypass secret, audit history), tool drafts | providing the services you ask for | Art. 6(1)(b) | until you delete it or delete the Account; document trash 30 days |
| Workflows: their nodes, settings, triggers (schedules, webhook addresses) and notes; data tables and the data a workflow keeps between runs (such as an AI agent's memory or items already seen); resume links of waiting runs | running the automations you build | Art. 6(1)(b) | until you delete the workflow or the Account |
| Workflow run history: when and how a run started, each node's input and output data (shortened for large outputs), errors, duration | showing you what your workflows did, finding mistakes | Art. 6(1)(b) | the last 100 runs of each workflow, at most 14 days; you can delete runs earlier |
| Workflow credentials: name, type and secrets (API keys, passwords, tokens, the client id and secret of OAuth apps you registered, the tokens those apps issue) | letting your workflows reach the services you chose | Art. 6(1)(b) | until you delete the credential or the Account; given to a run only for the nodes that use it |
| Requests to your workflows' webhook addresses: headers (including the caller's IP address and browser as passed on by the reverse proxy; cookies are removed), query parameters, body and files | starting the workflow with the data the caller sent | towards you Art. 6(1)(b); towards the caller Art. 6(1)(f) (providing the service the User set up) | as run history |
| AI provider settings (one or more named profiles: address, model, encrypted API key, whether the model sees images), the assistant's turn limit, MCP keys (hashes only, full or read-only) | the AI assistant, AI nodes in workflows, and your programs' access to the Account (a program with your key can read what the key allows, including your assistant conversations and tasks) | Art. 6(1)(b) | until changed, revoked or the Account is deleted |
| Site screenshots requested from the assistant and their embedded resources (e.g. images, fonts, scripts) | show you the site and send its image to the AI model chosen in the assistant or MCP client | Art. 6(1)(b) | working file in a temporary job directory, removed when the job completes; result in memory up to 30 minutes; no copy in Account files |
| Usage counters (such as model tokens used by the assistant and by AI nodes) | fair sharing of resources, limits | Art. 6(1)(b) and (f) | until the Account is deleted |
| Data from GitHub when you sign in with GitHub: GitHub id and login, the name on your profile, your verified e-mail address; the installations and repositories you can access | signing in, linking the Account, the website studio | Art. 6(1)(b) | until you unlink GitHub or delete the Account |
| Security events: event type, account name, IP address (for IPv6 the /64 prefix), time | security of the Service, detecting abuse and attacks | Art. 6(1)(f) (legitimate interest: network and information security, recital 49) | 30 days |
| Rate-limit and block counters (IP address, number of requests) | protection against overload and abuse | Art. 6(1)(f) | in server memory, minutes to hours |
| Technical logs: the server's own log files (server output, operations on add-on services, updates; secrets are removed before writing), and the logs of the mail server and the reverse proxy (IP address, time, page address, browser, status; for mail the recipient address and delivery status) | operating and securing the Service, fixing faults | Art. 6(1)(f) | up to 30 days |
| E-mails sent to you (recipient address and generated transactional content, such as an Account name or one-time link) | confirming the address, password resets, security and change notices | Art. 6(1)(b) and (f) | messages are relayed only to deliver them; delivery logs as above; an address that bounces is blocked for 30 days (stored only as a hash) |
| Correspondence with the Operator, complaints, notices of illegal content | handling them, DSA obligations, defending against claims | Art. 6(1)(c) (DSA) and (f) | until the matter is closed, then until claims are time-barred |
| Addresses of pages you ask to fetch (job offers, company sites) or audit | carrying out the requested feature | Art. 6(1)(b) | with the offer or the audit history |
| Orders and payments: order number, plan, amount, payment method, dates, status, transaction identifiers at Tpay; invoices, purchase confirmations and corrective invoices with the invoice details given and the e-mail address | concluding and performing the contract, issuing and keeping invoices, tax settlements | Art. 6(1)(b) and (c) (Tax Ordinance, VAT Act) | as a rule 5 years from the end of the tax year in which the obligation arose; after Account deletion with the Account identifier replaced by an unreadable hash, while the details on issued documents stay unchanged |
| Statements and evidence: acceptance of the Terms, acknowledgement of the AI notice (§ 5a), the statement when ordering – version, date and time | demonstrating compliance, defending claims | Art. 6(1)(c) and (f) | until the limitation periods for claims expire |
| Per-request AI usage logs, without content: time, Account, plan, provider, model, number of tokens, cost | metering the AI allowance, handling disputes and withdrawals, abuse | Art. 6(1)(b) and (f) | 1095 days |
| Free AI tries: a keyed hash of the e-mail address (an HMAC value that cannot be reversed without a key held on the server) and the number of tries used; IP prefix for the limit | enforcing the one-off limit on tries, preventing abuse | Art. 6(1)(f) (legitimate interest: protection against creating Accounts to obtain free resources) | 1095 days from the last use, also after Account deletion; IP prefix up to 30 days |
The Operator does not use your data, your conversations with the AI assistant, your files or the work you do in the Service for marketing, profiling or training AI models, and does not sell, rent or share them with anyone for marketing; nor does it sell or share e-mail addresses (address lists). Your e-mail address is used only for messages about your Account, Plan and payments. Tools that run in the browser send data to the server only when the tool must compute there (for example OCR); the working files are deleted when the job ends.
4. Recipients
- OpenRouter, Inc. (USA) and the model hosts named in § 5a – processors of the AI features (§ 5a).
- Krajowy Integrator Płatności S.A. (Tpay), plac Andersa 3, 61-894 Poznań – the operator of BLIK and instant transfer payments. With an order the Operator passes to Tpay: the e-mail address, the Account name, the IP address and browser information (user agent), the amount, description and number of the order and the bank chosen; from Tpay it receives the transaction's identifier and status (notifications, and when a notification does not arrive, a query about the transaction's status). Tpay acts as a separate controller of the payer's data: it executes the payment, meets its own legal obligations (including anti-money-laundering) and handles payment complaints; Tpay's data protection officer: iod@tpay.com (Tpay information notice). Basis for passing the data: Art. 6(1)(b) GDPR (performing the Plan contract).
- The Seller's accounting office or tax adviser, if used – a processor or separate controller for accounting documents.
- netcup GmbH, Karlsruhe (DE): the provider of the virtual server that hosts the database of Account tables (Accounts, login sessions, MCP keys and AI provider profiles, section 2) and relays outgoing Service e-mail. It stores those tables in its data centre (passwords, session tokens and MCP keys as hashes, AI provider API keys encrypted with a key it does not hold) and, to deliver a message, receives the recipient address, the generated transactional message (which may contain an Account name or a one-time link), and technical delivery metadata. It does not receive Account files such as CVs, documents or AI conversations. It acts as a processor (Article 28 GDPR).
- The AI provider you chose: when you use the AI assistant, the Service sends, at your request, the conversation and data from open tools to the address configured in your Account. If you request a screenshot in the assistant, its image (or, depending on settings, a description) goes to the AI provider configured for the profile you chose. If you request a screenshot through MCP, the image is returned to your MCP client, and further recipients depend on the AI provider configured in that client. In neither case is the image sent to the Operator or the Operator's AI model as a recipient. When you ask the Service to detect whether a model sees images, it sends that model one small generated test picture (two coloured halves, nothing about you); the answer (the provider's address, the model name, whether it saw the picture and when it was checked) is kept for 30 days in a list shared by all Accounts that does not record who checked. The Operator does not view screenshots or keep copies; during rendering, a working file is stored in the temporary job directory and removed when the job completes, and the result is cached in server memory for up to 30 minutes. When a workflow runs an AI node, the data that node is given goes to the provider of the profile or credential the node names. The provider processes it under your contract with them and their own privacy policy, not on the Operator's behalf. Do not send it other people's data you have no right to share.
- Addresses and services your workflows contact: an HTTP request or integration node sends what the workflow gives it to the address in the node, with the credentials you saved; when you connect an OAuth app, the provider of that app (for example Google, Microsoft or GitHub) takes part in the sign-in. These recipients act under your relationship with them, not on the Operator's behalf. Whoever calls your webhook address receives the answer your workflow gives.
- Vercel Inc. (USA): only if you connect Vercel in the website studio: with your token the server reads your Vercel project and its deployments and build logs, and starts preview builds of the work branch; Vercel acts as an independent controller for your Vercel account (Vercel privacy policy).
- GitHub, Inc. (USA): when you sign in with GitHub and work with a repository; GitHub acts as an independent controller for your GitHub account (GitHub privacy statement). The Craft app update checks (section 2) also go to GitHub, without data about you.
- Google LLC (USA): when you audit a site with PageSpeed Insights, the address of the audited site is sent there (from the Operator's server, without your IP address).
- Sites you point the Service at (job offers, company sites, audited sites, project previews, GitHub Pages, and addresses your workflows call): they see the IP address of the Operator's server, not yours. For a screenshot, the server browser also fetches resources referenced by the page (such as images, fonts, scripts and API requests); their hosts see this IP address too.
- Public authorities: only where the law requires it.
5. Transfers outside the European Economic Area
GitHub, Google and Vercel are based in the USA. Transfers rest on Commission Decision (EU) 2023/1795 on the EU-US Data Privacy Framework where the recipient is certified under it, and otherwise on standard contractual clauses. The recipients of the AI features are described in § 5a. For an AI Provider chosen by the Service's administrator (own key) or services connected by workflows, Art. 49(1)(b) GDPR applies where the transfer is necessary to carry out your instruction.
5a. AI features and transfers outside the EEA
Basis and scope. The AI features in a Plan and Free AI tries work only through paid AI services outside the EEA, so we send them what you give them: the conversation, documents and data from tools you open. We mainly use models of the DeepSeek family (open-weight models), hosted by the providers in the table below, not by DeepSeek in China; we may use another model or provider when it works better, faster, cheaper or more reliably, but only one from this table. A CV contains personal data. Do not paste special categories of data (health, opinions, beliefs), national ID or document numbers, other people's data without the right to share it, passwords or keys. The legal basis is Art. 6(1)(b) GDPR (performing the contract); before the first use of AI you acknowledge a separate notice, whose version and time we record.
Recipients and transfer bases (Chapter V GDPR):
| Recipient | Role | Country | Transfer basis |
|---|---|---|---|
| OpenRouter, Inc., 169 Madison Avenue, New York, NY 10016 | processor, intermediary routing requests; an independent controller only for its own legal obligations (detecting and reporting CSAM) | USA | standard contractual clauses, Module 2 (Art. 46(2)(c)), incorporated in the OpenRouter data processing agreement (DPA) |
Wafer, InferenceNet, CoreWeave, Baseten, Fireworks AI, Venice (only these, named in the only configuration) |
further processors hosting the model | USA | standard contractual clauses through OpenRouter (SCC clauses 8.8 and 9) |
| Anthropic, PBC (backup provider, only when OpenRouter is unavailable) | processor | USA | Decision (EU) 2023/1795 if certified, and otherwise standard contractual clauses in the contract with Anthropic |
What recipients do with the data. OpenRouter deletes content after generating the answer, and traffic goes only to providers marked in OpenRouter as not retaining content (ZDR, only with zdr: true and data_collection: "deny"). OpenRouter does not train on this content and keeps metadata (token counts, latency). OpenRouter may screen content for child sexual abuse material and retain content flagged for that purpose. Providers may hold fragments briefly in a cache. Anthropic may keep content for a short time (normally up to 30 days) for safety, without training on it. Providers not on this list do not receive your data; changing the list requires a new edition of this notice and your renewed acknowledgement.
What we do not guarantee. AI output can be wrong; we make no automated decisions about you (point 11).
6. Cookies and browser storage
The Service stores on your device only information that is strictly necessary to provide the service you ask for (Article 399(3) of the Polish Electronic Communications Law), so it does not ask for consent. There is no analytics, no advertising and no third-party script.
| Name | Kind | Purpose | Lifetime |
|---|---|---|---|
knife_session |
cookie | keeping you signed in | up to 30 days |
knife_device |
cookie | recognising a device you signed in on before (protection against account takeover) | up to 180 days |
knife_gh_state |
cookie | securing "Sign in with GitHub" | 10 minutes |
knife_vercel_state |
cookie | securing "Connect with Vercel" in the website studio | 10 minutes |
knife_office |
cookie on the office editor's address (where offered) | letting your browser load the editor for your document | up to 6 hours |
knife_craft |
cookie on the Craft apps' address (where offered) | letting your browser load the Craft apps | up to 12 hours |
knife_lang |
cookie | the interface language you chose with the switch (Polish or English) | 1 year |
| the Craft apps' own storage (preferences, photo libraries, projects and media, recovery copies of open documents) | local storage, IndexedDB, OPFS on the Craft apps' address | the apps working in your browser | until you clear it in the browser; never sent to the server |
knife:account |
local storage on the Craft apps' address | an opaque marker of the Account that used the apps last in this browser, so another Account's local data is cleared before the apps open | until you clear it in the browser |
sk-theme, tool settings |
local storage | light or dark theme, your tool settings | until you clear it in the browser |
samurai-knife:showcase:v1 |
local storage | whether tool cards open a tool's description page first or the tool straight away, and for which tools you chose not to see that page again | until you clear it in the browser; never sent to the server |
| a copy of the AI assistant conversation, the message queue, trust mode, SQL settings | local storage | running the assistant and the tools without reloading | removed when you log out |
You can delete these in your browser settings; without the session cookie you cannot sign in.
7. Your rights
You have the right of access to your data and to a copy, to rectification, erasure, restriction of processing, data portability, and to object to processing based on legitimate interest (Articles 15–21 GDPR). You can delete your Account and all its data yourself in the Account settings, and parts of it where they are shown: documents and Craft files ("My files"), workflows, their runs and credentials (in the workflow editor). Send any other request to admin@smart-samurai.pl. The Operator answers without undue delay and within one month at the latest. If you sent data to a webhook address of another User's workflow, you can also ask that User; the Operator helps where the User does not answer.
8. Complaint to the supervisory authority
You have the right to lodge a complaint with the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych), ul. Stanisława Moniuszki 1A, 00-014 Warszawa, Poland (uodo.gov.pl).
9. Do you have to provide data
A username, an e-mail address and a password (or signing in with GitHub) are required to create an Account. Payment details are voluntary, but a Plan contract cannot be concluded without them. Invoice details (a name, an address, a NIP only for a business) are optional: without them you get a purchase confirmation instead of an invoice, and you can ask for the invoice within 3 months. Everything else you provide voluntarily when you use the features you choose; an AI provider API key is only needed for the AI assistant and for AI nodes.
10. Security and breaches
Connections are encrypted (HTTPS; between the Service and its database a WireGuard tunnel with TLS inside), Account files, API keys and workflow credentials are encrypted, passwords are stored as hashes, the server is protected by a firewall and limits, and the tools that process files run in an isolated environment (sandbox). Workflows run in a separate process without access to the server's files or to other Accounts; code you write in a workflow runs in a further sandbox with time and memory limits, and on the public Service workflows cannot reach addresses in the Operator's private network. The Craft apps run on their own address, separate from the Service, so they cannot read your Account. If there is a personal data breach, the Operator notifies the Personal Data Protection Office within 72 hours where required and, if the risk to you is high, tells you without undue delay.
11. Automated decisions
The Operator makes no decisions based solely on automated processing, including profiling, that produce legal effects for you or similarly significantly affect you. Automatic limits and blocks against abuse are temporary and do not assess you as a person. Workflows do what their User built; the Operator does not use them to decide anything about you.
12. Age
The Service is intended for people aged 16 or older.
13. Special-category data and other people's data
A CV may contain special categories of data (such as health or disability) and other people's data (such as references), and a workflow may handle other people's data (such as messages or form entries it receives or fetches). Store and process them only when needed and when you have the right to.
14. Changes
The Operator announces material changes to this notice by e-mail and in the Service, in the same way as changes to the Terms.
15. Versions of this notice and of Smart Knife
Every change of the text or of the instance's details is a new version. The bottom of this page shows its edition, its fingerprint (a short code computed from the full text) and the Smart Knife version the server runs; earlier versions are listed there and stay readable. Your Account settings show the version you accepted at sign-up.
What each version of Smart Knife added that matters for your data:
| Smart Knife version | Added | What it means for your data |
|---|---|---|
| 0.1 | Accounts, browser tools, CV studio, office documents, database course, website studio, AI assistant, MCP keys, sign-in with GitHub | as described in edition 1 of this notice |
| 0.2 | The server's own log files; the Craft apps | technical logs kept up to 30 days; the apps keep your work in your browser |
| 0.4 | Automatic updates of the Craft apps from GitHub | requests to GitHub without data about you |
| 0.5 | Craft files: saving work from the Craft apps in your Account | stored encrypted in the Account, counted in the storage limit |
| 0.6.1 | Several named AI provider profiles | each profile's API key stored encrypted |
| 0.7.0 | Workflows: automations with schedules, webhook addresses, code and credentials | workflows, run history (100 runs, 14 days), encrypted credentials, data sent to your webhooks |
| 0.7.1 | AI nodes in workflows; the assistant and MCP can build and run workflows | workflow data goes to the AI provider you chose; token use is counted |
| 0.8.0 | Versions of the Terms and this notice: earlier versions stay readable | the version you accepted is shown in your Account; no new personal data |
| 0.10.0 | The interface in Polish and English | the language you choose is kept in the knife_lang cookie and on your Account; e-mails come in that language |
| 0.13.0 | Optional Vercel connection and site screenshots for the assistant | your Vercel token and project bypass secret are encrypted; the server browser fetches the page and resources; the working file is deleted after rendering and the result goes only to the AI provider you chose; the Operator does not view it, and the result stays in server memory for up to 30 minutes |
| 0.13.0 (later builds) | Detecting whether a model sees images; a turn limit for the assistant | a generated test picture goes to the AI provider you chose; the answer is kept per provider address and model, without who checked; the turn limit is kept on your Account |
| 0.14.0 | Polish as the default language; a description page for every tool | without a choice of yours the Service is shown in Polish (English when your browser asks only for English); how tool cards open is kept in your browser's local storage only; the description pages are public and read no Account data |
| 0.15.2 | The Account tables move to a database on a rented virtual server | Accounts, login sessions, MCP keys and AI provider profiles are stored by netcup GmbH, Karlsruhe (DE) as a processor, reached through an encrypted tunnel; passwords, tokens and keys stay hashed or encrypted; a copy is kept on the Operator's server in Poland; retention unchanged |
| 0.16.0 | Paid Plan and Free AI tries | orders and payments, AI usage logs without content, a keyed hash of the e-mail address, new recipients of AI features outside the EEA (§ 5a) |
| 0.17.1 | Payments through Tpay: choosing a bank for an instant transfer, checking a payment's status at Tpay | Tpay also receives the bank chosen; when a payment notification does not arrive, the Service asks Tpay for the transaction's status and records the time of the query on the order; no new categories of data |
| 0.13.0 (later builds) | Saved assistant tasks; a "What's new" window; programs you connect with your MCP key can read your assistant conversations | tasks are stored encrypted in the Account and counted in the storage limit; the Account keeps which release notes you saw; each conversation keeps the provider address and model of its latest answer; nothing goes to a new recipient |
Changes:
- Edition 12 (2026-11-20, Smart Knife 0.17.1): section 4 now states which data the Operator passes to Tpay and receives from it, the purpose and basis, and how to reach Tpay's data protection officer.
- Edition 11 (16 November 2026, Smart Knife 0.16.0.22): no changes to this Privacy Notice; the Terms only clarify the VAT-exemption statement by removing an unconfirmed statutory basis.
- Edition 10 (16 November 2026, Smart Knife 0.16.0): the Service is run as a business; adds orders and payments, statements, AI usage logs, Free AI tries (a keyed hash of the e-mail address for 1095 days), Tpay as a separate controller and a new § 5a naming the recipients of AI features and the bases for transfers outside the EEA.
- Edition 9 (5 November 2026, Smart Knife 0.15.2): the Account tables (Accounts, login sessions, MCP keys, AI provider profiles) are kept in a database on a virtual server of netcup GmbH, Karlsruhe (DE), a processor, reached through an encrypted tunnel, with a copy on the Operator's own server in Poland (§ 2, § 4, § 10); retention periods unchanged.
- Edition 8 (4 November 2026, Smart Knife 0.14.0): adds the
samurai-knife:showcase:v1local storage entry (how tool cards open) to § 6 and describes Polish as the default language. - Edition 7 (30 October 2026, Smart Knife 0.13.0): adds saved assistant tasks to the content, which release notes you last saw to the Account data, the provider address and model of a conversation's latest answer, and that a program you connect with your MCP key can read your assistant conversations and tasks.
- Edition 6 (29 October 2026, Smart Knife 0.13.0): adds the assistant's turn limit and the vision flag to the AI provider settings, and describes vision detection: a generated test picture sent to the AI provider you chose, and the shared list of answers that does not record who checked.
- Edition 5 (28 October 2026, Smart Knife 0.13.0): describes site screenshots: the server fetches the page and its resources, a temporary working file is removed when the job completes, the result is cached in memory for up to 30 minutes, sent to the AI provider you chose, and not viewed by the Operator.
- Edition 4 (28 October 2026, Smart Knife 0.13.0): adds the optional Vercel connection of the website studio (Vercel token and bypass secret, Vercel as a recipient) and the
knife_vercel_statecookie. - Edition 3 (26 October 2026, Smart Knife 0.10.0): adds the interface language to the Account data and the
knife_langcookie. - Edition 2 (22 October 2026, Smart Knife 0.8.0): describes the Craft apps and Craft files, workflows (run history, credentials, webhooks, AI nodes), several AI provider profiles, the server's log files and the
knife_office,knife_craftand Craft app storage entries; adds this section. - Edition 1 (21 October 2026, Smart Knife 0.1): first version.