B2B focus
The main processing context is business correspondence, project assessment, proposal preparation and technical communication.
This document explains what data may be processed when visiting the APIACE website, submitting a form, using contact channels and discussing a B2B API integration.
Contact details and project information are used to respond to an enquiry and discuss an integration.
Technical logs and analytics may be used for security, performance and website improvement.
Access, storage and transfer of data are limited to website and business interaction needs.
Passwords, secret API keys, payment details or players' personal data should not be sent through the website or contact form.
APIACE uses the website to publish information about iGaming API integrations and communicate with companies that need gaming, payment, player, KYC, CRM, sportsbook and other technology solutions.
This policy applies to data about website visitors and company representatives who submit business enquiries. It does not describe processing of player data within customer platforms or external iGaming systems.
The main processing context is business correspondence, project assessment, proposal preparation and technical communication.
Only the amount of information necessary for website operation, security and responding to an enquiry is collected.
Visitors may request access to, correction of or deletion of information to the extent permitted by applicable law.
The specific data set depends on whether a visitor browses the website, uses a form or contacts APIACE directly.
Name, work email, company name, phone number, messaging account and preferred contact method.
Project type, target markets, providers, payment methods, technology stack, timelines, API requirements and attached materials.
IP address, browser, device, language, approximate region, pages viewed, referral source, time and interaction events.
Messages, attachments, comments, agreements and working notes needed to continue business communications.
Until a separate agreement is in place, do not send player databases, customer documents, full payment details, private keys, access tokens or other secret data through the website.
Data is processed only for clear business, technical and protective purposes related to the APIACE website and the visitor's enquiry.
To contact the sender, clarify the task, answer questions and agree on further communication.
To understand the scope of work, API components, providers, markets and dependencies, and prepare a technical or commercial path.
To analyze performance, navigation, multilingual pages, section demand and interface usability.
To detect malicious activity, protect forms, maintain technical logs and investigate incidents.
Depending on the situation, processing may be based on the user's request, preparation or performance of a contract, consent, legitimate interests or a legal obligation. The applicable basis is determined by the nature of the enquiry and legal requirements.
Reasonable technical and organizational measures are applied, but no method of storing or transmitting data can guarantee absolute security.
Depending on the country and applicable law, users may have the following rights in relation to personal information.
Obtain confirmation of processing and a copy of available information.
Correct or update incomplete or inaccurate information.
Request deletion of data where there is no basis for continued retention.
Temporarily restrict processing in cases provided for by law.
Object to processing based on legitimate interests or direct marketing.
Receive provided data in a structured format where this right applies.
Verification of a request may require confirmation of identity or a company representative's authority. Some rights are limited by retention obligations, protection of rights and applicable law.
Requests for access, correction, deletion or other questions about data processing can be submitted through the APIACE contact page.
The policy may be updated when the website, connected services, processing methods or legal requirements change. The current version is published on this page.
User rights, retention periods and data processing procedures may differ depending on the country and applicable legal requirements.