SetApka terms of use

Effective from 10 October 2026 · Polski · Deutsch

1. Provider and definitions

The provider is Jacek Piotr Strzelecki, running a business as JPS FILM Jacek Strzelecki, ul. Chodkiewicza 33/1, 94-028 Łódź, Poland, tax ID (NIP) 727 265 72 84, registered in the Polish CEIDG business register; e-mail: office@setapka.pl (the “Provider”).

2. Scope of the service and technical requirements

SetApka gives project members the shooting day schedule, announcements and notifications, the crew list, files and chat, and in the Base – crew profiles, job posts, locations and the company directory. You need a smartphone with an up-to-date iOS or Android system or an up-to-date web browser and internet access (some data also works offline).

The agreement for the provision of electronic services is concluded when you start using SetApka and lasts until your account is deleted. By using SetApka you accept these terms and the privacy policy.

3. Account

4. Projects and responsibility for content

The production decides which documents and data it uploads to a project and who can see them (project code, PRO roles, removing people, the Production folder). The production is responsible for having a legal basis to share this data with project members. For data in projects, the Provider processes it on behalf of the production under the Data Processing Agreement (Annex 1), which forms part of these terms and binds the production from the moment it creates a project.

Please do not upload special categories of data (e.g. health data) to projects beyond what is necessary to organise the shooting day.

5. Reading call sheets and SetApka's role on set

Call sheets are read automatically by artificial intelligence. Before publishing to the crew, a person with the PRO role sees the result and hints about what to check, and can correct it. SetApka does not replace the production's instructions: in case of discrepancy the original call sheet and the instructions of the set management prevail. This does not exclude the Provider's liability for the operation of SetApka within the limits set out in section 11.

6. Payments

7. Base: crew, job posts, locations, companies

8. Content rules – zero tolerance

In the chat, in announcements and in the Base it is forbidden to publish unlawful content (e.g. threats, incitement to hatred, infringement of personal rights or copyright, fraud) or content that breaks SetApka's rules (e.g. offensive, harassing, discriminatory, sexual or violent content, spam).

9. Reports, moderation and appeals

10. Complaints

11. Liability

The Provider makes every effort to keep SetApka working continuously and correctly and is liable for damage resulting from non-performance or improper performance of the service under general rules. Towards businesses (excluding sole traders acting with consumer protection), the Provider's liability for damage resulting from the use of the paid service is limited to the fees paid for the project concerned in the 12 months before the event and does not cover lost profits. This limitation does not apply to damage caused intentionally or to other cases where liability cannot be limited by law, in particular personal injury and liability under data protection law to the extent it cannot be limited by contract. The Provider is not responsible for content uploaded and published by users, subject to the obligations in section 9.

12. Support and support access

Report problems to office@setapka.pl. The scope, purpose and logging of support access to data are described in the privacy policy, section 5. At the production's request, support may correct project settings (e.g. roles, activation); every such change is logged.

13. Changes and final provisions

Annex 1. Data Processing Agreement

Concluded between the production that creates a project (the Controller) and the Provider (the Processor) under Article 28 GDPR, when the project is created.

  1. Subject matter and duration: processing of personal data contained in the project to provide the SetApka service, for as long as the project exists.
  2. Nature and purpose: storage, automatic reading of call sheets (including via the Claude API), making data available to project members, sending notifications, remembering corrections after reading for later call sheets of the project and – on the instruction of a person with the PRO role – sending Base invitations (with information on the source of the data; without using the data for any other purpose).
  3. Types of data: names, positions, phone numbers, e-mail addresses, organisational information from call sheets (times, locations, transport), the content of files, announcements and chat, reading results and corrections, and technical data related to project membership (device, app version, notification status, call sheet reading history).
  4. Categories of data subjects: crew and cast members, collaborators and contractors of the production named in project documents.
  5. Processor's obligations: processes data only on documented instructions of the Controller (the instructions are the settings and actions in the project); ensures confidentiality of people with access; applies security measures under Article 32 GDPR (encryption in transit, project access control, backups with 7-day restore, logging of support actions); assists the Controller with data subject rights and obligations under Articles 32–36 GDPR; notifies the Controller of a personal data breach without undue delay, no later than 48 hours after becoming aware of it, providing the information needed to assess the breach; assists the Controller with data protection impact assessments and prior consultation with the supervisory authority; makes available the information needed to demonstrate compliance with Article 28 GDPR and allows audits, including inspections, by the Controller or an authorised auditor, scheduled at least 14 days in advance and carried out without disrupting the service (the Controller bears the audit costs unless it shows a material breach of this agreement).
  6. End of processing: after the services for the project end, the Controller may, at its choice, request the return of personal data – on request sent to office@setapka.pl we provide, within 14 days, an export of the project's files and data (files in their original format, other data as JSON) – or their deletion; the Processor deletes the data and existing copies (backups expire within 7 days) unless the law requires further storage. Deleting the project by the Controller is a request for deletion.
  7. Sub-processors: the Controller gives general authorisation for the providers listed in the privacy policy, section 4 (Google – Firebase, Anthropic – Claude API, home.pl, Apple and Google – notifications). We announce an intended change of sub-processor 14 days in advance; the Controller may object and delete the project.
  8. Transfers outside the EEA: only on the bases described in the privacy policy (adequacy decision – EU-US Data Privacy Framework – or standard contractual clauses).