{"document_kind":"privacy","version":"2026-11-17.1","document_locale":"en","title":"Neltivo B2B Privacy Policy","intro":"Information on the processing of data relating to people creating accounts, business owners and persons representing installers, integrators and distributors using b2b.neltivo.pl. It explains the purposes, legal bases, data recipients and users’ rights. Acknowledging receipt of this information at registration is not consent to marketing or a waiver of rights.","sections":[["1. Controller and contact","The controller of personal data is Eliasz Fuczek, trading under the Neltivo brand, tax identification number (NIP) 2220928834, ul. Katowicka 51M/19, 41-400 Mysłowice, Polska. Contact for privacy matters and the exercise of rights: info@neltivo.pl.\nThis information concerns the b2b.neltivo.pl platform. For B2B functions, it applies independently of the separate rules for neltivo.pl; merely entering B2B does not signify consent to analytics or advertising used on another website."],["2. Categories and sources of data","Depending on how the platform is used, we process identification details of the business and its representatives, registration and tax details, company and delivery addresses, the contact person’s name, email and telephone number, account identifier, verification status, communication language, assigned commercial terms, the history of orders, enquiries, settlements and correspondence, project documents and data necessary to document changes and acceptance of documents.\nLogin services provided through Supabase involve protected authentication data, sessions and data required by the authentication method used. Passwords are not made available to the platform administrator in plain text. Security-event data includes, among other things, the account identifier and the time of login or an operation. Infrastructure providers may process technical connection logs, including IP addresses and browser data, as necessary for operation and security.\nThe record of document confirmations includes the account identifier, the version and actual language of the document, the interface language, the system time and a content identifier, such as a technical hash. Order data is recorded as it stands when the order is submitted and confirmed so that subsequent profile edits do not alter the transaction documentation.\nWe receive data from the user, the company they represent and authorised colleagues. For verification, we also use public business registers, VAT information and VIES to the extent appropriate for the transaction. If we received a contact person’s details from their company or from correspondence, the same rules and rights apply to them; the controller can be asked about the source and scope of the data."],["3. Purposes and legal bases","1. Creating and maintaining an account, responding to an enquiry and entering into and performing a contract with a natural person acting on their own behalf as a business owner: Article 6(1)(b) GDPR, to the extent necessary for the contract or steps taken at their request before entering into a contract.\n2. Verifying a business and authority to represent it, communicating with company representatives, handling B2B relationships, quotations, deliveries and complaints: Article 6(1)(f) GDPR, namely the legitimate interest in conducting and documenting cooperation; where the individual is a party to the contract, also Article 6(1)(b) to the relevant extent.\n3. Invoicing, settlements, tax and accounting obligations and legally required transaction documentation: Article 6(1)(c) GDPR.\n4. Account and document security, preventing abuse, controlling access rights, investigating errors, recording significant changes and establishing, exercising or defending claims: Article 6(1)(f) GDPR. The legitimate interest is the protection of users, information, assets and evidence of cooperation. Data used to demonstrate compliance with a legal obligation is also processed, to the extent necessary, under Article 6(1)(c).\n5. The platform does not carry out ongoing individual analytics of products viewed for the purpose of building a user’s commercial profile. Events concerning login, administrative changes and transactions serve the security and cooperation-management purposes described above.\n6. Registration does not include marketing consent. Messages necessary to manage an account, security, an enquiry or a transaction do not constitute a newsletter subscription. Any marketing requiring consent will be covered by separate, voluntary consent for the specified channel and purpose; refusal does not deprive the user of an account or order service."],["4. Requirement to provide data and third-party documents","Data marked as required is necessary to consider an application, verify a company, maintain an account or handle a particular transaction. Without it, the relevant action may not be possible. Other data is optional and should not be supplied just in case. The required acknowledgement of privacy information documents that it was made available and does not replace the legal bases described in section 3.\nProject documents should be limited to the needs of the matter. Do not send unnecessary data about children, residents or employees, scans of identity documents, special categories of personal data, passwords or building access codes. If a document contains other people’s data, the person supplying it should have an appropriate basis for disclosure. We also ask that this information be passed on to those individuals; this does not release Neltivo from its own information obligations."],["5. Data recipients and scope of disclosure","Access is limited to persons authorised to handle the particular matter. To the extent necessary, data is processed by infrastructure and service providers: Supabase (Supabase Pte. Ltd.) — database, accounts, authentication and file storage; Resend (Plus Five Five, Inc.) — transactional email delivery; Cloudflare — hosting, content-delivery and security infrastructure; providers of technical support and the email service used for correspondence.\nResend receives sender and recipient addresses, the content of the necessary message and delivery data. A notification may contain the enquiry text and the names of submitted files; the platform does not attach the project files themselves to such a notification. Excessive personal data should therefore also be avoided in the enquiry text and file name.\nRecipients may also include providers of accounting and settlement services, lawyers, advisers, manufacturers, carriers and customs agencies — only where the particular matter requires it — and authorised public authorities. Project documentation is provided to a supplier or contractor only to the extent necessary for an enquiry or contract. We do not publish customers’ attachments in an open catalogue.\nEntities processing data on our instructions should operate under an appropriate data processing agreement. Entities performing their own professional or legal obligations may act as separate controllers. The scope of disclosure should always correspond to the purpose of the particular matter."],["6. Location and transfers of data outside the EEA","The main Supabase project database is located in the eu-central-1 region (Frankfurt, Germany). This does not mean that all operations of all providers take place exclusively within the European Economic Area. Technical support and subprocessors of international services may involve access or processing outside the EEA. Supabase is a provider headquartered in Singapore.\nResend stores data relating to the messages it handles, including their content and delivery logs, in the United States. Selecting a European sending region does not mean that this data is stored in the EU. Cloudflare’s infrastructure operates globally and may process technical data outside the EEA.\nThe data processing agreements of Supabase and Resend provide for the European Commission’s standard contractual clauses for transfers for which those clauses are the appropriate basis, together with the required safeguards. Depending on the recipient and the scope of the transfer, a current adequacy decision may also apply. Merely using a well-known provider or a paid plan does not replace an assessment of the conditions for transferring data.\nInformation about the applicable transfer mechanism and how to obtain a copy of the safeguards is available at info@neltivo.pl, subject to the protection of trade secrets and other people’s rights. Provider documents are available at: https://supabase.com/legal/customer-resources/data-processing-addendum, https://resend.com/legal/dpa and https://www.cloudflare.com/cloudflare-customer-dpa/."],["7. Retention periods and criteria","1. Application and account data: for the period of considering the application and maintaining cooperation, and thereafter only to the extent needed to bring it to an end, meet legal obligations or protect specific claims. When assessing inactive accounts, relevant considerations include the most recent contact, unsettled orders, submissions and whether the purpose remains current. A refusal of cooperation or inactivity does not, in itself, justify retaining all data indefinitely.\n2. Tax and accounting documents: for the period required by the applicable law. The period is determined according to the type of document and the method of calculating the statutory period, taking into account its extension, suspension or interruption in connection with relevant proceedings.\n3. Orders, arrangements, complaints, correspondence and necessary project documents: for the duration of handling the matter and the resulting period of liability, and subsequently for the applicable limitation periods for claims where retention is necessary for that purpose. In a dispute, until proceedings have ended and the relevant periods have expired. Materials unnecessary for these purposes should not be retained solely because they were attached to a message.\n4. Evidence that documents were made available and accepted, and evidence of significant data changes: for the period of account use and the further time necessary to demonstrate the terms of contracts concluded or compliance with a legal obligation. The scope of retained evidence should be limited; it does not include passwords or authentication codes.\n5. Login and security events: for the period necessary to detect and investigate abuse, ensure accountability for operations and protect relevant claims. Longer retention of a particular event requires a connection with an incident, dispute or legal obligation. Any earlier records of catalogue activity are assessed for continuing necessity; records without a justified ongoing purpose are deleted or anonymised.\n6. Providers’ technical data also has its own retention periods resulting from the relevant service. Under Resend’s current rules, message data and logs in the standard Free, Pro and Scale plans are available for 30 days; the provider also specifies a 7-day backup cycle. This does not mean correspondence is deleted from Neltivo’s mailbox or transaction documentation after 30 days — the appropriate purpose and the criteria above apply to those records.\n7. Closing an account ends the ability to use its functions, but does not automatically delete documents for which retention still has a legal basis. Once that basis ceases to exist, the data is deleted or effectively anonymised. We do not apply one unlimited retention period to all categories; on request, we explain the basis for retaining particular data."],["8. Profiling and automated decisions","We do not make decisions about users based solely on automated processing that would produce legal effects concerning them or similarly significantly affect them within the meaning of Article 22 GDPR. The decision to approve a company and assign commercial terms is made by an authorised person at Neltivo.\nAutomated checks of data format and VAT status, price calculations according to assigned terms and technical protection against abuse support the service but do not replace individual confirmation of a transaction. If a result is incorrect or access is blocked, contact info@neltivo.pl. We do not use external behavioural-advertising pixels in B2B or ongoing individual tracking of viewed products for commercial purposes."],["9. Sessions, cookies and browser storage","The platform uses Supabase’s technical authentication and session-maintenance mechanisms and stores user-selected settings in localStorage. Session information is used to identify the signed-in account and provide the requested service, not to signify consent to advertising. A session may be refreshed; signing out or revoking a session ends its authorisation, irrespective of any technical entry that may remain in the browser.\nLocal entries include: neltivo-b2b-language — the selected language; neltivo-b2b-sidebar-collapsed — the menu layout; neltivo-b2b-cart-v1 with the account identifier — the working basket. localStorage entries have no automatic expiry time set and remain until replaced or removed by the application or the user. They are not evidence that a contract has been concluded. Deleting site data in browser settings may sign the user out and remove a local basket or preferences.\nInfrastructure providers may use technical mechanisms necessary to deliver the service securely and protect against abuse. Technologies not required to provide the requested service, if introduced and requiring consent, will be activated only after separate prior consent, with the ability to change it. Acceptance of the Terms or acknowledgement of this Policy is not consent to such technologies."],["10. Individuals’ rights","Within the limits provided by law, individuals have the right to access their data and receive a copy, to rectification, erasure, restriction of processing and data portability where the statutory conditions are met. Processing based on a legitimate interest may be objected to on grounds relating to the individual’s particular situation. An objection to direct marketing does not require such justification. Where particular processing is based on consent, consent may be withdrawn without affecting the lawfulness of processing carried out before its withdrawal.\nRequests may be sent to info@neltivo.pl or the controller’s postal address. If there are reasonable doubts, we may request proportionate information necessary to confirm identity, not a password or MFA code. As a rule, we respond within one month and notify the individual within that period of any justified extension under the GDPR.\nThe right to erasure does not mean the unconditional deletion of data needed for statutory obligations or the establishment, exercise or defence of claims. If retaining some data is justified, we explain the basis and limit its use to that purpose. A complaint may be lodged with the President of the Polish Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych); information on contact methods and lodging a complaint is available at https://uodo.gov.pl/."],["11. Document security and accountability","We use organisational and technical measures appropriate to the type of data, in particular encrypted connections, authentication, separation of access rights and restricted access to company data and documents. Project attachments are stored in a private resource; access to a file is checked, and its download link is temporary. Such a link should be treated as confidential and not shared with unauthorised persons.\nThe history of significant account changes and the record of document confirmations serve accountability and the protection of evidence of cooperation. A correction of data should not silently overwrite information in a historical order or an earlier acceptance. Access to administrative records is restricted.\nNo system offers an absolute guarantee of security. A file’s acceptance through the form does not confirm that its content has been examined for every threat. We do not request excessive data or guarantee that every piece of information throughout the environment is encrypted in a way that prevents access by all providers. Suspected unauthorised access, incorrect disclosure or an incident should be reported to info@neltivo.pl."],["12. Updates and access to information","This Policy may be amended when the law, providers, functions or the way data is processed changes. Current and earlier versions are identified by separate version numbers. We notify users of significant changes through the platform or by email before new processing begins, where required.\nAcknowledging that new information has been made available does not legitimise processing that requires separate consent and does not apply retroactively. For matters concerning documents and privacy, contact the controller at info@neltivo.pl. Version 2026-11-17.1."]],"bottom":"Eliasz Fuczek • Neltivo • NIP 2220928834 • ul. Katowicka 51M/19, 41-400 Mysłowice, Polska • info@neltivo.pl. This Policy applies to b2b.neltivo.pl."}