Privacy Policy
Last Updated: September 11, 2026
1. Introduction
This Privacy Policy explains how Coinsnap processes personal data in connection with its websites, Merchant software, applications, wallet software, APIs, plugins, integrations and related services.
Coinsnap is a brand operated by:
Onlineshop24 DOO
Ljubimira Ivkovica Suce 75
11453 Sopot (Ducina)
Serbia
Registration Number / Matični broj: 21579041
Tax ID / PIB: 111945856
D-U-N-S® Number: 679972520
Email: support@coinsnap.io
Website: https://coinsnap.io
Coinsnap provides software and technical infrastructure that enables Merchants to accept Bitcoin payments.
For standard self-custodial Bitcoin payments, Bitcoin is transferred directly from the Payer to a wallet selected by the Merchant. Coinsnap provides the technical software used to create, detect, assign, document and reconcile the payment.
Coinsnap does not receive, hold or take possession of the Bitcoin at any stage of the standard self-custodial payment flow.
This Privacy Policy should be read together with the Coinsnap Terms of Service, Cookie Policy, Non-Custodial & Risk Disclosure and, where applicable, the Coinsnap Data Processing Addendum.
2. Applicable Data Protection Law
Onlineshop24 DOO is established in the Republic of Serbia and is subject to applicable Serbian data protection law, including the Serbian Law on Personal Data Protection.
Depending on the circumstances, data protection laws of other jurisdictions may also apply to a particular processing activity.
Where the General Data Protection Regulation (EU) 2016/679 (“GDPR”) or another foreign data protection law applies to a particular processing activity due to its territorial scope, Coinsnap complies with the requirements applicable to that processing activity.
References in this Privacy Policy to GDPR concepts or requirements do not mean that the GDPR applies to all Coinsnap Services, Users, Merchants or processing activities worldwide.
3. Different Data Protection Roles
Coinsnap’s data protection role depends on the type and purpose of the processing.
3.1 Coinsnap as an Independent Controller
Coinsnap determines the purposes and means of processing information required for its own relationship with Merchants and Users.
This may include, for example:
- Merchant registration and account administration;
- contract administration;
- billing and tax administration;
- account and platform security;
- prevention and investigation of unauthorised access;
- customer support;
- service-related communications;
- operation and security of Coinsnap’s own websites and infrastructure;
- referral and partner programs;
- compliance with legal obligations; and
- establishment, exercise or defence of legal claims.
For these activities, Onlineshop24 DOO acts as the relevant Controller under Applicable Data Protection Law.
3.2 Coinsnap Processing Data on Behalf of a Merchant
A Merchant may choose to submit information relating to its customers or Payers to Coinsnap.
Where Coinsnap processes such information solely in order to provide functionality selected and instructed by the Merchant, Coinsnap may act as a Processor or equivalent service provider on behalf of the Merchant under Applicable Data Protection Law.
Examples may include processing information for:
- associating a payment with an order or invoice;
- displaying Merchant-provided information in the Merchant Dashboard;
- transaction reconciliation;
- payment reporting;
- accounting exports;
- APIs and webhooks;
- integrations with Merchant systems; or
- technical transmission to a Third-Party Provider selected by the Merchant.
In these circumstances, the Merchant determines why the Payer-related information is collected and submitted to Coinsnap.
The Merchant is responsible for ensuring that its collection and transmission of such information is lawful under the laws applicable to the Merchant and its customers.
Where Coinsnap acts as a Processor, the Coinsnap Data Processing Addendum applies as described in Section 13.
3.3 Independent Third-Party Providers
Certain optional services accessible through Coinsnap may be provided by independent Third-Party Providers.
These providers may independently determine the purposes and means of processing personal data required for their services and may therefore act as independent Controllers.
This may apply in particular to providers of services such as:
- Bitcoin-to-fiat conversion;
- brokerage or exchange services;
- bank settlement;
- banking services;
- KYC or KYB procedures;
- AML or sanctions compliance; or
- other independently provided financial services.
Such providers process information under their own terms, privacy policies and regulatory obligations.
4. Merchant Account Data
When a Merchant creates or uses a Coinsnap account, Coinsnap may process information such as:
- name;
- company or organisation name;
- business address;
- email address;
- telephone number, where provided;
- country;
- tax or VAT information;
- billing information;
- account settings;
- Store information;
- website URLs;
- wallet configuration information;
- settlement configuration;
- plugin or integration settings;
- API credentials or identifiers;
- referral information; and
- communications with Coinsnap.
Coinsnap processes this information in order to establish, administer and support its relationship with the Merchant and to provide the Coinsnap Services selected by the Merchant.
5. Merchant Registration and Country Determination
During Merchant registration, Coinsnap may temporarily process the IP address from which the registration is performed in order to estimate the Merchant’s probable country of establishment.
This information is used for administrative and tax purposes, including determining the appropriate VAT treatment of Coinsnap’s Services.
The IP address used for this country determination is not retained solely for that purpose.
The result of the country determination may be supplemented or corrected by information provided by the Merchant.
The Merchant remains responsible for providing accurate information concerning its place of establishment, tax status and other information relevant to the tax treatment of Coinsnap’s Services.
6. Merchant Access and Security Data
When a Merchant or authorised User accesses a Coinsnap account, Coinsnap may record technical access and security information such as:
- IP address;
- date and time of access;
- login activity;
- browser or application information;
- authentication events;
- account activity;
- security events; and
- technical information necessary to investigate suspicious or unauthorised access.
This information may be used to:
- protect Merchant accounts;
- document account access;
- identify suspicious login activity;
- detect unauthorised access;
- investigate security incidents;
- prevent abuse; and
- protect Coinsnap’s systems and Users.
Merchant access and security information is not used to associate the IP address of a Merchant account User with a Payer’s Bitcoin transaction.
7. Technical Payment Data
When Coinsnap provides Bitcoin payment functionality, Coinsnap processes technical information required to create, detect, assign, document and reconcile payments.
Depending on the payment method and configuration, this may include:
- invoice or order identifiers;
- Store or Point-of-Sale identifiers;
- payment amount;
- pricing currency;
- calculated Bitcoin amount;
- exchange-rate information used for the calculation;
- Bitcoin addresses;
- Lightning payment information;
- Lightning payment hashes;
- Bitcoin transaction identifiers;
- timestamps;
- confirmation information;
- payment status;
- technical payment metadata; and
- information necessary to associate the payment with the relevant Merchant invoice or order.
Some technical Bitcoin information may constitute personal data where it can reasonably be associated with an identified or identifiable natural person.
Coinsnap processes technical payment information in order to provide the payment-related software functionality selected by the Merchant.
8. No Payer Identification Required for Standard Bitcoin Payments
Coinsnap does not require a Payer to create a Coinsnap account or identify themselves merely in order to make a standard self-custodial Bitcoin payment to a Merchant.
For standard payment detection, Coinsnap does not require information such as the Payer’s:
- name;
- postal address;
- email address; or
- identity document.
Coinsnap does not store the Payer’s IP address as part of the standard Bitcoin or Lightning payment transaction record.
The fact that Coinsnap does not require Payer identification does not prevent a Merchant from collecting information from its own customers where required for the Merchant’s business or under laws applicable to the Merchant.
9. Merchant-Provided Payer Data
A Merchant may choose to associate additional information with a payment and submit that information to Coinsnap.
Depending on the functionality selected by the Merchant, this may include:
- Payer or customer name;
- email address;
- customer reference;
- order number;
- invoice number;
- accounting reference;
- delivery or transaction reference; or
- other information defined and supplied by the Merchant.
Coinsnap does not independently decide that such information must be collected for a standard self-custodial Bitcoin payment.
Where a Merchant submits Payer-related information to Coinsnap, Coinsnap processes the information for the functionality requested by the Merchant.
Such purposes may include:
- payment attribution;
- order reconciliation;
- transaction history;
- Merchant reporting;
- accounting exports;
- APIs and webhooks;
- connection to external Merchant systems; or
- technical transmission to a Third-Party Provider selected by the Merchant.
Merchants should not transmit personal information to Coinsnap unless it is necessary for a functionality they have chosen to use.
10. Merchant Responsibility for Customer and Payer Information
The Merchant controls its own relationship with its customers and Payers.
The Merchant is responsible for determining:
- which customer or Payer information it collects;
- the legal basis for collecting that information;
- what information is associated with a Bitcoin payment;
- whether information is submitted to Coinsnap;
- whether information is transmitted to another system or provider;
- how its customers are informed about such processing; and
- whether consent, notice or another legal requirement applies.
Depending on the Merchant’s jurisdiction and customer relationship, this may require appropriate provisions in the Merchant’s privacy policy, terms and conditions, checkout information or other customer disclosures.
Coinsnap does not determine the Merchant’s legal basis for processing information about its own customers.
11. Optional Third-Party Financial and Settlement Services
A Merchant may choose to use an independent Third-Party Provider for services such as Bitcoin-to-fiat conversion, brokerage, exchange or settlement to a bank account.
Coinsnap does not itself provide these financial services.
A Third-Party Provider may require information about the Merchant or Payer in order to provide its service or comply with legal and regulatory requirements applicable to that provider.
For example, an independent provider may require Payer identification information for its own:
- KYC procedures;
- KYB procedures;
- AML compliance;
- sanctions compliance;
- transaction monitoring;
- banking requirements;
- customer due diligence; or
- other regulatory obligations.
The Third-Party Provider determines which information it requires.
Where supported by the integration and instructed by the Merchant, Coinsnap may technically receive information supplied by the Merchant and transmit that information to the selected Third-Party Provider.
Coinsnap does not independently determine the Third-Party Provider’s regulatory information requirements.
The Third-Party Provider processes information required for its own service under its own terms, privacy policy and regulatory framework.
12. Independent Third-Party Providers and Subprocessors
A Third-Party Provider is not automatically a Subprocessor of Coinsnap merely because its service is accessible through a Coinsnap integration.
Where a provider independently determines the purposes and means of processing, including processing for its own regulatory, banking, settlement, KYC, KYB or AML purposes, that provider acts under its own responsibility.
Separately, Coinsnap may use Subprocessors or technical service providers to operate, secure or support Coinsnap Services.
Where such a provider processes personal data on behalf of Coinsnap and Coinsnap itself acts as Processor for a Merchant, the applicable Subprocessor provisions are governed by the Coinsnap Data Processing Addendum.
Coinsnap maintains information concerning relevant Subprocessors internally and provides information to affected Merchants where required under Applicable Data Protection Law or the applicable contractual framework.
13. Data Processing Addendum
The Coinsnap Data Processing Addendum (“DPA”) forms part of the Coinsnap Terms of Service.
The DPA applies automatically to the extent that Coinsnap processes personal data on behalf of a Merchant.
No separate signature or individually negotiated data processing agreement is generally required for the standard Coinsnap Merchant Service unless mandatory Applicable Data Protection Law requires otherwise.
The DPA includes provisions concerning:
- processing instructions;
- confidentiality;
- technical and organisational security measures;
- Subprocessors;
- assistance with individual rights;
- Personal Data breaches;
- retention and deletion;
- international processing; and
- applicable international transfer mechanisms.
The DPA does not apply to processing for which Coinsnap independently determines the purposes and means and acts as an independent Controller.
14. Coinsnap Wallet
Coinsnap may provide self-custodial Bitcoin wallet software.
The Coinsnap Wallet is designed so that Users control their own wallet and the credentials required to authorise transactions.
As part of the standard self-custodial wallet model, Coinsnap does not operate the wallet as a custodial account on behalf of the User.
Users are responsible for protecting their:
- wallet;
- private keys;
- recovery information;
- devices;
- authentication credentials; and
- backups.
Where Coinsnap offers optional backup, recovery or third-party storage functionality, information concerning that functionality should be reviewed together with the relevant product documentation.
15. Mobile Application Data
When a User uses a Coinsnap mobile application, limited technical information may be processed in order to operate, maintain and secure the application.
Depending on the platform and functionality, this may include:
- application version;
- operating system information;
- application diagnostics;
- crash information;
- push notification tokens;
- technical performance information; and
- security-related application events.
Depending on device settings and permissions, the application may request access to specific device functions such as:
- the camera for scanning QR codes;
- notifications; or
- secure local device storage.
Coinsnap does not intentionally access unrelated personal content stored on a User’s device.
16. Bitcoin Blockchain and Lightning Network Information
Bitcoin transactions operate on decentralised or distributed network infrastructure.
Information relating to Bitcoin on-chain transactions may be publicly available and may include:
- Bitcoin addresses;
- transaction identifiers;
- transaction amounts;
- timestamps; and
- confirmation information.
Public blockchain records are not controlled by Coinsnap.
Coinsnap cannot alter or delete information that has been validly recorded on the Bitcoin blockchain.
Lightning Network information is handled differently from public on-chain transaction information, but certain technical information may nevertheless be processed by infrastructure necessary for Lightning functionality.
Users should understand that Bitcoin transaction information may potentially be analysed or associated with other information by third parties independently of Coinsnap.
17. Purposes of Processing
Depending on the relevant data category and Coinsnap’s role, information may be processed in order to:
- provide Coinsnap software and functionality;
- create Bitcoin and Lightning payment requests;
- detect payments to Merchant-selected wallets;
- associate payments with orders or invoices;
- provide payment status information;
- provide transaction histories;
- provide reporting and accounting functionality;
- operate APIs, plugins and integrations;
- administer Merchant accounts;
- authenticate Users;
- protect Merchant accounts;
- prevent and investigate unauthorised access;
- provide customer support;
- administer fees, billing and taxes;
- determine the appropriate tax treatment of Coinsnap’s Services;
- operate referral and partner programs;
- maintain and improve system reliability;
- protect Coinsnap’s infrastructure;
- send service-related communications;
- comply with applicable legal obligations; and
- establish, exercise or defend legal claims.
Coinsnap does not use Merchant-Provided Payer Data for unrelated consumer advertising or Payer profiling.
18. Legal Grounds for Processing
The legal ground applicable to a processing activity depends on the relevant jurisdiction, the nature of the data and Coinsnap’s role.
Where Applicable Data Protection Law uses legal grounds comparable to those under Serbian data protection law or the GDPR, Coinsnap may process personal data on grounds including the following.
Performance of a Contract
Processing may be necessary to:
- create and administer a Merchant account;
- provide requested Coinsnap Services;
- support Merchant integrations;
- manage billing; or
- fulfil Coinsnap’s contractual obligations.
Legitimate Interests
Processing may be necessary for legitimate interests such as:
- protecting Merchant accounts;
- maintaining system security;
- preventing fraud and abuse;
- investigating unauthorised access;
- providing customer support;
- maintaining service reliability; and
- establishing, exercising or defending legal claims.
Where required by Applicable Data Protection Law, such interests are balanced against the rights and interests of affected individuals.
Compliance With Legal Obligations
Coinsnap may process information where necessary to comply with applicable:
- tax obligations;
- accounting obligations;
- legal record-keeping requirements;
- binding orders; or
- other legal obligations.
Consent
Where consent is required under Applicable Data Protection Law, processing may be based on consent.
This may apply, for example, to certain optional marketing communications or non-essential website technologies.
Where Coinsnap processes Merchant-Provided Payer Data solely on behalf of a Merchant, the Merchant is responsible for determining the legal basis applicable to its own processing of that information.
19. Cookies and Similar Technologies
Coinsnap may use cookies and similar technologies on its websites and web-based applications.
These technologies may be used for purposes such as:
- essential website functionality;
- Merchant login sessions;
- authentication;
- security;
- preferences;
- consent management; and
- analytics where applicable.
Where Applicable Data Protection Law requires consent before a non-essential cookie or similar technology is used, Coinsnap will apply the relevant consent requirements.
Further details are provided in the Coinsnap Cookie Policy.
The Cookie Policy may be updated as Coinsnap’s technical cookie and consent-management configuration develops.
20. Website Analytics
Coinsnap may use analytics technologies to understand how its websites are used and to improve website functionality, content and performance.
Depending on the technology used, analytics may process information such as:
- browser information;
- device information;
- pages visited;
- interaction information;
- approximate geographic information derived from technical data; and
- session information.
Where Applicable Data Protection Law requires consent for non-essential analytics technologies, such technologies will be subject to the relevant consent requirements.
Website analytics are separate from Coinsnap’s technical Bitcoin payment records.
Coinsnap does not use website analytics to add the Payer’s IP address to the standard Bitcoin or Lightning payment transaction record.
21. Technical Service Providers
Coinsnap may use external providers to support the technical operation, security and availability of its software.
Depending on the functionality used, these may include providers of:
- hosting or cloud infrastructure;
- email and communications;
- application distribution;
- security;
- monitoring;
- analytics;
- blockchain-related technical infrastructure;
- Lightning-related technical infrastructure; and
- other technology necessary for specific Coinsnap functionality.
The use of a particular provider depends on the Coinsnap product, configuration and technical architecture in use at the relevant time.
Not every technology provider is necessarily a Processor or Subprocessor for personal data.
Coinsnap does not publicly disclose confidential technical infrastructure, security architecture or commercial service-provider information except where disclosure is required by Applicable Data Protection Law or reasonably necessary in relation to a specific data processing relationship.
Where a service provider processes personal data on behalf of Coinsnap, Coinsnap applies appropriate contractual and organisational safeguards where required by Applicable Data Protection Law.
22. Disclosure of Personal Data
Coinsnap may disclose personal data where reasonably necessary to:
- provide the Coinsnap Service;
- use a service provider acting on Coinsnap’s behalf;
- provide an integration selected by the Merchant;
- transmit information to a Third-Party Provider selected by the Merchant;
- protect Coinsnap, its Users or its systems;
- investigate suspected fraud or security incidents;
- comply with applicable law;
- respond to a binding order from a competent authority; or
- establish, exercise or defend legal claims.
Coinsnap does not sell Merchant or Payer personal data to advertisers or data brokers.
23. International Processing and Data Transfers
Coinsnap is operated by Onlineshop24 DOO in Serbia.
Accordingly, personal data submitted to Coinsnap may be processed in Serbia.
Depending on the functionality used and the location of relevant technical providers or Third-Party Providers, information may also be processed in other jurisdictions.
Where Coinsnap itself transfers personal data internationally, Coinsnap applies the safeguards required by Applicable Data Protection Law for the relevant transfer.
Where a Merchant transfers personal data to Coinsnap from another jurisdiction, the Merchant remains responsible for determining which international transfer requirements apply to that Merchant.
Where Applicable Data Protection Law requires a particular Processor agreement, contractual safeguard or international transfer mechanism, Coinsnap will apply or make available the legally appropriate contractual mechanism according to:
- the jurisdictions involved;
- the respective roles of the parties;
- the nature of the processing; and
- the law applicable to the transfer.
Such safeguards may include applicable standard contractual clauses where legally appropriate.
No particular international transfer mechanism, including EU Standard Contractual Clauses, applies automatically to every Merchant, User, country or processing activity.
Additional provisions concerning international transfers are contained in the Coinsnap Data Processing Addendum.
24. EEA Transfers and Standard Contractual Clauses
Where a Merchant subject to the GDPR transfers personal data to Coinsnap in Serbia and the transfer is subject to Chapter V GDPR, an appropriate international transfer mechanism may be required.
Where applicable EU Standard Contractual Clauses are legally appropriate for such a transfer, Coinsnap may make the relevant standardised contractual transfer terms available to the affected Merchant.
The appropriate mechanism depends on the actual processing relationship and circumstances.
Acceptance of the Coinsnap Terms of Service or Data Processing Addendum does not by itself mean that EU Standard Contractual Clauses automatically apply to every Merchant or every transfer.
Where additional transfer terms are required, they may be implemented through a standardised electronic process without individual commercial negotiation where legally permissible.
25. Data Minimisation
Coinsnap seeks to limit personal data processing to information reasonably necessary for the relevant functionality.
A standard self-custodial Bitcoin Payment does not require Coinsnap to identify the Payer.
Merchants are encouraged not to submit customer or Payer personal data unless it is necessary for the Merchant’s selected functionality.
Where an order or invoice can be associated with a payment through a non-personal reference number, Merchants are encouraged to use such references rather than unnecessary personal information.
26. Data Retention
Coinsnap retains personal data only for as long as reasonably necessary for the purpose for which it is processed or for a longer period where required or permitted by Applicable Data Protection Law.
Retention depends on the category of information and may take into account:
- the duration of the Merchant relationship;
- the need to provide requested functionality;
- account and system security requirements;
- the need to investigate security incidents;
- applicable accounting and tax obligations;
- legal limitation periods;
- dispute resolution;
- requirements relating to a selected Third-Party Provider; and
- Merchant instructions where Coinsnap processes information on the Merchant’s behalf.
Merchant security and access logs are retained only for a period reasonably necessary for security, audit and investigation purposes.
Information used temporarily during registration to estimate the Merchant’s country is not retained solely for that purpose after the relevant country determination has been completed.
Merchant-Provided Payer Data is retained according to the relevant Coinsnap functionality, Merchant instructions and Applicable Data Protection Law.
Where retention is no longer necessary, information is deleted, anonymised or otherwise removed from active processing where technically and legally appropriate.
Information permanently recorded on a public blockchain cannot be deleted by Coinsnap.
27. Account Closure
When a Merchant closes a Coinsnap account, Coinsnap may delete or deactivate account information that is no longer required.
Certain information may need to be retained after account closure where required or permitted for:
- accounting or tax purposes;
- fraud prevention;
- security investigations;
- legal obligations;
- contractual claims; or
- establishment, exercise or defence of legal rights.
Closing a Coinsnap account does not delete transactions recorded on the Bitcoin blockchain.
Closing a Coinsnap account also does not affect Bitcoin held in a Merchant-controlled self-custodial wallet.
28. Security
Coinsnap implements technical and organisational measures intended to protect personal data and Coinsnap systems against:
- unauthorised access;
- accidental loss;
- misuse;
- alteration;
- unauthorised disclosure; and
- destruction.
Depending on the relevant system, measures may include:
- encrypted communications;
- access controls;
- authentication controls;
- restricted administrative permissions;
- security monitoring;
- logging;
- infrastructure protection; and
- backup and recovery measures where appropriate.
The general categories of measures applicable where Coinsnap acts as a Processor are also described in the Coinsnap Data Processing Addendum.
No internet-connected service can guarantee absolute security.
Merchants and Users remain responsible for protecting their own:
- account credentials;
- devices;
- wallets;
- private keys;
- recovery information; and
- API credentials.
29. Security Incidents and Personal Data Breaches
If Coinsnap becomes aware of a Personal Data breach or other relevant security incident, Coinsnap will investigate the incident and take appropriate measures.
Where Applicable Data Protection Law requires notification to an affected individual, Merchant or supervisory authority, Coinsnap will make or support the required notification according to its role in the relevant processing activity.
Where Coinsnap processes affected information on behalf of a Merchant, Coinsnap will notify and reasonably assist the Merchant where required under the applicable Data Processing Addendum or Applicable Data Protection Law.
30. Individual Rights
Depending on the law applicable to a particular processing activity, individuals may have rights concerning their personal data.
These may include rights to:
- request access;
- request correction;
- request deletion;
- request restriction of processing;
- object to certain processing;
- withdraw consent where processing is based on consent;
- request data portability where applicable; and
- lodge a complaint with a competent supervisory authority.
Requests concerning information for which Coinsnap acts as an independent Controller may be submitted to:
Coinsnap may need to verify the identity of the person making a request where reasonably necessary.
Rights are subject to the conditions, limitations and exemptions contained in Applicable Data Protection Law.
31. Requests Concerning Merchant-Provided Payer Data
Where Coinsnap processes Payer information solely on behalf of a Merchant, the Merchant remains primarily responsible for handling requests from its customers concerning that information.
A Payer should therefore generally contact the Merchant with whom the Payer conducted the underlying commercial transaction.
Where Coinsnap receives a request relating to Personal Data processed solely on behalf of a Merchant, Coinsnap may refer the request to the relevant Merchant and provide reasonable assistance where required by Applicable Data Protection Law or the Data Processing Addendum.
32. Complaints and Supervisory Authorities
Onlineshop24 DOO is established in Serbia.
Individuals may have the right to lodge a complaint with the competent Serbian authority responsible for personal data protection.
Where the GDPR or another foreign data protection law applies to a particular processing activity, an individual may also have rights in relation to the supervisory authority competent under that law.
Nothing in this Privacy Policy limits rights that cannot lawfully be excluded.
33. Service and Marketing Communications
Coinsnap may send service-related communications required to operate a Merchant account or provide requested functionality.
These may include:
- account information;
- security notifications;
- technical notices;
- service changes;
- billing information; and
- other contractual communications.
Marketing communications are sent only where permitted under Applicable Data Protection Law.
Where consent is required, marketing communications will be based on consent.
Recipients may unsubscribe from optional marketing communications using the unsubscribe mechanism provided or by contacting Coinsnap.
Unsubscribing from marketing communications does not prevent Coinsnap from sending necessary service, account, security or contractual communications.
34. Referral and Partner Programs
Coinsnap may operate referral, affiliate or partner programs.
Where a Merchant registers using a referral identifier, Coinsnap may record the relationship between the referring party and the new Merchant for purposes such as:
- referral attribution;
- program administration; and
- commission calculation.
Coinsnap does not provide the referring party with unnecessary personal details concerning the referred Merchant.
Only information reasonably necessary to administer the referral or partner relationship is disclosed where applicable.
35. Self-Hosted Software and Merchant-Controlled Systems
Certain Coinsnap plugins, software components or integrations may operate partly within systems controlled by the Merchant.
Where data is processed exclusively within Merchant-controlled infrastructure and is not transmitted to Coinsnap, Coinsnap does not control that processing merely because the Merchant uses Coinsnap software.
The Merchant remains responsible for its own systems and for personal data processed exclusively within those systems.
Relevant technical documentation may provide additional information concerning which information is transmitted to Coinsnap for a particular integration.
36. Third-Party Websites and Services
Coinsnap websites and software may contain links or integrations relating to independent websites and services.
Coinsnap does not control the privacy practices of independent third parties.
Users should review the privacy information provided by the relevant Third-Party Provider before using its services.
37. Children’s Privacy
Coinsnap’s Merchant Services are intended for businesses and adult Users and are not directed at children.
Coinsnap does not require age information or identification of a Payer merely in order to detect a standard self-custodial Bitcoin Payment.
Merchants remain responsible for determining whether their goods, services and processing of customer information may lawfully involve minors under laws applicable to the Merchant.
38. Changes to This Privacy Policy
Coinsnap may update this Privacy Policy where necessary to reflect:
- changes to Coinsnap products;
- changes to technical infrastructure;
- new or modified integrations;
- changes to data processing activities;
- changes in Applicable Data Protection Law; or
- improvements to Coinsnap’s privacy practices.
The current version will be published on the Coinsnap website together with the date of the latest revision.
Where required by Applicable Data Protection Law or where a change materially affects affected individuals, Coinsnap may provide additional notice.
39. Contact
For privacy-related questions or requests, contact:
Coinsnap / Onlineshop24 DOO
Ljubimira Ivkovica Suce 75
11453 Sopot (Ducina)
Serbia
Email: support@coinsnap.io
Website: https://coinsnap.io
