Terms of Service

These Terms govern your use of Pixelary. Please read them together with the Privacy Policy and the Data Processing Agreement, which forms part of these Terms.

1. Who we are and how these Terms apply

1.1. Pixelary is provided by Oleksii Ukrainskyi, a sole proprietorship (jednoosobowa działalność gospodarcza) entered in the Polish business register CEIDG, ul. Ceramiczna 5c/58, 03-126 Warszawa, Poland, NIP 5242785728, REGON 521840030 (“Pixelary”, “we”, “us”). Contact: hello@pixelary.app.

1.2. These Terms are a contract between us and the person or organization that creates a Pixelary account or uses the Service (“you”, the “Customer”). If you accept them for an organization, you confirm that you may bind it.

1.3. You accept these Terms when you create an account, or when you sign in after being shown these Terms. For accounts that existed before 28 October 2026, these Terms apply 30 days after we tell you about them in the dashboard or the Framer plugin, or by email; until then the terms you accepted earlier apply, and you may stop using the Service before then.

2. Definitions

• Service: the Pixelary script, the dashboard (app.pixelary.app), our servers and APIs, the Framer plugin, the Google Tag Manager template and the documentation on pixelary.app.
• Site: one domain with its staging and preview addresses. A subdomain with its own pixels counts as a separate site.
• Visitor: a person who visits one of your sites.
• Destination: an advertising platform you connect to a site: Meta, TikTok or ChatGPT Ads (OpenAI).
• Browser pixel: a destination’s own script, which Pixelary loads in the visitor’s browser.
• Server event: an event the Pixelary script sends to our servers for a site with server-side delivery, counted when we receive it, whether or not we then forward it.
• Server-side delivery: forwarding server events to the destinations’ Conversions APIs (Meta Conversions API, TikTok Events API, ChatGPT Ads Conversions API).

3. Who may use Pixelary

3.1. Pixelary is built for website owners and businesses. You must be at least 18 years old and have the authority to act for the website or business you connect.

3.2. You may connect only sites you own or are authorized to manage, and only advertising accounts you are authorized to use.

3.3. The Service is offered only to businesses and professionals, for their business. By using it, you confirm that you use it that way. Consumers may not use the Service. If mandatory law still gives you consumer rights (including the Polish rules for sole traders who act outside their professional activity, art. 385⁵ of the Civil Code and related provisions), those rights apply and nothing in these Terms limits them.

4. The Service

4.1. What Pixelary does. Pixelary sends conversion events from your sites to the destinations you connect. In particular it:

• tracks page views, form submissions, clicks, scroll depth and bookings in embedded tools, according to the triggers you set up, and events your own code or Google Tag Manager passes to it;
• reads your visitors’ consent from your cookie banner, IAB TCF, Google Consent Mode or your own code, and holds back what consent does not allow;
• loads the destinations’ browser pixels on your sites;
• on paid plans, sends a copy of each event from our servers to the destinations’ Conversions APIs, with the same event ID, so the destination can count it once;
• on paid plans, keeps an event log you can view and export (section 6.3).

How the Service handles personal data is described in the Privacy Policy and the Data Processing Agreement.

4.2. We are not the destinations. We are not affiliated with Meta, TikTok or OpenAI. We do not control whether they accept, match, attribute or report your events, how they use the data they receive, or whether they restrict your advertising accounts.

4.3. Features in development. Features marked “soon” on our website or in the dashboard are not part of the Service until we release them.

4.4. The older Framer plugin tag. Sites installed with earlier versions of the Framer plugin may still run the older tag (framer.js). It keeps working, but it does not include the current consent handling (it loads the browser pixels before consent unless your site tells it otherwise) and receives no new features. You should move to the current script. The older tag stays supported while live sites use it, with no fixed end date. We will give at least 60 days’ notice in the dashboard and the Framer plugin before ending it, and we remove it once no site has sent an event with it for 30 days.

5. Your account and team

5.1. You sign in with Google or with a code sent to your email address. Keep access to your Google account and email secure. You are responsible for everything done through your account.

5.2. On plans that include a team, you can invite other people as Editor or Viewer. Each account has one Owner. The roles allow:

• Owner: everything, including access tokens, billing, the team and the deletion of sites;
• Editor: the pixels, triggers, domains and settings of the sites shared with them, but not access tokens, billing or the team;
• Viewer: reading events, stats and settings.

You are responsible for the people you invite and for what they do in your account.

5.3. Team size per plan:

6. Plans, prices and payment

6.1. Plans.

Prices are in US dollars and are shown without VAT or sales tax. Lemon Squeezy, as merchant of record, adds the tax that applies at checkout and issues the invoice. For more than 10 sites, write to us.

6.2. What every plan includes. Browser pixels for Meta, TikTok and ChatGPT Ads, triggers, consent handling, the Framer plugin, the Google Tag Manager template and the HTML snippet are included on every plan, including Free.

6.3. What paid plans add. Server-side delivery for the number of sites in the plan, the event log (kept 30 days on the 1-site and 5-site plans and 90 days on the 10-site plan) with CSV export, and team members as in section 5.3.

6.4. Merchant of record. Paid plans are sold by Lemon Squeezy, which acts as merchant of record. Lemon Squeezy takes the payment, charges tax and issues invoices. Its buyer terms (https://www.lemonsqueezy.com/buyer-terms) govern the purchase and the payment; these Terms govern the Service. Your billing details and invoices are in the Lemon Squeezy customer portal, linked from Billing in the dashboard.

6.5. Renewal. Subscriptions renew automatically at the end of each monthly or yearly period until you cancel. Lemon Squeezy charges the payment method on file.

6.6. Changing plans. You can upgrade, downgrade or switch between monthly and yearly billing in Billing. An upgrade takes effect at once and is prorated for the rest of the billing period; a downgrade takes effect at the next renewal. If you add a site beyond your plan’s limit, that site keeps working with browser pixels only until you upgrade.

6.7. Cancellation. You can cancel at any time in Billing. Server-side delivery keeps running until the end of the period you paid for. After that, your sites fall back to the Free plan: browser pixels keep firing and nothing is sent from our servers. The event log stops recording, and its existing entries are deleted on the normal schedule (section 6.3). Team members lose access, as the Free plan includes only the owner (section 5.3); the owner keeps access.

6.8. Refunds. Payments are not refunded for partial periods or unused time, except where the law requires it or we decide otherwise in a specific case. Refunds are paid by Lemon Squeezy.

6.9. Trials. There is no free trial of paid plans. The Free plan is free, with no time limit.

6.10. Price changes. We may change prices for future billing periods. We will tell you at least 30 days before a change applies to your subscription, and you may cancel before it does.

6.11. Existing plugin subscriptions. Subscriptions bought through the Framer plugin before 28 October 2026 continue as the 1-site plan at their current price.

7. Fair use

7.1. Every plan includes up to 1,000,000 server events per site per calendar month (UTC).

7.2. Above that limit, server-side PageView events are counted and shown in the event log as “counted”, but not forwarded to the destinations. All other events are still sent and logged. Browser pixels are not limited.

7.3. To protect the Service, our servers drop requests and events that look automated (for example crawler user agents, headless browsers, very high event rates from one visitor, and page views from data-center networks), may sample the Free plan’s session summaries, and may limit traffic from a site that overloads the Service. If a site needs much more capacity, we will contact you to agree on a plan.

8. Your responsibilities

8.1. Consent and legal basis. You decide whether and how Pixelary runs on your sites, which destinations receive data and what counts as an event. You are the controller of your visitors’ personal data (for sites you manage for clients, see section 9). You are responsible for:

• having a valid legal basis for the tracking and for sharing visitor data with the destinations, including consent where the law requires it (for example under the GDPR and the ePrivacy rules for cookies and similar technologies);
• running a cookie banner or consent tool that collects that consent, and making sure Pixelary receives the answer (from a supported banner, IAB TCF, Google Consent Mode or a pixelary('consent', …) call);
• choosing the consent defaults on the Consent screen. By default, Pixelary waits for consent from visitors in the EEA, the UK and Switzerland, and treats consent as given elsewhere unless your banner, your Consent Mode defaults, your settings or the visitor’s Global Privacy Control say otherwise. Check that these defaults match the law that applies to your visitors;
• telling your visitors, in your privacy notice, that you use Pixelary and the destinations, what data is shared and why.

Pixelary’s consent features are tools. They do not make your site compliant, and we do not give legal advice.

8.2. Data you must not send. Do not use Pixelary to collect or send:

• special categories of personal data (for example health, sexual orientation, religion, political opinions, biometric or genetic data) or data about criminal convictions, including information that reveals them through event names, parameters, page addresses or the pages you track;
• payment card numbers, bank account numbers, government ID numbers, passwords or access credentials;
• contact details or other personal data in event names, event IDs, custom parameters or page addresses. Use the user data fields, which Pixelary hashes;
• any data from websites or pages directed at children under 16. Pixelary must not be used on them.

8.3. Destination terms. You are responsible for complying with the terms and policies of each destination you connect, for example Meta’s Business Tools Terms and advertising policies, TikTok’s business terms and OpenAI’s terms for ChatGPT Ads, including their rules on sensitive data and on what you may send them. Your agreements with the destinations govern how they process the data.

8.4. Access tokens. You provide the access tokens and API keys for the destinations’ Conversions APIs, and you may revoke them in the destination at any time. We use them only to deliver your events and to check them when you save them. Use tokens that you are allowed to share with a service provider.

8.5. Domains and installation. Install Pixelary only on sites you control and add their domains to the site in the dashboard. Our servers accept events only from those domains. Events from staging addresses go to the destinations in test mode only.

8.6. Your configuration. Check that your triggers, event names, values and destinations do what you intend, for example with test mode and the event log. We are not responsible for events sent according to your configuration, or for events missing because of it.

9. Acceptable use

You must not:

• use the Service in breach of the law or of the destinations’ terms;
• send events that did not happen, or inflate or manipulate conversions;
• try to get around the fair-use limit, the domain check, consent handling or our security measures;
• access or try to access other customers’ data or sites;
• disrupt the Service, load-test it, or send malicious code through it;
• resell or white-label the Service without our written agreement.

Agencies may manage their clients’ sites within their own plan. The agency is then our customer, must have its client’s authority, and the client’s sites count towards the agency’s plan. For the visitor data of those sites, the client is the controller, the agency is its processor and Pixelary is the agency’s sub-processor (Data Processing Agreement, section 2.2).

We may suspend access that breaks this section (section 13).

10. Personal data

10.1. For your account data we act as controller, as described in the Privacy Policy.

10.2. For your visitors’ personal data that the Service processes on your behalf, we act as your processor under the Data Processing Agreement, which forms part of these Terms.

11. Availability and support

11.1. We work to keep the Service available and fast, but we provide it without a service level agreement. It may be interrupted for maintenance, updates, problems at our providers (such as Cloudflare or Supabase) or at the destinations, or events outside our control.

11.2. Events may be delayed, dropped or rejected, for example when a destination is unavailable or refuses an event, a token stops working, an ad blocker or browser setting stops the script, or our bot filter misjudges traffic. Pixelary does not retry failed deliveries today.

11.3. The destinations change their APIs and rules. We adapt the Service when they do, but some features may stop working or change.

11.4. Support is by email at hello@pixelary.app. We aim to answer within 2 business days, but we do not guarantee response times.

12. Intellectual property

12.1. We own the Service and its software. While these Terms apply, we give you a non-exclusive, non-transferable right to use the Service for your sites. The Google Tag Manager template is also published under the Apache License 2.0; that licence governs the template’s code.

12.2. You keep all rights in your data, your configuration and your sites. You allow us to use them to provide and support the Service.

12.3. If you send us feedback, we may use it without obligation to you.

13. Suspension

13.1. We may suspend your account, a site or server-side delivery if you seriously or repeatedly breach these Terms, if payment fails, if your use endangers the Service or other customers, or if the law or an authority requires it.

13.2. Before a suspension that is not urgent, we will tell you and give you 7 days to fix the problem. In urgent cases (a security risk, abuse, non-payment or a legal requirement) we may act at once, and we will tell you promptly.

14. Term, termination and your data

14.1. These Terms apply from your acceptance until your account is closed.

14.2. You may stop using the Service and ask us to close your account at any time by writing to hello@pixelary.app. Cancel any paid plan first (section 6.7).

14.3. We may terminate these Terms for convenience with 30 days’ notice, or immediately for a serious breach that is not fixed within 14 days after we tell you about it. If we terminate without cause, we refund the prepaid fees for the unused period, pro rata.

14.4. Your data after termination. Remove the Pixelary script from your sites. Export what you need from the event log before your account closes. When you delete your account in the dashboard, your account data, sites, settings and access tokens are deleted at once; if the account is closed another way, we delete them within 30 days. Event log entries are deleted by our daily retention job no later than the end of their retention period (30 or 90 days). Counts that identify no one may be kept. Details are in the Data Processing Agreement, section 12.

14.5. Free accounts with no sign-in and no events for 24 months may be deleted after 30 days’ notice by email.

14.6. Sections 8, 12, 15, 16 and 18 survive termination.

15. Warranties

To the extent the law allows, the Service is provided “as is” and “as available”. We do not promise that it will be uninterrupted or error-free, that every event will reach the destinations, or that using it will improve your advertising results.

16. Liability

16.1. Our total liability under these Terms is limited to the fees you paid us in the 12 months before the event giving rise to the claim. For Free accounts, it is limited to USD 100.

16.2. We are not liable for lost profits (utracone korzyści), indirect or consequential damage, loss of data or revenue, the suspension or restriction of your advertising accounts by the destinations, the destinations’ own processing or outages, or the performance of your ads.

16.3. Nothing in these Terms limits liability that cannot be limited by law. The limits in sections 16.1 and 16.2 do not apply to damage caused intentionally (art. 473 § 2 of the Polish Civil Code) or where the law does not allow liability to be limited.

16.4. You indemnify us against third-party claims, damages and costs, and, as far as the law allows, fines, arising from missing or invalid consent on your sites, from your configuration, or from data you send in breach of section 8.2.

17. Changes to these Terms

We may change these Terms. We will tell you about material changes by email or in the dashboard at least 30 days before they take effect. If you do not agree, you may cancel before the change applies. Changes required by law, or made for security, may take effect sooner.

18. Governing law and courts

18.1. These Terms are governed by Polish law. The UN Convention on Contracts for the International Sale of Goods (CISG) does not apply.

18.2. Disputes will be decided by the common court competent for our registered address in Warsaw.

18.3. If mandatory consumer protection rules apply to you despite section 3.3, nothing in these Terms limits them.

19. Other terms

19.1. These Terms, the Privacy Policy and the Data Processing Agreement are the whole agreement between you and us about the Service.

19.2. If a provision is invalid, the rest stays in force, and the invalid provision is replaced by a valid one as close as possible to its purpose.

19.3. You may not transfer these Terms without our consent. We may transfer them to a successor of the business, and we will tell you.

19.4. We send notices to your account’s email address or show them in the dashboard. Send notices to hello@pixelary.app.

19.5. These Terms are written in English only. There is no Polish version.