SupplyFolio client-portal privacy notice
Version sf-2026-11-16-v1. Publication and effective date: 16 November 2026.
Who is responsible
Martin Trnka, sole trader trading as SupplyFolio, Mateja Bela 3461/76, 010 15 Žilina, Slovak Republic, IČO 44970307, is the controller for account administration, billing, security and our own support records described below. Contact us at m.trnka@supplyfolio.com for privacy questions or requests.
Your business normally controls personal data it chooses to put in product and supplier evidence. For that data, we act on its instructions under the Customer data-processing terms. The business decides the lawful purpose and who may access or receive an export. If a supplier or employer put your details in a workspace, contact that business first; we can help route a request. A sign-in account and the same person's actions recorded in customer evidence can involve these different roles.
This notice covers the client portal and related account, billing and service communications. The public marketing website's enquiries and optional analytics have a separate notice. Hosted Stripe pages also have their own privacy information.
Information we handle and why
| Information and source | Purpose | Basis where SupplyFolio is the controller |
|---|---|---|
| Email, password hash, account identifier, verification status and account dates, provided by you or created during registration | Create and secure your account; verify email and recover access | Contract necessity for an individual customer; legitimate interests in administering business access for a customer's representatives |
| Company and membership details, invitations, role and action records, provided by workspace members | Give the authorised people the correct access and keep workspace administration accountable | Legitimate interests in delivering and securing the business service; customer-directed evidence/reviewer records are processed for the customer |
| Name, billing address, tax details where required, payment status, customer/subscription/invoice identifiers, amount and period, from you and Stripe | Process subscriptions, issue or reconcile invoices, handle payment problems and keep required records | Contract necessity for an individual customer; legitimate interests for business billing contacts; legal obligations for required tax and accounting records |
| Network address, browser information, session activity, authentication events and technical error or security records, generated during use | Maintain access, prevent abuse and investigate faults or incidents | Legitimate interests in service security and reliability |
| Your support correspondence and contact information | Answer requests, investigate problems and document their resolution | Contract necessity where you are the customer; otherwise legitimate interests in supporting the business service and resolving claims |
| A minimal record of terms versions and subscription acceptance | Show the applicable contractual terms and investigate a dispute | Legitimate interests in evidencing the agreement and protecting legal rights |
Our legitimate interests are to operate a secure business service, communicate with the people authorised to use it, and resolve genuine disputes. They do not automatically override your interests or rights. You may object as explained below. A company's contract is not treated as consent from its employees or supplier contacts.
You need to provide an account email and required checkout details to use paid features. Without them we cannot authenticate you or complete the relevant purchase. Support details are necessary only to the extent needed to handle your request. We do not use service communications to enrol you in marketing.
Customer evidence can include names, business contact details, signatures, document authors, reviewer identities, and other information contained in uploaded files or source quotations. We do not automatically anonymise documents. The customer must limit uploads to relevant information it may lawfully provide; sensitive personal records are outside the intended service.
AI document processing
When a member requests AI extraction, we send the selected original document and the relevant product name, SKU and page context to OpenAI. The original can include personal data even when those details are not separately entered in our form. The result returns to the customer's workspace for human review. It is not an automated legal or similarly significant decision about an individual, and this feature must not be used to make such decisions.
We use the selected standard OpenAI Global API service, sending documents inline with ordinary response storage and optional training sharing disabled and without separate Files API uploads. This is not EU-only processing or Zero Data Retention. OpenAI may keep content and metadata in safety logs for up to 30 days from the request, with longer legal or safety exceptions, including manual review of flagged inputs. Short-lived model caching may also occur. Deleting your workspace does not itself erase these provider records. OpenAI data controls.
The selected Global route may process data outside the EEA. The standard API Services Agreement incorporates OpenAI's DPA by reference; those standard terms do not require a separate DPA signature. For an EEA customer they name OpenAI Ireland Ltd. and describe onward-transfer safeguards. We keep the applicable terms and transfer information available through the privacy contact. The 14-day hosting-backup deadline does not shorten OpenAI retention. On a valid earlier workspace-deletion instruction we stop further AI processing for that workspace and carry out our return/deletion procedure; this does not itself erase OpenAI safety records. We assist with valid requests through the provider's available privacy/support procedures, without promising earlier provider-log erasure. Our confirmations distinguish completed workspace deletion, pending provider retention and unresolved exceptions. Ordinary safety retention is not automatically a statutory storage exception, and mandatory data-protection rights remain unaffected. Our selected standard EEA customer route is with OpenAI Ireland Ltd. under the applicable API agreement and incorporated DPA. OpenAI Services Agreement, DPA.
Recipients and international processing
Access is limited to authorised workspace members, authorised service personnel and the providers needed for the stated purposes. We do not sell your personal data or make customer evidence public.
| Recipient | Information and role |
|---|---|
| Websupport s.r.o., IČO 36 421 928, under its published processing terms | Existing paid host for Martin Trnka's application, database, private files, recovery copies and service email. Published production location is Perpetuus, Bratislava, Slovakia, with backups in another Bratislava datacentre. Recovery is controlled and manual. Its onward-provider arrangements use section 16.11.1 and the linked recipient list for the relevant stated purposes, as described in Schedule B of the data-processing terms. Provider terms, datacentres, recipient information. |
| OpenAI | Selected document content and product context for requested AI extraction using the standard Global route above, under the applicable OpenAI agreement/DPA. Processing may occur outside the EEA; the provider's separate retention and account/current-control confirmation and request assistance are stated above. |
| Stripe | Checkout and subscription data, payment and billing details. Card details are entered on Stripe's hosted pages, not in a SupplyFolio card form. Stripe has processor and controller roles for different purposes, including payment services, fraud prevention and its own legal obligations. Stripe privacy information. |
| Authorities and professional advisers, where necessary | Limited records required by law or needed for accounting, a specific legal claim or professional advice, under appropriate duties of confidentiality |
The detailed list for processing customer evidence and the procedure for subprocessor changes, objections and necessary audits appear in the data-processing terms. Our direct provider changes receive 30 days' advance notice; onward changes by existing providers follow their published procedures and are relayed directly without undue delay, without a uniform 30-day advance guarantee. We may receive details from an inviting colleague, the workspace owner, Stripe, or your business's uploaded records, as well as directly from you.
Some provider processing may occur outside the European Economic Area. OpenAI's standard EEA DPA describes SCC/adequacy safeguards for onward transfers; its selected Global route is not EEA-only. Websupport's published production/backup locations are stated above; physical location alone is not a promise that every onward provider's access is EEA-only. Its published recipient/transfer information and section 16 arrangements apply to the relevant processing. Stripe's separate payment roles follow its linked privacy information. You can request the applicable safeguards at m.trnka@supplyfolio.com. A data-processing agreement alone is not a substitute for an applicable international-transfer safeguard.
Retention and deletion
The following rules apply to our working systems and the separately identified recovery and provider records. The selected periods are maximums or defined disposal criteria; the relevant process must remove the record by its deadline, subject only to a documented applicable exception.
| Category | Retention rule |
|---|---|
| Customer workspace evidence, originals, catalogue and review records | Available while paid access is valid, followed by 30 days (720 hours) of reading/download/export access. Working data is then deleted. An owner's valid earlier deletion request closes access and starts deletion sooner. |
| Hosting recovery-backup copies of deleted workspace data | Expire within at most 14 days (336 hours) after working-data deletion. This assurance relies on Websupport's documented daily 14-day database/file rotation applied to the selected hosting scope, with actual capture and recovery verified; it is not a claim of physically observed erasure of each internal copy. We remove our own archives, requested backup bundles and temporary restores. Recovery must verify originals and reapply completed deletions and current access restrictions before access is reopened. |
| OpenAI safety records | Separate from workspace and hosting deletion: the selected Global policy described in the AI section, generally up to 30 days from the API request, with the stated legal/safety exceptions and request-assistance limits. |
| Accounts closed on request | Revoke sign-in access when the verified closure is accepted; remove account email, password hash and recoverable authentication data within 30 days. If the account still owns an active workspace, arrange transfer or workspace closure first and explain any necessary delay. Keep only the separately justified records below; do not erase another user's workspace or its required review history merely by closing one account. |
| Unverified and inactive accounts | Delete an unverified account 30 days after registration if it has no accepted workspace membership or payment. For a verified account with no active or read/export workspace membership, subscription or unresolved payment, delete 12 months after the later of its last sign-in and the date it first meets those cleanup conditions; email notice 30 days before deletion. A new sign-in or qualifying workspace relationship resets the relevant clock. This does not prevent an earlier account-closure request. |
| Invitations and one-use authentication records | Remove an invitation's email and token record within 30 days after acceptance, revocation or expiry. Remove used or expired password-reset and email-verification token records within seven days; their validity ends on use or the stated expiry, not at the later cleanup date. Active membership and necessary security events have their own rules. |
| Server sessions | A two-hour access timeout; remove an expired or revoked server-session record within 24 hours. This requires scheduled cleanup and is distinct from the current timeout setting. |
| Routine technical and delivery logs | Remove application errors, hosting access/error logs processed for us, worker diagnostics and mail-delivery logs within 30 days of the event. Do not include full document content, passwords or usable authentication tokens. |
| Security events | Retain minimal sign-in, access-denial and privileged-action security records for 90 days from the event. Isolate only records needed for an actual incident or claim under the exception below. Workspace review history follows workspace retention rather than this log deadline. |
| Raw incoming Stripe event records | The current application minimises raw billing payloads after 144 hours. The smaller payment/invoice records follow the next row; this is not Stripe's own retention period. |
| Minimal payment and contract-acceptance evidence | Retain the minimum identifiers, amounts, paid periods, accepted versions/hashes and timestamps for four years after the relevant agreement ends, then remove them within 30 days. Remove the initiating-user link when its workspace is deleted. This is our selected contract-record period, not a claim that all statutory deadlines are four years. A record actually required for tax/accounting follows the next row; it does not justify keeping the full payment payload or source documents. |
| Required tax records | We use the Slovak flat-rate-expense regime. Keep the required income/receivables records and supporting evidence until the right to assess or reassess the relevant tax has expired, including a documented extension or proceeding. Separately, keep cross-border service invoices covered by section 72(2) of the VAT Act and received invoices for which we must account for VAT for ten years following the year concerned. Remove each required record within 30 days after its applicable period and any documented hold end. This does not extend retention of customer evidence or justify keeping the full payment payload. |
| Minimal deletion record | Keep only the workspace identifier, deletion cutoff/status and integrity evidence needed to prevent restoration. Retain it while any copy capable of recreating that workspace remains recoverable, including provider, archive and temporary restore copies, and for 90 days after the last such copy is verified expired or destroyed. For routine provider snapshots, recorded rotation and capture-scope evidence can support expiry assurance; our own copies require separate removal. Review this need monthly and investigate any unexplained or longer-lived copy. Verification keys remain usable for every retained record that depends on them. |
| Support correspondence | Remove the correspondence within 12 months after the last substantive contact. Remove customer evidence attachments within 30 days of case closure, sooner if no longer needed; a continuing dispute uses the documented exception below. Keeping an attachment for support does not extend its workspace retention without a separate lawful reason. |
| Routine service-email copies | Remove authentication, invitation and reminder email copies from service mailboxes within 90 days of sending. Mail-delivery logs use the 30-day rule. Billing messages and support conversations follow their specific rows instead. |
The working-record deadlines above include removal from ordinary mail folders and Trash; archiving or moving a message to Trash is not deletion. Provider-owned mailbox recovery is separate from the workspace database/private-file 14-day policy. Websupport documents daily backups with five available restore points and a separate Expunged recovery folder, without a combined maximum elapsed lifetime. For those recovery copies, the retention criterion is replacement of the relevant restore point through the provider's rotation and expiry or removal of the corresponding deleted-message recovery entry. We use the published recovery process and any recorded expiry information, without promising an unestablished number of days. Mailbox recovery.
After working deletion, we exclude these recovery copies from ordinary use, keep no separate copy to extend their life and reapply deletions before restored mail is used. We record the known recovery scope, deletion date and pending expiry status and review unresolved cases monthly. We remove copies under our control without undue delay and use available provider procedures for valid erasure instructions or unexplained continued recovery. Unknown expiry is not permission for indefinite retention or an automatic legal exception. A deletion response distinguishes completed working deletion from any provider recovery that remains pending; it does not claim all copies have gone. These criteria do not extend the working-record deadlines or remove mandatory rights. Providers' own controller records and OpenAI safety retention remain separately described.
A genuine incident, claim, proceeding or legal duty can require a limited exception. We identify the affected records, reason, responsible person and next review date; review at least every 90 days; and remove the exceptional copy within 30 days after the reason and any applicable legal hold end. We do not retain an entire account or evidence collection because one invoice or incident record is needed. We explain the applicable exception when responding to deletion requests, unless law prevents disclosure. Your workspace export is not necessarily a complete personal-data access response.
The seller confirmed the flat-rate-expense regime on 13 November 2026. It requires limited tax evidence rather than automatically making every service record an accounting document. The general assessment period is five years from the end of the year in which the return was due, subject to the applicable restart, extension and treaty rules. The separate ten-year invoice rule above also applies to a taxable person who is not a VAT payer. Financial Administration: flat-rate-expense evidence, assessment periods and invoice retention. Before disposal, we record each required document's actual class, relevant tax year, expiry date and any documented hold in our operational records.
Cookies and browser storage
The portal uses the necessary supplyfolio_session cookie to maintain sign-in and XSRF-TOKEN to protect requests against forgery. The configured session lifetime is two hours. Temporary tab storage supports invitation and verification flows, the return path and workspace selection. These features support the requested portal functions; they are not marketing tracking.
No marketing analytics is included in the current portal implementation. The separate public website asks for permission before its optional analytics runs. Stripe can use its own cookies and similar technologies on hosted payment pages under its notice.
Security and your rights
We apply access controls, private document storage, protection of sign-in credentials, encrypted connections and controlled backup/recovery procedures appropriate to the service. No system eliminates every risk. The data-processing terms describe the security commitments for customer evidence. Before processing customer data, we confirm that the actual installation and operational configuration implement those commitments.
Depending on the applicable conditions, you may request access, correction, deletion, restriction or portability of your personal data, and object to processing based on legitimate interests. Where a purpose relies on consent, you may withdraw it without affecting earlier lawful processing. Write to m.trnka@supplyfolio.com; we may request proportionate information to verify your identity. We normally respond within one month and explain any lawful extension. European Commission explanation of individual rights.
You may complain to a competent supervisory authority, including the Personal Data Protection Office of the Slovak Republic, or the authority where you habitually live, work, or believe an infringement occurred. Contacting us first is welcome but is not required before making a complaint.
We date changes to this notice and bring material changes to affected users' attention. Publishing a new notice does not by itself provide a lawful basis for a new processing purpose or retroactively authorise it.