Privacy Policy

1. Data controller and contact

The controller of personal data processed for OpenRun is ZarazWSieci, NIP 5671938865, Poland, also identified in the privacy policy of zarazwsieci.pl.

For requests about privacy and personal data, contact [email protected]. OpenRun is a separate product, so this policy describes OpenRun rather than ZarazWSieci's agency, SEO or audit services.

2. What information may be processed

When you open the website, technical records may include your IP address, browser and device type, requested pages, date and time of access and basic diagnostic information needed to deliver and protect the service.

If you use a workspace, account and session data may be needed to identify you and keep you signed in. When you connect an external service, OpenRun may process the configuration, account identifiers, authorization details and service information necessary for the connection you choose. The categories depend on the particular integration and permissions you approve.

If you email us, we receive your contact details, the message and any attachments you send.

3. Purposes and legal grounds

We process information to provide requested site and workspace features, manage access and integrations, respond to support requests, secure systems, investigate errors and meet legal obligations.

Depending on the purpose, the legal grounds under Article 6 GDPR are: steps taken before entering into or performing a contract, compliance with a legal obligation, our legitimate interests in security and service operation, or consent where consent is required. Any optional processing that requires consent should be presented separately.

4. Accounts and contact

Account information is used to provide sign-in and workspace access where those functions are available. Data you include in an email is used to handle your request and any necessary follow-up. Providing contact details is voluntary, but without an address for the reply we may not be able to respond.

Do not send passwords, payment card numbers or other sensitive information in regular support messages.

5. Connected services and authorization

Connecting a service is voluntary. You should authorize only services that you are permitted to manage and review the requested permissions carefully. Providers may process information under their own privacy policies; OpenRun does not control their independent processing.

Where an integration uses an access token or another credential, that information is needed to operate the connection. You can withdraw access through the external provider and, if the workspace offers that control, remove the connection from OpenRun. The specific information and the way it is stored must correspond to each integration actually released.

6. Payments

The public OpenRun landing page does not collect payment card details. If paid OpenRun features are introduced, the payment provider and the related processing will be identified before payment. Banking, invoice and transaction records, where applicable, may also have to be kept for statutory accounting or tax purposes.

7. How long information is kept

We keep information only for as long as it is needed to provide the relevant feature, respond to a request, protect our rights, maintain security or satisfy legal requirements. Contact messages are kept for the time required to handle the correspondence and any related claims. Financial records, if created, are retained for the period required by law.

Account information, service connections, technical logs and backups may have different retention periods depending on the feature. When an integration is disconnected or an account is closed, some records may still need to be kept temporarily for security, legitimate claims or legal compliance.

8. Recipients and transfers

Information may be processed by service providers supporting hosting, infrastructure, databases, authentication, email delivery, security and the integrations you actively use. It may also be disclosed to competent authorities where required by law.

If a particular provider processes data outside the European Economic Area, the transfer must rely on a lawful mechanism and any safeguards required by GDPR. The relevant providers and transfer arrangements depend on the production setup and enabled services.

9. Your rights

You may request access to your personal data, correction, deletion, restriction, portability, or object to processing where those rights apply. If processing is based on consent, you may withdraw it at any time without affecting processing already carried out lawfully.

Send requests to [email protected]. You also have the right to complain to the President of the Polish Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych) if you believe your rights under GDPR have been infringed.

10. Cookies and technical data

Cookies or similar browser storage may be required to keep a session active or maintain the technical operation of a workspace. Basic website request logs may also be used for diagnostics and security.

The landing page in this project does not include advertising or analytics scripts. If optional analytics, advertising cookies or third-party chat tools are added to OpenRun, this policy and the relevant consent controls must be updated before those tools are deployed. You can also manage cookie permissions in your browser.

11. Automated decisions

The OpenRun promotional website does not use personal information to make automated decisions that produce legal effects or similarly significant consequences for visitors. Any future feature with a different impact would require a separate explanation.

12. Security and privacy questions

Appropriate technical and organizational measures should protect personal information against unauthorized access, loss or misuse. You can help by using secure sign-in methods, checking permissions for connected accounts and reporting suspicious activity.

For a question or privacy request, write to [email protected].

13. Changes to this policy

This policy may change when OpenRun's functions, providers or legal requirements change. The updated version will be available here with its effective date.