Bloxks Pay Terms of Service

Bloxks Pay is provided by Bloxks SAS, a simplified joint-stock company (SAS) with a share capital of €100.00, registered with the Paris Trade and Companies Register under number 130 543 515, whose registered office is at 47 rue Vivienne, 75002 Paris, France (“Bloxks”, “we”, “us”). Contact: contact@bloxks.app.

Bloxks Pay is a feature of the Bloxks platform. You use it with your Bloxks account, so the Bloxks Terms of Use and the Bloxks Terms and Conditions of Sale continue to apply. These Bloxks Pay Terms supplement them for everything that concerns Bloxks Pay.

The following documents form a single agreement between you and Bloxks (the “Agreement”). If they conflict, they apply in this order:

• the Bloxks Pay Data Processing Addendum (the “DPA”), for anything relating to the processing of personal data on your behalf;
• these Bloxks Pay Terms, for anything relating to Bloxks Pay;
• the Bloxks Terms of Use and Terms and Conditions of Sale, for everything else.

In particular, Article 4.4 of the Bloxks Terms of Use (financial independence from your apps) remains true for Bloxks Pay: we never collect or hold the money your apps earn. Section 17 below explains how fees for Bloxks Pay itself could be introduced in the future.

How we process personal data about you and your team as a controller is explained in the Bloxks Pay Privacy Policy.

In these Terms, the following words have the meaning given below, whether used in the singular or the plural.

• “App” means a mobile application that you publish or plan to publish, and for which you enable Bloxks Pay.
• “App Store” means the Apple App Store. “Google Play” means the Google Play Store, which Bloxks Pay will cover only when we announce that it is supported. “Stores” means the App Store and, once supported, Google Play.
• “Store Account” means your Apple Developer / App Store Connect account or, once supported, your Google Play Console account.
• “Store Credentials” means the credentials you give us to act on your Store Account, as described in Section 7.
• “End User” means a person who uses your App and may buy digital content or subscriptions in it.
• “Customer Data” means all data that Bloxks Pay processes for your Apps: purchase and transaction records, store notifications, subscription states, entitlements, consumable credits, End User identifiers, product catalogue, configuration and similar data.
• “Service” means Bloxks Pay: its dashboard, its SDK, its API, its server-side processing and the related documentation.
• “SDK” means the Bloxks Pay software library that Bloxks adds to your App.
• “API Keys” means the publishable key (starting with bxpay_pub_) and the secret key (starting with bxpay_sk_) issued for each App.
• “Integration” means an outgoing destination you configure in Bloxks Pay, such as a webhook URL, a Slack channel or a Discord channel.
• “you” or the “Developer” means the business or professional who uses Bloxks Pay, and the people it authorises to use its Bloxks account.

Bloxks Pay is a business-to-business service. You may use it only for purposes related to your trade, business, craft or profession, for example to sell digital content in an App you publish. You are not using it as a consumer.

If you accept these Terms on behalf of a company or another legal entity, you confirm that you have the authority to bind it. If you are an individual acting as a sole trader or freelancer, you confirm that you act in a professional capacity.

You must hold a valid Bloxks account and a Store Account in your own name or in the name of your business. During the beta, we may limit access to Bloxks Pay to certain accounts or regions.

Bloxks Pay helps you manage in-app purchases and subscriptions in your Apps. Depending on what is available for your account, it lets you:

• verify the signed purchase records issued by the Stores, and restore purchases;
• work out which End Users have access to which content (entitlements), and grant or revoke access manually;
• receive and process the Stores’ server notifications (App Store Server Notifications and, once supported, Google Play Real-time developer notifications) and query the Stores’ server APIs to keep subscription states up to date;
• credit consumable purchases (such as coins or lives) once per transaction through your own server;
• view revenue figures, charts, customer and payment lists, and export them;
• send information to Apple when Apple asks about a refund request, if you choose to (Section 13);
• create offer or promotional codes in your Store Account at your request (Section 14);
• send events to the Integrations you choose (Section 15).

Today, Bloxks Pay supports iOS apps distributed through the App Store. Google Play support is planned. Where these Terms mention Google Play, they describe how the Service will work once Google Play is supported; they do not mean it is available now.

We may improve, change or remove features over time, in particular during the beta. Section 27 explains how we tell you about significant changes.

The Stores sell your in-app products to End Users and are the merchant of record for those sales. Under your agreements with Apple and, once supported, Google, they collect payment, handle the taxes they are responsible for, decide on refunds and chargebacks, and pay out your proceeds.

Bloxks Pay does not take part in any of this. In particular, Bloxks:

• never receives, holds, transfers or pays out funds belonging to you or to End Users;
• never sees or stores End Users’ card or bank details;
• does not decide on, issue or pay any refund, and does not handle chargebacks;
• does not collect, calculate or pay any tax on your sales;
• is not your agent for selling to End Users, and is not a party to the sale between the Store and the End User.

Payments, taxes, refunds, chargebacks and payouts remain matters between the End User, the Store and you. Any question about them should be raised with the Store concerned.

You are bound by your own agreements with the Stores, including the Apple Developer Program License Agreement, the App Review Guidelines, the Google Play Developer Distribution Agreement, the Google Play Developer Program Policies and the Google Play Developer API Terms (together, the “Store Terms”). These Bloxks Pay Terms do not change them.

When Bloxks Pay uses your Store Credentials or receives data from the Stores, it acts as your service provider, solely on your behalf and for your Apps. Bloxks will:

• use Store services, Store data and Store Credentials only to provide the Service to you and to carry out what you authorise in these Terms (including the publication of App revenue figures under section 12), and never for any other developer;
• keep confidential any information that the Store Terms treat as confidential, and protect it at least as well as the Store Terms require of you;
• use data obtained from Store APIs only for the purposes those APIs allow (for example, data about voided Google Play purchases only to revoke access and prevent fraud);
• stop using a Store service on your behalf if the Store asks you or us to do so.

These commitments are the written agreement that the Store Terms require between you and a service provider acting on your behalf. Where the Store Terms impose other obligations on such a service provider, Bloxks will comply with them as far as they relate to the Service.

You remain responsible to the Stores for your Store Account. The Stores may change their services, rules or APIs, limit access to them, or take decisions about your Apps and your Store Account at any time. Bloxks does not control those decisions and is not responsible for them, nor for any Store outage. We will make reasonable efforts to adapt the Service to Store changes, but some features may stop working, in whole or in part, as a result.

To run the Service, you give us credentials that let us act on your Store Account. Depending on the Store and the features you use, they may include:

• for the App Store: your App Store Connect API key (Issuer ID, Key ID and private key) and your In-App Purchase key;
• for Google Play, once supported: a Google Cloud service-account key with access to your Play Console.

We use Store Credentials only to provide the Service you ask for: for example, to verify transactions, read subscription states and transaction history, configure where the Store sends its server notifications, answer refund-related requests you have enabled, and create offer codes you request. We do not use them for anything else.

We store Store Credentials encrypted, we never display them again after you provide them, and we decrypt them only in server memory when a request needs them. Access by our staff is limited to what is strictly needed for security and support.

You should give credentials with the narrowest permissions the Service needs. You can revoke them at any time in App Store Connect (or, once supported, in Google Play Console); revocation takes effect at the Store immediately. To have us delete the copies we hold, write to contact@bloxks.app: we delete them within 30 days of your request. Once revoked, the features that depend on them stop working. You are responsible for rotating your keys if you believe they have been exposed, and for keeping the credentials you give us valid.

If we become aware that your Store Credentials may have been compromised while in our care, we will tell you without undue delay so that you can revoke them.

We are not responsible for any measure that a Store takes regarding your Store Account or your Apps, unless it results from our own failure to comply with these Terms.

Subject to these Terms, we grant you a non-exclusive, non-transferable, worldwide and royalty-free right, for as long as you use Bloxks Pay, to include the SDK in your Apps and to call the Bloxks Pay API, solely to use the Service.

The publishable key is meant to be embedded in your App. The secret key must stay on your servers and must never be included in an App, a public repository or a web page. We store API Keys only in hashed form and show them once. If you ask us to, Bloxks can write your secret key into a database project you have connected to your Bloxks account. You are responsible for all activity carried out with your API Keys, and you should revoke and replace any key you believe has been exposed.

We may apply reasonable rate limits and usage limits to protect the Service. We may release new versions of the SDK and API and retire old ones. When a retirement requires you to update your App, we will give you reasonable notice, except where an immediate change is needed for security or to comply with Store rules or the law.

You are responsible for your Apps, your Store Account, your products and your relationship with your End Users. In particular, you agree to:

• comply with the Store Terms and with the laws that apply to your Apps, including consumer protection, data protection and tax laws;
• meet your obligations as controller set out in Section 4 of the DPA, in particular naming Bloxks Pay in your App’s privacy policy and Store privacy disclosures;
• make sure the products, prices, entitlements and settings you configure in the Stores and in Bloxks Pay are accurate, and check that your Apps unlock the right content;
• keep your Store Credentials and API Keys valid, confidential and up to date;
• give End Users a way to restore purchases they have made, as the Stores require;
• use manual access grants only in ways the Store Terms allow, and not to bypass Store billing;
• not use Bloxks Pay to process data about children in breach of the rules that protect them;
• tell us promptly at contact@bloxks.app if you notice a security issue or an error in the Service.

The information you configure (such as your refund preference or your Integrations) is treated as your instruction, and we act on it as you have set it.

In addition to the prohibited uses listed in Article 5 of the Bloxks Terms of Use, you must not use Bloxks Pay to:

• submit forged, altered or replayed purchase records, or otherwise defraud a Store, an End User or Bloxks;
• process purchases for apps that you do not own or are not authorised to manage;
• sell or transfer offer codes, virtual currency or access in breach of the Store Terms;
• disrupt, overload, probe or bypass the security or limits of the Service, or access it other than through the means we provide;
• copy, reverse engineer or resell the Service, or use it to build a competing service;
• carry out any activity that is illegal or that breaches the rights of others.

You confirm that neither you nor the business you represent is subject to sanctions or restrictive measures adopted by the European Union, France, the United Nations or the United States, nor owned or controlled by such a person. You must not use the Service for Apps, End Users or activities in countries or regions subject to comprehensive sanctions under those rules.

For personal data about End Users that Bloxks Pay processes for your Apps (such as End User identifiers, purchase and subscription records and store country), you are the controller and Bloxks is your processor. That processing is governed by the Bloxks Pay Data Processing Addendum, which forms part of these Terms and which you accept by accepting them.

For personal data about you and the people who use your Bloxks account (such as identity, login and support data), Bloxks is the controller, as explained in the Bloxks Pay Privacy Policy and the Bloxks Privacy Policy.

Where and how Customer Data is hosted, including any transfer outside the European Union, and the list of our subprocessors, are described in the DPA.

As between you and Bloxks, you keep all rights in your Customer Data. You grant us a non-exclusive, worldwide, royalty-free licence to host, process, copy and display Customer Data only as needed to provide, secure and support the Service, for the duration of the Agreement and any export period after it ends.

We may produce statistics from the use of the Service (for example, the number of transactions processed or the error rate of an API), provided that they are aggregated and anonymised so that they identify neither you, nor your Apps, nor any End User, apart from the showcase described below. We may use them to operate and improve our services. The other limited uses we make of data for our own purposes are listed in Section 2 of the DPA.

Showcase of your Apps. Under Article 4.6 of the bloxks.app Terms of Use, which you accept with your Bloxks account, you authorise Bloxks to display on its website, social media and promotional materials the name, icon, store screenshots and store link of your published Apps, together with their revenue figures measured by Bloxks Pay. You may object at any time to the publication of exact figures by writing to support@bloxks.app; approximate figures that do not reveal the exact amount (rounded down to the nearest thousand euros, to the nearest 10% above €10,000, or shown as a range) may still be published. No End User data is ever published.

Bloxks Pay, its SDK, its API, its dashboard, its documentation and all related technology remain the exclusive property of Bloxks. Except for the rights expressly granted in these Terms, no right is transferred to you.

If you send us suggestions or feedback, we may use them freely and without any obligation to you.

When an End User asks a Store for a refund, the Store alone decides whether to grant it. Some Stores let the developer send information that the Store takes into account. On the App Store, for example, Apple may ask for consumption information about a purchase.

Bloxks Pay sends such information only if you have turned the feature on: you choose a refund preference in Bloxks Pay and confirm that your End Users have agreed to this information being shared with the Store. If you have not done both, Bloxks Pay sends nothing. When it does send information, it does so in your name and on your instructions.

You are responsible for the preference you choose, for obtaining and documenting End Users’ consent, for describing this sharing in your App’s privacy policy, and for making sure the information is accurate. Bloxks has no say in the Store’s decision and is not responsible for it, whether the refund is granted or refused.

At your request, Bloxks can create offer codes or promotional codes in your Store Account using your Store Credentials, and Bloxks Pay can track how they are redeemed. We create codes only when you ask us to, with the settings you choose.

You are the issuer of these codes. You are solely responsible for their terms and conditions, for how and to whom they are distributed, for the information you must give End Users under the Store Terms and consumer law, and for honouring them. The Store Terms apply to them: for example, codes may not be sold, and a Store may limit, deactivate or refuse them.

Bloxks is not responsible if codes run out, expire, are deactivated by a Store, or are redeemed by people you did not intend to receive them.

You can ask Bloxks Pay to send events about your Apps (such as purchases, renewals, refunds and new customers) to Integrations you choose. Each event may include information about the transaction and, for some events, an End User identifier.

Integrations are third parties chosen by you, not subprocessors of Bloxks. We send data to them on your instructions and under your responsibility. Their use of that data is governed by your own agreements with them, and you must describe these recipients in your App’s privacy policy where required.

We sign webhook requests so that you can check they come from Bloxks Pay, and we retry failed deliveries for a limited time. Delivery is provided on a best-effort basis: you should not rely on webhooks as your only record of events, and you are responsible for securing the endpoints you configure.

The revenue, proceeds, recurring revenue (MRR), conversion, refund and other figures shown in Bloxks Pay are estimates provided for information. They are calculated from the data the Stores send us and may differ from the amounts you actually receive. In particular:

• amounts in other currencies are converted using monthly reference exchange rates, which differ from the rates the Stores apply;
• Store commissions and taxes are estimated;
• figures can change when the Stores send late notifications, refunds or corrections.

These figures are not accounting, tax or financial records. The financial reports and payments issued by the Stores always prevail, and you should rely on them for your accounting and tax returns.

Bloxks Pay is free during the beta: we charge no fee for it, whatever your Apps earn.

We may introduce fees for Bloxks Pay in the future. If we do, we will tell you at least 30 days before they apply, by email and in the dashboard, with the amount and how it is calculated. Fees will never apply to any period before they take effect. If you do not accept them, you may stop using Bloxks Pay before they take effect, without any charge, as described in Section 20.

Once fees apply, they will be invoiced by Bloxks under the Bloxks Terms and Conditions of Sale, including their late-payment terms for professionals, unless the notice says otherwise.

We use reasonable efforts to keep Bloxks Pay available, secure and accurate, and to fix errors brought to our attention. The Service may nonetheless be interrupted for maintenance, updates or reasons beyond our control, such as a failure of a Store or of a hosting provider. During the beta we do not offer any service level agreement (SLA).

Bloxks Pay relies on services that Bloxks does not control: the Stores’ servers, APIs and notifications, the networks, and our hosting providers. A Store may send a notification late, out of order or not at all, its APIs may be slow or unavailable, and the connection between a Store and our servers may fail temporarily. In such cases, a purchase, renewal, refund or change of access may appear in Bloxks Pay, or reach your App, with a delay. Bloxks Pay then resynchronises with the Stores as soon as possible, in particular through automatic retries, scheduled checks and the restore function of the SDK. The Stores’ records always prevail. Since the Store remains the merchant of record (Section 5), such a delay does not affect the End User’s payment or the Store’s record of it.

These interruptions, delays and synchronisation errors are an inherent risk of a service connected to third-party platforms, and you accept this risk by using Bloxks Pay. They do not in themselves constitute a breach of these Terms, and they give rise to no refund, service credit, fee reduction or compensation, during the beta or after fees are introduced. Only where they result from Bloxks’s own failure to act with the reasonable care described in Section 22 may you claim compensation, within the limits of Section 23.

The SDK keeps a local copy of each End User’s access on the device, so that your App can keep working for a limited time if Bloxks Pay cannot be reached. You should design your App to behave sensibly if Bloxks Pay is temporarily unavailable.

Support is provided by email at support@bloxks.app and through the Bloxks support chat, on a reasonable-efforts basis.

We may suspend all or part of your access to Bloxks Pay, without prior notice, if this is reasonably necessary to:

• deal with a security risk to the Service, to other developers or to End Users;
• stop fraud, abuse or a serious breach of these Terms;
• comply with the law, an order of an authority or a request from a Store.

In other cases of breach, we will first ask you to remedy it and give you a reasonable time to do so. We will tell you the reasons for any suspension in writing, limit it to what is necessary, and lift it as soon as the reason has gone. Where we can do so safely, we will keep purchase verification running for your End Users during a suspension.

These Terms apply from the first time you enable or use Bloxks Pay until they are terminated.

You may stop using Bloxks Pay at any time, without notice, reason or charge, by turning it off for your Apps, revoking your Store Credentials and API Keys, and removing the SDK from your Apps, or by writing to contact@bloxks.app. Closing your Bloxks account also ends your use of Bloxks Pay.

We may terminate these Terms:

• with at least 60 days’ notice, if we end the beta without a successor offer or stop providing Bloxks Pay;
• with 15 days’ notice, if you commit a serious breach of these Terms and do not remedy it within that period;
• immediately, in the event of fraud or of a breach that makes it impossible to continue, or if a Store or an authority requires it.

Before you stop using Bloxks Pay, plan how your Apps will check purchases afterwards: once Bloxks Pay is turned off and the local copy on devices expires, the SDK will no longer unlock content. If you move to another provider or to your own system, we will cooperate in good faith during a transition period of up to 30 days, and we will not charge you for switching or for exporting your data.

Sections 5, 12, 13, 14, 15, 16, 21, 22, 23, 24, 25, 28 and 29, and any other provision that by its nature should continue, survive the end of these Terms.

You can export customer and payment lists from the dashboard at any time. You can also ask us, at contact@bloxks.app, for a full export of your Customer Data. We will provide it within 30 days, free of charge, in a commonly used, machine-readable format (such as CSV or JSON).

Before you delete your data, export the entitlements and consumable balances of your End Users. The Stores require that purchases can be restored, and once your data is deleted we can no longer help your App do so.

You may ask us at contact@bloxks.app, at any time, to delete the Customer Data of one or all of your Apps. We will delete it within 30 days of your request. After these Terms end (including when you close your Bloxks account), you have 30 days to request an export; we then delete your Customer Data within the following 30 days, so no later than 60 days after the end of these Terms, unless you ask us to do so sooner.

Copies in our backups are removed as the backups are overwritten in the normal cycle described in the DPA. We may keep data longer only where the law requires it, and only for that purpose. Our copies of your Store Credentials are deleted on the same timeline: within 30 days of your request, and in any case with the rest of your Customer Data after these Terms end.

Each party warrants that it has the right to enter into these Terms. You warrant that you have the rights and permissions needed to give us your Store Credentials and Customer Data and to instruct us as provided in these Terms.

Bloxks provides Bloxks Pay as a beta, “as is” and “as available”, under an obligation of means (obligation de moyens). Within the limits allowed by law, we do not warrant that the Service will be uninterrupted or error-free, that it will meet all of your needs, or that it will keep working with every future version of the Stores’ services. Nothing in these Terms limits our obligation to perform the essential purpose of the Service with reasonable care.

Each party is liable for the direct and foreseeable damage caused by its own breach of the Agreement, under the conditions below.

Neither party is liable for indirect damage, such as loss of profit, revenue, customers, opportunity or reputation, except under the indemnities in Section 24. In addition, Bloxks is not liable for:

• damage caused by a Store, by an Integration or other third party you have chosen, or by a failure of a Store’s services, including lost sales during a Store outage;
• interruptions, delays or errors in the exchange of data between a Store and Bloxks Pay, as described in Section 18, that do not result from Bloxks’s own failure, and their consequences for your Apps and End Users, such as access granted or withdrawn late;
• damage resulting from your own configuration, products, Apps, instructions or breach of these Terms, or from the misuse or exposure of your Store Credentials or API Keys outside our systems;
• decisions taken on the basis of the estimated figures described in Section 16.

Bloxks’s total liability under the Agreement for Bloxks Pay, for all claims combined, is limited to the greater of (a) the amounts, excluding tax, that you paid for Bloxks Pay during the twelve months before the event giving rise to the claim, and (b) €1,000.

These limits do not apply in case of gross negligence or wilful misconduct, for personal injury, or where the law does not allow liability to be limited. They do not deprive Bloxks’s essential obligations of their substance, and they do not prevent the application of Article 82 of the GDPR to End Users.

Any claim must be brought within one year of the date on which the claimant became aware, or should have become aware, of the facts giving rise to it, to the extent permitted by law.

You will compensate Bloxks for the costs, damages and reasonable legal fees resulting from a claim by a third party (including a Store, an End User or an authority) to the extent that the claim results from your Apps, your offer codes, your Integrations, your instructions, the Customer Data you provide, or your breach of these Terms, the Store Terms or the law.

Bloxks will compensate you, within the limits of Section 23, for the costs, damages and reasonable legal fees resulting from a claim by a third party that the Service, used in accordance with these Terms, infringes that third party’s intellectual property rights.

The party seeking compensation must tell the other party promptly about the claim, let it lead the defence and any settlement, and cooperate reasonably. A party’s obligation is reduced to the extent that the other party contributed to the damage.

Each party will keep confidential the non-public information it receives from the other in connection with Bloxks Pay, including your Customer Data, your Store Credentials, your API Keys and our non-public technical information. It will use that information only to perform the Agreement and will disclose it only to people who need to know it and are bound by similar duties, or where the law or an authority requires it. Revenue figures that Bloxks may publish under section 12 are not covered by this duty.

This duty does not cover information that is public through no fault of the receiving party, that it already lawfully held, or that it developed independently. It lasts for the duration of the Agreement and five years after it ends, and for as long as the information remains confidential in the case of Store Credentials and trade secrets.

Neither party is liable for a failure caused by an event of force majeure within the meaning of Article 1218 of the French Civil Code. The affected party will inform the other promptly and take reasonable steps to limit the consequences. If the event lasts more than 30 days, either party may terminate these Terms by written notice.

We may update these Terms, for example to reflect new features, Google Play support, new Store rules or changes in the law. We will notify you of any material change by email or in the dashboard at least 30 days before it takes effect. If you do not accept the change, you may stop using Bloxks Pay before that date, without charge. If you keep using Bloxks Pay after that date, the new Terms apply.

Where a change is required at shorter notice by the law, an authority or a Store, or concerns only a new feature, it may take effect sooner, and we will tell you as soon as we can.

Significant changes to the Service that reduce its features in a way that materially affects you will be announced in the same way, except where an immediate change is needed for security or legal reasons.

• Notices: we send notices to the email address of your Bloxks account and through the dashboard. You send notices to contact@bloxks.app.
• Subcontracting and assignment: we may use subcontractors and subprocessors as described in the DPA, and remain responsible for them. We may transfer the Agreement to a company that takes over all or part of our business, provided that it does not reduce your rights; we will inform you. You may not transfer the Agreement without our written consent.
• Publicity: we will not use your name or logo as a reference without your prior consent.
• Independence: the parties are independent contractors. Nothing in these Terms creates a partnership, joint venture, employment or agency relationship, except for the service-provider role described in Sections 6 and 7.
• Severability: if a provision is found invalid, the rest of these Terms remains in force, and the invalid provision is replaced by a valid one as close as possible to its purpose.
• No waiver: failing to enforce a provision is not a waiver of the right to enforce it later.
• Entire agreement: the Agreement described in Section 1 contains everything the parties have agreed about Bloxks Pay and replaces any earlier version of these Terms.
• Language: these Terms are written in English, which is the language that governs them.

These Terms are governed by French law.

Before going to court, the parties will try to settle any dispute amicably. The party raising the dispute writes to the other, and the parties discuss it in good faith for 30 days. This step does not prevent either party from seeking urgent or interim measures.

If the dispute is not settled, it falls within the exclusive jurisdiction of the courts of Paris, subject to rules of public policy, as provided in the Bloxks Terms of Use for professionals. As Bloxks Pay is reserved for professional use, the consumer mediation available under the Bloxks Terms of Use does not apply.

For any question about these Terms, to revoke your Store Credentials, or to request an export or deletion of your data, write to contact@bloxks.app. For help with the Service, write to support@bloxks.app.

Bloxks SAS, 47 rue Vivienne, 75002 Paris, France. Paris RCS 130 543 515.