Experience

Selected examples of work on digital products, contracts and data protection.

IT and SaaS

Legal work for the development, delivery and operation of digital services.

  1. Product
  2. Documents
  3. Implementation
IT and SaaS services

SaaS documentation aligned with the product

Terms, a DPA, privacy information and data-migration arrangements prepared ahead of a SaaS product’s planned launch.

Business outcome: The product’s legal framework is prepared for its planned launch and further development. Addressing data migration and changes in Data Act requirements reduces the risk of costly changes to the service model after launch.

Scope of work

We worked on the legal framework for a SaaS product, including its Terms of Service, Data Processing Agreement and Privacy Policy. The work started with data flows, the parties' roles and how customers would use the service. It also covered subprocessors, billing and customer eligibility.

We combined the documentation work with a review of implementation assumptions, identifying parts of the customer journey that needed to reflect the agreed legal terms.

The scope also covered provider switching and data migration under the Data Act, including preparation for further changes to switching charges. The product has not yet launched; the work prepared its legal framework for launch and further development.

Checking implementation against the legal documentation

Reviewing implementation materials against the agreed contract, service activation and data handling.

Business goal: Reduce the risk of refunds, customer claims and interrupted sales caused by a mismatch between the service terms and the product.

Scope of work

We reviewed a SaaS product using repository materials and team reports. We compared the implementation with the earlier assumptions on contract formation, service activation, customer verification and data retention.

We prepared comments on specific implementation points and corresponding documentation changes. The recommendations connected legal requirements with product behaviour.

A software services agreement for an enterprise engagement

Development scope, acceptance, software IP and liability in an enterprise services agreement.

Business outcome: The software company signed the contract and is earning revenue under agreed billing rules for different delivery models. Its customer is satisfied with the clear arrangements for ordering and documenting work and acquiring rights to the results.

Scope of work

We reviewed and prepared a master services agreement for a software company providing development services to an enterprise customer. The work covered team delivery and pricing models, scope, acceptance and termination.

We also addressed software IP, data processing, subcontractors, liability and restrictions on recruiting personnel. The agreement was reviewed against how the services would be organised and delivered.

Preparing B2B customer onboarding

Reviewing B2B registration, document acceptance and individual commercial terms before a planned launch.

Business goal: Onboard paying B2B customers and reduce disputes over who ordered the service, accepted the price and is responsible for payment.

Scope of work

We analysed product materials and a proposed registration process before a planned B2B onboarding launch. We considered how service documentation would connect with commercial terms, document acceptance and authority to represent an organisation.

The work also covered questions about personal data and suppliers that needed answers before the final documentation could be prepared. The work is ongoing; the intended process still requires further decisions and implementation.

Aligning platform documentation before launch

Updating platform documentation before a planned launch, with consistent references and an open-issues list.

Business goal: Bring the product to market without postponing launch because of inconsistent service terms or unresolved user arrangements.

Scope of work

We worked on updating a platform’s legal documentation before its planned launch. The scope covered service terms, privacy information, contact channels and vulnerability reporting.

We compared the documents with the current product and planned changes, aligned names and references, reduced duplicated information and prepared a list of questions for the team to close before launch. Product development is ongoing; the platform has not yet launched.

Startups and IP

Company arrangements, contracts and product rights for growing ventures.

  1. Creators
  2. Rights
  3. Company
Support for startups

Rights in software under continued development

A draft agreement and an inventory of product components, taking future software versions into account.

Business goal: Protect the ability to earn revenue from the software and its value to investors, while limiting the cost of handling rights to future releases.

Scope of work

We prepared a draft agreement for transferring software rights to a company. We first identified the components of the product and which should be covered by the document, including future software versions.

Comparing legal models for a digital platform

Organising processes, reviewing the agreement and planning successive payment-model iterations for a digital platform.

Business outcome: The platform launched quickly, with further payment-model iterations able to be introduced progressively as the business develops.

Scope of work

We analysed alternative operating models for a digital platform. Starting with user journeys and transaction flows, we mapped the contractual structure, the parties' roles and their responsibilities under each option.

The assessment covered personal data, consumer issues and operational risks. We combined it with a review of the agreement, clearer processes and a plan for successive payment-model iterations.

Agreements between platform users

A draft user-to-user agreement distinguishing the users’ responsibilities from the platform operator’s role.

Business goal: Build trust in transactions on the platform and reduce the cost of handling disputes between users.

Scope of work

We worked on a draft agreement for use between platform users. The analysis covered their mutual obligations, responsibility and the distinction between the platform operator and the users entering into an agreement.

The work also addressed how users would complete the document: the necessary information, clear provisions and options reflecting different user situations.

Engaging a team member working from Poland

Negotiating Polish employment for a US company while preserving participation in its US equity programme.

Business outcome: The US company hired a specialist who is now working under a Polish employment agreement. The negotiated terms enabled the engagement to begin while preserving access to the US equity programme.

Scope of work

We advised an international technology company on engaging a team member who would work from Poland. We compared direct employment, an employer of record and genuine B2B cooperation against the intended working relationship.

The assessment covered employment and remote work obligations, social security, tax considerations, software IP and the relationship with equity documentation. It provided a basis for selecting a model and adapting the relevant documents.

The agreed model was employment under Polish law, connected with the US equity programme documents. The agreement was signed and the employee started work.

US employer documents for work performed in Poland

Reviewing a US employer’s templates for work performed in Poland and consistency across employment, IP and data terms.

Business outcome: The signed engagement package combined Polish employment with the US equity programme. The company brought the employee on board while retaining the incentive mechanism used in its organisation.

Scope of work

We reviewed a US employer’s document package for a person who would work in Poland on an ongoing basis. We identified terms requiring adaptation in working arrangements, confidentiality, intellectual property and data use.

We distinguished the local employee or contractor relationship from the US company’s corporate and equity documents. The work covered the Polish part of the review and consistency across the package.

Corporate structure and startup governance

Company structure, founder rights, representation and decision-making for a growing technology startup.

Business goal: Keep the company operating and making decisions through ownership changes, and prepare the business for investor discussions.

Scope of work

We supported a technology startup with its corporate structure and governance arrangements. The work covered founder rights, equity arrangements, management, representation and the allocation of corporate decisions.

We considered beneficial ownership requirements and the clarity needed for future ownership changes and due diligence. The corporate work was connected to the team's product and commercial plans.

Founder discussions before drafting an agreement

A business questionnaire before drafting a founder agreement: roles, commitment, equity and decisions.

Business goal: Protect product development from decision-making deadlock, costly disputes or a team breakup caused by unresolved founder expectations.

Scope of work

We prepared a questionnaire to help founders organise their business arrangements before drafting legal documents. It covered roles, commitment, equity, decision-making and possible departures.

We also addressed how to assess whether each person was fulfilling their responsibilities. We brought together shared positions and differences so the founders could discuss their expectations and decide how to develop the product.

Data protection

Processes and documentation with clear roles and responsibilities.

  1. Processes
  2. Roles
  3. Principles
Data protection services

Shared data protection principles and distinct responsibilities

A draft shared data protection policy distinguishing roles, authorisations and areas of responsibility.

Business goal: Reduce the risk of penalties, claims and operational disruption caused by improper access to or use of personal data.

Scope of work

We worked on a draft data protection policy for an organisation where responsibility for processing required distinctions between several roles and activities. We identified which principles could be shared and where separate documentation was needed.

The draft covered authorisations and access, document handling, cooperation with the data protection officer and allocation of responsibilities. It was prepared for further substantive review. The new arrangements have not yet been implemented.

Privacy and terms for an MVP

Proposed changes to terms and privacy information reflecting the product’s actual MVP features.

Business outcome: The platform launched with legal documentation matched to its MVP, without expanding it to cover features the product did not yet offer.

Scope of work

We prepared proposed changes to the terms and Privacy Policy of an MVP platform. We compared the documents with the available user features, contact arrangements and information made visible on the platform.

The changes clarified the operator’s role, data visibility and processing information. Descriptions of features not yet offered also needed to be removed so the documents matched the current product.

Data roles in a multi-party engagement

Comparing documents in a multi-party engagement and distinguishing responsibility for specific data processing activities.

Business outcome: The client agreed cooperation terms without taking on data protection responsibility for complaints about other parties’ services. This reduced exposure to claims and costs arising from processes outside the client’s own role.

Scope of work

We analysed engagement documents involving personal data flows between several parties. We compared provisions across the documents to check that the roles and responsibilities were described consistently.

We prepared proposed changes and their rationale for discussions between the parties. The work included identifying the limits of the client’s responsibility for specific processes and distinguishing changes from issues to confirm with the other parties.

Funded projects

Procurement records, decision rationale and contract amendment reviews.

  1. Requirements
  2. Decision
  3. Records
Explore our services

Procurement records for a funded project

Reviewing procurement requirements, an offer and correspondence, and preparing a record of the decision.

Business outcome: The client closed out the project and retained its funding without having to repay it.

Scope of work

We reviewed procurement records for a funded project, including requirements, an offer and correspondence. The work concerned the reasons for the decision and the distinction between missing documents and an offer that did not meet the requirements.

We prepared draft supplementary records and a conflict of interest document. The work included identifying the materials needed to document the decision.

Reviewing a change to a contractual deadline

Reviewing the grounds for extending a contractual deadline and the evidence needed to document a delay.

Business outcome: The client completed the project despite the delay and retained its funding without having to repay it.

Scope of work

We analysed whether a delivery deadline could be changed in a project subject to additional funding rules. We reviewed the amendment provisions, the stated reason for delay and the evidence needed to support it.

We worked on the draft amendment and the information to obtain before signing. The assessment connected the actual grounds for the change with its effect on the procurement terms.

These descriptions cover different areas of work. Some belong to the same engagement.

A similar question in your business?

Tell Maciej Lis about your product, contract or data process. We will agree the scope and next step.

Maciej Lis, attorney-at-law and DPO
Discuss your matter

Online · up to 30 minutes · free

Request a free consultation

Choose a few answers and we’ll put your enquiry together. You don’t need legal knowledge or a list of documents to get started.

We’ll check whether your enquiry falls within the scope of our Polish-law practice.