Clear terms for working with SF Method.

1. Provider and contact

The service provider is SF METHOD GROUP Sp. z o.o., ul. Ks. Dziekana Wawrzyńca Bochenka 23, 55-100 Trzebnica, Polska, Polish tax ID 9151834363, KRS 0001165633, REGON 541350735 (“SF Method”, “Operator”). General contact: hello@sfmethod.co. Privacy: privacy@sfmethod.co.

These documents are available free of charge before contracting in a form that can be saved and reproduced.

2. Business customers only

SF Complete is not a consumer offer. It may only be contracted by a business, legal entity or organisation acting for professional or commercial purposes.

The person starting the pilot confirms authority to bind the named organisation. Do not start the subscription without that authority.

3. SF Complete service terms

SF Complete is SaaS for managing clients, services, teams, bookings and finances. Current product descriptions and organisation configuration define the functional scope.

The agreement is formed after the organisation details are submitted, the current Terms, DPA and pricing are accepted, a payment method is saved with Stripe, and SF Method confirms activation. We record the accepted versions, time and a technical evidence hash.

A current browser, internet connection and working email address are required. The customer is responsible for data accuracy, user permissions, a lawful basis for processing its clients’ data and credential security.

Platform, code, marks and materials remain owned by SF Method or its licensors. The customer receives a non-exclusive, non-transferable right to use the service internally for the agreement term.

We may improve the service and make justified security, feature or supplier changes. Material changes to rights or price will be notified with reasonable advance notice.

4. Pilot, pricing and variable billing

The pilot lasts 14 days and PLN 0 is due today. Stripe saves the card and the first charge may occur after the pilot unless the subscription is cancelled earlier.

SF Complete starts at PLN 149 net per month, including 10 active clients and 1 active location. Each additional location is PLN 99 net per month. Applicable VAT is added.

Clients above the allowance are progressively billed: 11–20 at PLN 5, 21–50 at PLN 4, 51–100 at PLN 3, 101–250 at PLN 2 and 251+ at PLN 1.50 net per client/month. The monthly total varies with actual usage.

An “active client” is one unique person-client who, in the billing period, had valid access or recurring service, a paid non-refunded purchase, or a qualifying booking/session. A profile, invitation, login or payment record alone does not qualify. Each person is counted once per period and test accounts are excluded.

Numbers entered before Stripe are estimates only. Invoices and charges use measured activity. Customers may challenge a measurement error and request an explanation.

5. Term, cancellation and complaints

After the pilot the subscription renews monthly until cancelled. Cancel before renewal in the panel or via hello@sfmethod.co; cancellation takes effect at the end of the paid period unless agreed otherwise.

Fees incurred before effective cancellation remain payable. We may suspend access for overdue payment, security threats or material breach, after notice where practical and reasonable.

Send complaints to hello@sfmethod.co with the organisation name and issue. We acknowledge receipt and normally reply within 14 business days.

6. Availability and B2B liability

We use appropriate technical and organisational measures, but service may depend on networks, devices and third parties. Planned maintenance and material outages will be communicated where practicable.

To the maximum extent permitted by law, we exclude lost profit and indirect damage; aggregate liability for an event is capped at net fees paid in the preceding 3 months. This does not limit intentional harm or liability that cannot lawfully be excluded.

Polish law governs. B2B disputes are submitted to the court competent for the Operator’s registered office, subject to mandatory law.

7. Website and sales privacy notice

SF METHOD GROUP Sp. z o.o. is controller for website visitors and customer representatives. We process contact, company, billing, acceptance and technical data for pre-contractual steps and contract performance (GDPR Art. 6(1)(b)), legal/accounting duties (c), and security, claims and B2B support as legitimate interests (f).

Data includes identity and work contact details, organisation, declared scale, transactions, acceptance versions, technical identifiers and security logs. We do not make solely automated decisions producing legal effects for visitors.

Recipients include hosting/security, payment, email, accounting and legal providers and authorised authorities. Stripe also acts as an independent controller for parts of payment processing. Cloudflare processes traffic data for security.

Abandoned checkout records are deleted after 90 days. Contract, billing and acceptance evidence is kept for the agreement and generally up to 6 years afterwards, or longer if law or claims require. Security logs are normally kept up to 12 months.

You may request access, correction, deletion, restriction, portability where applicable and object to legitimate-interest processing, and complain to the Polish Data Protection Authority. Contact privacy@sfmethod.co. Contract-required data is voluntary, but the pilot cannot start without it.

Transfers outside the EEA use a GDPR Chapter V mechanism, such as an adequacy decision or Standard Contractual Clauses with assessment and supplementary safeguards.

8. Cookie policy and privacy settings

The website currently runs no analytics, Meta Pixel, remarketing or other optional trackers, so we do not show a misleading “accept all” banner.

Cloudflare may set strictly necessary __cf_bm for bot and abuse protection; it expires after about 30 minutes of inactivity. Depending on risk, cf_clearance may confirm a passed security challenge. These technologies are necessary to securely deliver the requested website.

If analytics or advertising is added, optional scripts will remain blocked until separate, voluntary consent. Users will be able to accept, reject or change choices equally easily through “Privacy settings” in the footer.

9. Data Processing Agreement (DPA)

Where the customer controls personal data of its clients, staff or contractors and SF Method processes it on the customer’s behalf, this section is the Article 28 GDPR processing agreement and forms part of the SaaS agreement.

Processing consists of hosting and operating the platform for the agreement term: recording, organising, displaying, transmitting, backing up, supporting and deleting data on documented instructions. Data may include identity, contact, service, booking, billing, progress, goals and activity data concerning end clients, staff and contractors.

SF Method processes only documented instructions, binds authorised staff to confidentiality, applies Article 32 safeguards, assists with rights, breaches, impact assessments and consultations, provides compliance information and permits proportionate agreed audits.

The customer gives general authorisation for the subprocessors below. We will provide reasonable advance notice of material changes and allow a reasoned objection. Subprocessors receive essentially equivalent data-protection obligations; SF Method remains accountable under Article 28.

At service end data is returned or deleted at the customer’s choice, subject to law. The customer is responsible for lawful grounds, transparency, lawful instructions and not submitting unagreed categories of data.

• We notify a documented customer-data breach without undue delay and provide available information needed for GDPR Articles 33–34 duties.
• We give at least 14 days’ notice of a subprocessor change unless urgent security risk requires faster action. The parties address a reasoned objection in good faith; if unresolved, the customer may terminate the affected service.
• Security measures include access control and least privilege, encryption in transit, vulnerability management, event logging, backups, incident procedures and periodic reviews, configured according to risk.
• A routine audit may take place once per 12 months on an agreed scope and under confidentiality; this limit does not apply to a substantiated breach concern or authority request.

10. Active vendors and subprocessors

This list covers the website, payments and core product operations. Supplier changes require a role/transfer assessment and documentation update.