1. The data controller
- The controller of your personal data is Arkadiusz Mastalerz, a sole trader trading as Mastalerz.it Arkadiusz Mastalerz, Polish tax ID (NIP) 5632311091, REGON 061610202, address: ul. Krasnowolska 18E, 02-849 Warszawa, Poland (we).
- Contact for personal data matters: arkadiusz@mastalerz.it. Please direct data protection matters to the controller at this address. If we appoint a data protection officer, we will publish their contact details in this policy.
- This policy covers the NoBrainer.social website and application, including the studio at studio.nobrainer.social.
2. The two roles in which we process data
- As a controller we process the data needed to create your account, sell access, bill you, keep the service secure and stay in touch with you.
- As a processor we process on your behalf the data you enter into the Studio: brand descriptions, texts, graphics, source materials and any personal data of other people they contain. You decide the purposes and the legal basis for that data. The rules are in the data processing agreement in section 15 of the Terms of Service. Do not submit special-category data or criminal conviction data.
3. What data we process and why
- Account and sign-in. Email address, a password stored as a hash (we cannot read it), a Google account identifier if you sign in with Google, your language, session data. Purpose: creating the account and signing in. Basis: contract (Article 6(1)(b) GDPR) if you are a party, or our legitimate interest in administering a contract with the business you represent (Article 6(1)(f) GDPR).
- Studio and content. Brand name, brand profile (industry, audience, style, content pillars, colours, logo), the sources and materials you add, post and graphic proposals and versions, publication times, approvals, the list of people in the Studio. Purpose: providing the Service. We process entrusted data on your instruction under the data processing agreement (Article 28 GDPR); you are responsible for its legal basis. For data needed to administer the account, the basis is contract or legitimate interest in administering it.
- Connection to Facebook and Instagram. Details of the connected account (Page and account identifiers, name) and the access key granted by Meta, which we store encrypted. Purpose: publishing approved posts at the chosen time. Basis for administering the connection: contract or legitimate interest in administering a contract with the business represented. Third-party content is processed on your instruction under the processing agreement. If you turn on receiving comments and messages, we fetch them from the connected account to show them in the Studio. This also covers data of the people who write to you. We use data received from Meta only for these purposes; we do not sell it and do not use it for advertising. Removing the connection and the data from Meta. You can disconnect an account at any time in the Studio (the Publishing tab, the connection's menu, Disconnect), or remove NoBrainer.social in Facebook (Settings and privacy > Settings > Business integrations, or Apps and websites). After a removal in Facebook, Meta notifies us and we disconnect access to the Pages and accounts connected through your Facebook account, clear the stored access data, and cancel unsent posts and replies. To also delete the messages and comments received through those connections, send a data deletion request for NoBrainer.social in the same Facebook settings; Facebook then shows you a confirmation code and a link to a page with the status of the request. Deleted data may remain in backups for the period given in clause 6.6. Removing the connection does not delete your Studio account; you can delete the account in the Studio settings or by writing to arkadiusz@mastalerz.it from the address of your account.
- Payments and invoices. Order and payment identifiers, the amount, the access period, invoice details (company name, address, tax ID) and issued invoices. Card details are processed by Stripe alone. Purpose: sales, billing and meeting tax obligations. Basis: contract and legal obligation (Article 6(1)(b) and (c) GDPR).
- Acceptance of documents. The versions of the Terms of Service and the Privacy Policy you accepted, with the date. Purpose: proving that the contract was concluded and establishing or defending claims. Basis: legitimate interest (Article 6(1)(f) GDPR).
- Email messages. The link to confirm your address, password recovery, purchase confirmations, replies to your questions. Purpose: running the account, support and responding to contact form enquiries (name, email, message and selected offer). Basis: pre-contract steps at your request or contract if you are a party (Article 6(1)(b) GDPR), and legitimate interest in correspondence and administering service for the business you represent (Article 6(1)(f) GDPR).
- AI generation. To generate texts and graphics we pass the brand description, selected sources, the topic and the instructions to model providers. Purpose: carrying out the operation you requested. Basis: contract or legitimate interest in administering it; for entrusted data, the data processing agreement. Submit only data needed for the task, without passwords or other secrets. Model suppliers’ terms may provide for their own retention and use of data; we do not give a general guarantee of no logging or model training on data. On request we will identify the recipient and terms applicable to a generation. We do not make decisions with legal effect about anyone based solely on automated processing.
- Technical data and security. IP address, browser type, time and result of requests, records of sign-in events and errors. Purpose: securing the Service, detecting abuse, limiting sign-in attempts, fixing errors. Basis: legitimate interest (Article 6(1)(f) GDPR).
- Cookies and browser storage. They are described in the Cookies policy.
- Measuring ad performance (only with consent). If you consent to marketing cookies in the cookie banner: (a) the Meta Pixel sends Meta Platforms Ireland Limited information about events on our site and in the Studio (a view of the offer page, the legal documents or the sign-in page, creating an account, starting a payment, a purchase with the net amount and currency) together with the address of the page, your IP address, browser and device data and the identifiers from the
_fbpand_fbccookies; (b) in thenbs_attributioncookie we store the UTM tags, Meta’s ad click identifier (fbclid), the landing page and the time of the visit. If you create an account within 30 days, we pass these tags, together with the new account’s email address and creation time, to the administrator of the Service in an email, to assess which ad brought the customer. We do not send Meta your email address or other form data. Purpose: measuring how our ads on Facebook and Instagram perform. Basis: your consent (Article 6(1)(a) GDPR). You can withdraw consent at any time with the "Cookie settings" button in the footer of the site and the Studio, without affecting the lawfulness of processing before the withdrawal. Not consenting does not limit your use of the Service. For the collection of data by the pixel on our site and its transmission to Meta we act together with Meta Platforms Ireland Limited as joint controllers, under Meta’s Controller Addendum; Meta carries out further processing of that data as a separate controller, under Meta’s Privacy Policy. You can exercise your rights in this respect with us or with Meta. - Newsletter form protection (Google reCAPTCHA). On the offer page (nobrainer.social and nobrainer.social/en) the newsletter sign-up form is protected by the invisible reCAPTCHA of Google Ireland Limited. The script loads only when you start using the form, and the check happens when you submit it; simply viewing the page sends Google no data. Google processes your IP address, browser and device data, the page address, how you use the page (for example cursor movements) and its own cookies, including
_GRECAPTCHAon its own domain. Purpose: protecting the form against spam, bots and abuse. Basis: our legitimate interest in protecting the form (Article 6(1)(f) GDPR). You can object by writing to arkadiusz@mastalerz.it. The Cookies policy and Google’s Privacy Policy describe the details. - Newsletter. On the offer page you can sign up for the NoBrainer.social newsletter. The form sends your email address and the ticked consent to our email delivery provider, EmailOctopus. Sign-up needs confirmation (double opt-in): we send a message with a link, and you start receiving the newsletter only after you click it. We process: your email address, the text and date of your consent, the date of sign-up and confirmation, the subscription status and information on delivery, opening of messages and link clicks. We send the newsletter from hello@nobrainer.tech. Purpose: sending news about NoBrainer.social, NoBrainer services and offers, as described in the consent. Basis: your consent (Article 6(1)(a) GDPR), which is also the consent to receive commercial information by electronic means required by the Polish Electronic Communications Law. Giving your address is voluntary. You can withdraw consent at any time with the unsubscribe link in every message or by writing to arkadiusz@mastalerz.it; withdrawal does not affect the lawfulness of earlier sending. We keep the data until you unsubscribe or withdraw consent. A sign-up that has not been confirmed receives no newsletter. After you unsubscribe we may keep only the address marked as unsubscribed, so that we never send it the newsletter again (our legitimate interest, Article 6(1)(f) GDPR); on request we delete it completely. The form is protected by Google reCAPTCHA (clause 3.11).
- Traffic statistics (Google Analytics 4, only with consent). If you consent to analytical cookies in the cookie banner, Google Analytics 4 measures traffic on nobrainer.social and in the Studio at studio.nobrainer.social: views of public pages (the offer page, the legal documents and the Studio sign-in and sign-up pages) and three events: creating an account, starting a payment and a purchase (with the net value, the currency and a random identifier of the payment attempt). With them Google receives the address of the page, in which we keep only UTM tags among the parameters, the address of the page the visit came from, browser and device data and the identifiers from the
_gaand_ga_<container-id>cookies. We do not send Google any content from inside the Studio, your email address, your name or any other identifier we hold about you. According to Google, the service does not log or store the IP addresses of users in the European Union; it uses them only to derive an approximate location (for example the country or city) and then discards them. Google signals and ad personalisation are turned off in our Google Analytics service. Purpose: traffic statistics for the site and the Studio, and measuring how many visits end with a new account or a purchase. Basis: your consent (Article 6(1)(a) GDPR). You can withdraw consent at any time with the "Cookie settings" button in the footer of the site and the Studio, without affecting the lawfulness of processing before the withdrawal; measurement then stops and we remove the_gaand_ga_<container-id>cookies from your browser. Not consenting does not limit your use of the Service. Google Ireland Limited acts as our processor for this, under Google’s data processing terms (Google Ads Data Processing Terms). The Cookies policy describes the details, including the Google consent mode settings.
Giving us your data is voluntary, but without an email address and the data needed for payment we cannot create an account or sell access.
4. Who receives data
We share only data needed for the task. A supplier may act as a processor under a data processing agreement, or as a separate controller for its own responsibilities. The Service involves these roles:
- MyDevil.net: hosting the public nobrainer.social website and its contact form, including technical data and handling the submitted enquiry. This role is separate from Studio hosting; Studio materials are not thereby sent to the form.
- Vercel Inc.: application hosting and execution, including requests and technical data. A processor for hosting.
- Supabase: database, authentication and private file storage. A processor for these services. The project region recorded in deployment documentation is Frankfurt, Germany (
eu-central-1). - OpenRouter and suppliers of the AI models called: processing brand descriptions, selected materials and instructions to generate text and graphics. OpenRouter provides access to models. Data scope depends on the task; this does not mean sharing the whole Studio database. Further suppliers’ roles and terms depend on the model and service selected. We provide information about a specific recipient on request.
- Resend: application messages and authentication emails, to the extent this service is used. It receives the recipient’s address and message content, not all Studio content.
- Stripe: payments and related billing data. You submit card details directly to Stripe. Stripe is a separate controller for its own regulatory, security and fraud-prevention purposes.
- Meta Platforms: Facebook and Instagram. We share selected materials and data needed for authorised publication; we retrieve comments and messages if you enable that feature. Meta acts as a separate controller on its platforms under its own rules.
- Meta Platforms Ireland Limited (4 Grand Canal Square, Grand Canal Harbour, Dublin 2, Ireland), only if you consent to marketing cookies: the recipient of the Meta Pixel data described in clause 3.10, for measuring how our ads perform. Clause 3.10 describes Meta’s role.
- Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland): reCAPTCHA protecting the newsletter form on the offer page (clause 3.11). Google receives the technical data described there and processes it under Google’s Privacy Policy.
- Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland), only if you consent to analytical cookies: Google Analytics 4, the traffic statistics described in clause 3.13. A processor under Google’s data processing terms (Google Ads Data Processing Terms).
- Three Hearts Digital Ltd, trading as EmailOctopus (86-90 Paul Street, London EC2A 4NE, United Kingdom, company number 09897211): sending the newsletter and storing the subscriber list (clause 3.12). A processor under the data processing agreement built into the EmailOctopus Terms of Use (Schedule 2). According to EmailOctopus, contact lists are stored with Amazon Web Services in the European Union, primarily in Ireland, and messages are sent from servers in the EU.
- Google, if you choose Google sign-in: authentication under Google’s rules; we receive data needed to link the account, not your Google password. Google is a separate controller for its service.
The Provider issues VAT invoices. Invoice details go to billing administration; a Stripe confirmation is not presumed to be an invoice. Where accounting or legal administration requires an authorised service provider, we share only necessary data under confidentiality and the appropriate legal basis or processing agreement. This does not give it access to the whole Studio’s materials. On request we will identify the recipient involved in your billing.
We may also disclose data to public authorities when required by law. We do not sell personal data. Changes to processors of entrusted data follow section 15 of the Terms of Service.
5. Transfers outside the European Economic Area
The Supabase project region in Frankfurt and the Frankfurt function region (fra1) specified in Vercel configuration do not mean that all supplier operations take place in the EEA. Global infrastructure, support and further suppliers may involve processing outside the EEA, particularly in the United States. The location of AI processing depends on the recipient of the request; we do not guarantee an exclusively European route.
Our transfers outside the EEA require a Chapter V GDPR mechanism: a European Commission adequacy decision where it covers the recipient and transfer, or appropriate safeguards, in particular standard contractual clauses (SCCs) together with transfer assessment and supplementary measures where needed. A region selection or supplier name does not replace these requirements.
Vercel, Supabase and Resend publish processing agreements and transfer safeguard information: Vercel DPA, Supabase DPA, Resend DPA. OpenRouter describes the data it shares in its privacy policy. Google (for reCAPTCHA and Google sign-in), Stripe and Meta describe their own controller processing in their policies. Meta Platforms Ireland Limited may transfer Meta Pixel data to Meta Platforms, Inc. in the United States; Meta names the European Commission’s adequacy decision on the EU-US Data Privacy Framework and standard contractual clauses as the basis for such transfers. EmailOctopus operates from the United Kingdom, for which the European Commission has found an adequate level of data protection; according to the EmailOctopus privacy policy, some of its features (AI content moderation) may run in other AWS regions, including the United States, under the EU-US Data Privacy Framework or standard contractual clauses. Google Ireland Limited may transfer reCAPTCHA data to Google LLC in the United States; Google names the EU-US Data Privacy Framework and standard contractual clauses as the basis. Google Ireland Limited may transfer Google Analytics 4 data to Google LLC in the United States; Google LLC is certified under the EU-US Data Privacy Framework, and the standard contractual clauses in Google’s data processing terms are an additional safeguard. Information about specific recipients, countries and transfer grounds, and a copy of the relevant safeguards, is available by emailing arkadiusz@mastalerz.it. Publication of a supplier’s agreement template does not confirm its execution for a particular account.
6. How long we keep data
- Account and Studio: for the duration of use and for 30 days after the last paid access ends, to allow renewal or export, then we delete Studio data. An export requested in time extends retention of data needed to prepare it until delivery and for 7 days for download, not indefinitely. JSON/CSV exports and archives have links valid for 24 hours after creation; we can prepare them again within the additional window. You can request earlier deletion. Deleting a personal account does not delete Studio data used by other people; the last owner must transfer that role or delete the Studio first. We keep account data needed for other active Studios for the duration of that use. An account that has never had paid access can be deleted on request or in settings; this does not retain data from an expired paid Studio.
- Accounting documents and billing data: for the statutory period, generally five years from the end of the calendar year in which the tax payment deadline fell. Retention may be longer if law or proceedings require it.
- Document acceptances, complaints and billing evidence: for the contract duration and until the applicable limitation period for claims expires, or until proceedings conclude with a final decision. We retain only data needed for that purpose.
- Security and error events: up to 90 days after the event. Separate information needed to investigate an incident, meet a legal obligation or protect claims is kept until that purpose ends. Studio content does not thereby become an ordinary part of logs.
- Traffic and ad measurement (with consent): your cookie choice (
nbs_consent) for 12 months; thenbs_attributioncookie in your browser for 30 days from the last visit with tags; the_fbpand_fbccookies for 90 days; the_gaand_ga_<container-id>cookies for up to 2 years (Google’s default lifetime). Google Analytics 4 event-level data is kept for at most 14 months; aggregate statistics that do not identify you may remain in reports for longer. We keep the email to the administrator of the Service about the source of a new account for up to 12 months after the account is created, then delete it. Meta keeps the data it received under its own policy. We keep newsletter subscriber data until you unsubscribe or withdraw consent, subject to the unsubscribe marker described in clause 3.12. We do not receive reCAPTCHA data; Google keeps it under its own policy, and the_GRECAPTCHAcookie for up to 6 months. When you withdraw consent, we remove the analytical or marketing cookies it covered from your browser and collect no new data. - Backups: up to 30 days after creation, solely for disaster recovery. Data deleted from the active system may remain in an isolated backup until that cycle ends; we do not use it for ordinary operations. Restoration uses the deletion registry to avoid returning erased data to use. Isolated copies required by law are an exception.
After Studio deletion, file removal may require several stages and retries. This does not keep the deleted Studio active. We do not keep data longer simply because an export was prepared earlier. Limited deletion records prevent data from being restored from backups.
7. Your rights
You have the right to access your data, rectify it, erase it, restrict processing, data portability (you will find an export in JSON and CSV in the Studio settings), to object to processing based on legitimate interest, and to withdraw consent where you gave it, without affecting earlier processing. You can withdraw consent to analytical and marketing cookies with the "Cookie settings" button in the footer of the site and the Studio. You can delete your account and Studio in settings under the conditions above and in the terms. Requests concerning entrusted data in another person’s Studio are forwarded to its controller. For anything else write to arkadiusz@mastalerz.it. We reply within one month of receipt. If law permits an extension due to complexity or the number of requests, we explain the reason and new deadline within that month.
You also have the right to lodge a complaint with the President of the Personal Data Protection Office in Poland (UODO, ul. Stanisława Moniuszki 1A, 00-014 Warszawa; UODO contact) or with the authority in your own country.
8. Security
We protect data with, among other things, an encrypted connection, encryption of the access keys to social accounts, separation of the data of each Studio and optional two-step verification on the account. No system is fully immune to incidents. If a breach affects your data, we will tell you as the law requires.
9. Changes to this policy
When we change the policy we publish a new version with a date and a number. We tell you about important changes by email or in the Studio.