Consentia — Privacy Policy

Document version 1.5 · Last updated 22 October 2026 · Effective 22 October 2026

For the personal data we process on a merchant’s behalf, see the Data Processing Agreement.

1. Identity of the provider

This Privacy Policy describes how TRANSYLVANIA MARKETING LTD SRL (“we”, “us”, “our”, the “Provider”) handles personal data in connection with the application Consentia (the “App”).

Legal nameTRANSYLVANIA MARKETING LTD SRL
Tax ID (CUI)43230933
Registered addressStr. Crișanei 2, 550012 Sibiu, Romania
Email[email protected]
Websitehttps://transilvaniamarketing.ro

Email is our designated channel for all privacy matters, including data subject requests, processor instructions from merchants, and questions about this Policy. Written correspondence to the registered address is also accepted.

2. Purpose, scope and audience

Purpose. This Policy explains, in full, which categories of data the App processes, for which purposes, on which legal basis, for how long, with whom they are shared, and which rights the individuals concerned have.

What this Policy covers. Data generated by visitors of an online store on which a merchant has installed and activated the App (“Visitor Data”), and data relating to the merchant that installs and operates the App (“Merchant Data”).

What this Policy does not cover. The privacy practices of the merchant who installs the App, who publishes its own privacy policy and is responsible for it; the privacy practices of the Store Platform itself; the privacy practices of Google or of any other third-party tool a merchant has installed on its store independently of the App; and any cookie, tag, pixel or script placed on a merchant’s store by anyone other than the App. The tags that the App loads at the Merchant’s instruction are described in section 9; the provider’s own processing of the data they collect is not covered by this Policy.

Audience. Merchants evaluating or using the App, visitors of stores on which the App is active, and app marketplace reviewers.

Interpretation. Where this Policy states that something is not done, that statement is absolute and is not subject to unstated exceptions. Where a figure, period or region is given, it is the figure, period or region actually applied. Headings are for convenience only and do not limit the text beneath them.

3. Definitions

GDPR means Regulation (EU) 2016/679. Personal data, processing, controller, processor, sub-processor, data subject and personal data breach have the meanings given in Article 4 GDPR.

Merchant means the person operating an online store who installs the App on that store. Visitor means any person who visits a store on which the App is active and to whom the consent banner is displayed. Consent Record means a single row stored by the App describing one consent-related event, as itemised in section 6. Store Platform means the e-commerce platform on which the Merchant’s store and the App run. Tag means a script of a third-party tool, for example an advertising pixel or an analytics script, that runs in the Visitor’s browser. Scan Data means the technical information about the cookies and scripts of a store found by the store scan described in section 7. Browser Markers means the entries that the App’s code writes in the Visitor’s browser storage, listed in section 6.

4. What the App does

The App has the following functions:

  1. it displays a cookie consent banner on the store, in Romanian, English, German, French or Italian, according to the Merchant’s settings and, where the Merchant has enabled it, the language of the Visitor’s browser;
  2. it transmits the Visitor’s choice to Google Consent Mode v2 and to the Store Platform’s customer privacy interface;
  3. it maintains a register of consents, which the Merchant can export as a CSV file;
  4. it shows the Merchant aggregated statistics about that Merchant’s own store: banner impressions, response rate, acceptance rate and a breakdown by region, including a three-dimensional globe, in the Merchant’s admin interface, that displays the same aggregated figures;
  5. it holds back, until the Visitor has consented to the relevant category, the scripts of recognised third-party tracking tools and of the domains the Merchant has listed, and starts them after consent (script blocking);
  6. where the Merchant has enabled it, it deletes from the Visitor’s browser the cookies of the categories the Visitor has not allowed (cookie deletion);
  7. it reads the public pages of the Merchant’s store from our servers in order to identify and classify the cookies and scripts of the store (the store scan) and, where the Merchant has enabled it, it shows the resulting list in the preferences window of the banner;
  8. where the Merchant has entered the relevant identifier, it loads on the store the Merchant’s own Google tag, Meta Pixel or Microsoft Advertising (UET) tag and passes the Visitor’s choice to it (see section 9);
  9. it asks the Visitor for the choice again after the interval the Merchant has set: 6 months, 12 months or never.

The App performs no function beyond these. The App itself is not an analytics product, an advertising product, a marketing product or a customer relationship management product: it does not collect, receive or transmit to any analytics or advertising provider any data about Visitors. Functions 5, 6 and 9 and the choice of the banner language run in the Visitor’s browser and send us nothing other than the consent event described in section 6. Function 7 concerns the Merchant’s store, not its Visitors. Function 8 is explained in section 9.

5. Roles: controller and processor

Visitor Data — the Merchant is the controller, we are the processor. For all Visitor Data described in section 6, the Merchant determines the purposes and means of processing. We act solely as a processor under Article 28 GDPR and process Visitor Data only to provide the functions in section 4 that involve Visitor Data (functions 1 to 4) to that same Merchant, and only on that Merchant’s documented instructions, which include its configuration of the banner and its installation of the App.

In practice, we do not decide why Visitor Data is collected, we do not use it for our own purposes, we do not combine data from different Merchants’ stores into any cross-merchant product or dataset, and we disclose it to no one other than the Merchant whose store generated it and the sub-processors listed in section 16.

Functions that run in the browser or concern the store. The code that holds back scripts, deletes cookies, chooses the language and shows the banner again runs in the Visitor’s browser and does not send us Visitor Data. The tags in function 8 send data from the Visitor’s browser directly to the tag provider, not to us. For the data about the store described in section 7, including Scan Data, we are the controller.

Merchant Data — we are the controller. For the merchant account data described in section 7, we determine the purposes and means of processing, in order to provide, secure, maintain and support the App.

Nothing in this Policy makes us a joint controller with a Merchant, with the Store Platform or with Google. If a Merchant gives us an instruction we consider to infringe data protection law, we will inform the Merchant and may suspend execution of that instruction, under Article 28(3) GDPR.

6. Visitor data: exactly what is stored

For each consent-related event the App stores one row, containing the following and nothing else:

Data elementDescription and example
Consent identifierA pseudonymous, random identifier generated by the Store Platform. It is not created by us and is not derived from any identifying attribute of the Visitor.
ActionOne of: banner displayed, accepted everything, refused everything, chose by category.
Three yes-or-no valuesPreferences, statistics, marketing: allowed or not.
Region codeA country code (ISO 3166-1 alpha-2, for example “RO” or “DE”), followed, where known, by the subdivision code from ISO 3166-2 written without a hyphen (for example “ROMS” for RO-MS, Mureș County).
Page pathThe path of the page on which the banner was shown, for example /collections/all.
Banner text versionThe version of the wording that was displayed.
Date and timeThe moment of the event.
Store domainThe store on which the event occurred.

Purposes

  • To give effect to the Visitor’s choice, by transmitting it to Google Consent Mode v2 and to the Store Platform.
  • To enable the Merchant to evidence the consent obtained, through the register and its CSV export.
  • To produce the aggregated statistics shown to that same Merchant.
  • To let the Merchant see where and under which wording consent was collected, for example to detect a misconfigured page or outdated text.

Legal basis

As stated in section 5, the Merchant is the controller and therefore determines and documents the legal basis. We do not determine it. Typically a Merchant relies on Article 6(1)(c) GDPR, compliance with the legal obligation under Article 7(1) GDPR to be able to demonstrate that the data subject consented, and/or Article 6(1)(f) GDPR, its legitimate interest in operating a functioning consent mechanism and keeping proof of the choices made. Our own processing of Visitor Data has no independent legal basis, because we process it only as processor.

Pseudonymous nature of the records

A Consent Record contains no direct identifier of the Visitor. The consent identifier is a random value generated by the Store Platform. We hold no key, table or additional dataset that would let us link it to a named individual, an email address, an order or a customer account. We nevertheless treat Consent Records as personal data and apply this Policy to them in full.

The region code identifies a country or a country subdivision. It is not a precise location, not a postal address, not GPS coordinates and not an IP address.

The banner can be shown in several languages. The Consent Record stores the version number of the banner text but not the language in which it was shown.

Browser Markers

Besides the register, the App’s code writes the following entries in the Visitor’s browser. They stay on the Visitor’s device; the App does not send them to us.

EntryWhereContentPurposeDuration
consentia_catlocal storagethree yes-or-no flags: preferences, statistics, marketinglets the script-blocking code know the previous choice before the Store Platform answers, so that scripts are neither started nor held back wronglyuntil the Visitor clears the browser data; ignored after the re-display interval
consentia_chfirst-party store cookie and local storagethe Visitor's choice (three yes-or-no flags: preferences, statistics, marketing) and the time of the choicewritten only when the Visitor clicks Accept, Refuse or Save; prevents the banner from reappearing and the choice from being lost when the browser or app in which the store is opened (for example Safari or Facebook) prevents the choice from being saved to the Store Platform; on its basis, the choice is re-sent to the Store Platform with its original time, without a new entry in the registeruntil the re-display interval expires, at most 12 months from the choice
consentia_tslocal storagethe time of the Visitor’s last choice (a number)decides when to ask againuntil the Visitor clears the browser data
consentia_rlsession storagethe time of the last automatic page reload (a number)avoids reloading the page more than once every ten seconds when consent is withdrawnuntil the browser tab is closed

consentia_cat is written only where script blocking or tag loading is active. These entries are strictly necessary for the banner to apply the Visitor’s choice and are used for nothing else. The consent state itself is kept by the Store Platform in its own storage, governed by the Store Platform’s documentation. A Visitor can delete these entries at any time from the browser settings; the banner will then ask for the choice again.

Where cookie deletion is enabled, the App’s code reads the names, not the values, of the cookies that scripts in the page can access, and deletes those that the Merchant’s list or our built-in list assigns to a category the Visitor has not allowed. Cookies assigned to no category are not touched, and cookies marked HttpOnly cannot be reached. Nothing that is read is sent to us.

7. Merchant data: exactly what is stored

Data elementPurposeLegal basis
Store domainIdentifies the installation and attributes records, settings and statistics to the correct store.Article 6(1)(b) GDPR — performance of the contract
Access token issued by the Store PlatformLets the App communicate with the store and operate.Article 6(1)(b) GDPR — performance of the contract
Banner settings chosen by the MerchantStores the chosen configuration so the banner behaves as set. These are held as an application-owned metafield on the Store Platform, not in our own database.Article 6(1)(b) GDPR — performance of the contract
Refresh token issued by the Store Platform (kept together with the access token)Lets the App keep operating when the access token expires.Article 6(1)(b) GDPR — performance of the contract
Dashboard languageRemembers the language chosen for the App’s admin interface.Article 6(1)(b) GDPR — performance of the contract
Subscription data: plan identifier, billing period, the date until which the period is paid, the date of uninstallApplies the plan the Merchant has chosen and honours the period already paid if the App is reinstalled during it.Article 6(1)(b) GDPR — performance of the contract
Scan Data (see below) and the Merchant’s classification choicesLets the Merchant see, classify and publish the list of cookies and scripts of its store.Article 6(1)(b) GDPR — performance of the contract
Marker that the store used the App before the script-blocking functions were introducedKeeps the functions that change the store’s behaviour switched off for stores that already used the App, until the Merchant switches them on.Article 6(1)(b) GDPR — performance of the contract
Extended banner settings: texts, colours, languages, domain lists to hold back, and the identifiers of the Merchant’s own measurement tags (Google Analytics, Google Ads, Meta Pixel, Microsoft UET)Operate the banner and the tags as configured.Article 6(1)(b) GDPR — performance of the contract
Server access logs (see section 10)Security and troubleshooting.Article 6(1)(f) GDPR — legitimate interest

Where a Merchant is a sole trader, or where these items can otherwise be associated with an identifiable individual, we treat them as personal data and this Policy applies to them in full.

The access token and the refresh token are credentials. They are stored solely to operate the App, are never exported, are never shared with anyone outside the sub-processors in section 16, and are deleted on uninstall.

Store scan

The App reads the public pages of the Merchant’s store from our server: the home page, the page listing all products, one product page and the cart page. It does this about once a week where the scan is switched on, and when the Merchant presses “Scan now”. For stores that install the App now, the scan is switched on from installation; for stores that already used the App before it was introduced, it stays off until the Merchant switches it on. The request is an ordinary web request that identifies itself as “ConsentiaScanner/1.0”; it follows redirects only within the store’s own addresses, over HTTPS only, and stops at a password page. Because the request comes from our server, the Merchant’s own statistics may show it as a visit.

From the responses the App keeps: (a) for each cookie set in the response headers, its name, its domain attribute, its lifetime and whether it is marked HttpOnly, but never its value; names that look like personal identifiers (such as an email address, a UUID, a long hexadecimal string or a long number) are discarded; (b) the third-party tools whose scripts it recognises in the page code; and (c) for each recognised tool, the cookies that tool is known to set, marked “expected” because they were not observed directly. Visitors take no part in the scan, and the App does not read any Visitor’s cookies. The Scan Data is stored in our database and, once the Merchant has reviewed it and chosen to show it, written to the App’s metafield on the Store Platform so that the banner can show it to Visitors. The Scan Data contains no personal data of Visitors. The classification of cookies is automatic and indicative; it may be incomplete or wrong, and the Merchant remains responsible for the content of its cookie policy.

8. Permissions and the limits of our access

One permission only. The only permission the App requests from the Store Platform is read access to themes. It is used exclusively to tell the Merchant whether the banner is active in the published theme, and for nothing else.

No access to protected customer data. The App does not request and does not have access to protected customer data. Within the Store Platform’s classification, the App operates at Level 0 — no customer data.

The App does not read orders, customers, carts, checkouts, payment data, fulfilment data or any customer account. It cannot do so, because it does not hold the permissions required.

Scan and background tasks. The store scan uses no permission: it reads the public pages of the store the way any visitor can. The stored access token is used in daily background tasks that check the subscription state, write the plan state and the cookie list to the App’s metafields, and start the scan.

9. What the App does not collect or do

The consent register described in section 6 contains none of the following, under any circumstances and through any mechanism:

  • names;
  • email addresses;
  • telephone numbers;
  • IP addresses;
  • order data of any kind;
  • customer accounts or any data from them;
  • device identifiers;
  • browser fingerprinting data of any kind.

The App does not:

  • carry out profiling;
  • track a Visitor across websites;
  • set any advertising cookie of its own;
  • make automated decisions producing legal effects;
  • sell data;
  • send Visitor Data from our servers to advertising networks;
  • use data to train any model.

These statements are unconditional. They are not limited to a particular plan, tier, configuration or region, and no setting a Merchant may choose waives them. If any of them ceases to be accurate, this Policy will be amended under section 23 before the change takes effect. These statements concern the data that the App and our servers handle. The tags that the Merchant can ask the App to load, described below, work differently: their data travels between the Visitor’s browser and the tag provider and does not pass through our servers.

One honest qualification. The statement above concerns the data the App itself records. Like any service reached over the internet, the App is served by a hosting provider whose ordinary access logs do contain the requesting IP address. That is described separately and in full in section 10, so that nothing here can be read as a broader claim than we can keep.

Tags the App loads at the Merchant’s instruction

The Merchant can ask the App to load a third-party tag on the store: the Google tag (with the Merchant’s Google Analytics or Google Ads identifier), the Meta Pixel (with the Merchant’s pixel identifier) or the Microsoft Advertising UET tag (with the Merchant’s tag identifier). The App loads a tag only if the Merchant has entered its identifier or enabled the option. For the Meta Pixel and the UET tag the App sends only a page-view event; it sends no cart or order events. The App is only the tool that loads the tag for the Merchant.

A tag runs in the Visitor’s browser and sends data directly from the browser to the tag provider, for example the IP address, the address of the page, browser and device information and, where the Visitor has consented, identifiers set by the tag. That data does not pass through our servers; we do not receive, store or use it, and it is not part of the consent register. It is governed by the Merchant’s own agreements with the provider, and the Merchant is responsible for it as controller. We are not a party to those agreements. The Merchant should list these tags in its own privacy policy and cookie information.

When the tag is loaded depends on the tag and on the Merchant’s choice:

  • Meta Pixel and Microsoft Advertising UET, without the consent interface option: the tag is loaded only after the Visitor has consented to the Marketing category.
  • Meta Pixel and Microsoft Advertising UET, with the optional consent interface switched on by the Merchant: the tag is loaded before the Visitor chooses, with consent set to “refused”, and is switched to “granted” after consent to Marketing. In this mode the Visitor’s browser contacts the provider’s servers before the choice is made. What the provider does with consent set to “refused” is governed by the provider’s own documentation and agreements. The option is a separate setting that is off until the Merchant switches it on.
  • Google tag: the tag is loaded before the Visitor chooses, with all Consent Mode signals set to “denied”. In that state the tag may still send requests without cookies, which can include the IP address and the address of the page.
  • Other tools (for example TikTok, Pinterest, Snapchat, LinkedIn, X, Reddit, Microsoft Clarity, Hotjar): the App does not load them; if the store loads them, the App holds them back until the Visitor consents to their category.

Limits of script blocking

Script blocking is a technical aid and does not guarantee that no request reaches a provider before the Visitor’s choice. In particular: (i) a script written directly in the page code, or placed in the theme before the App’s block, can be requested by the browser before the App’s code runs, and the request, including the IP address, can then reach the provider; (ii) scripts the App does not recognise and the Merchant has not listed or marked are not held back; (iii) once a script has run, withdrawing consent cannot stop it, and the page is reloaded; (iv) scripts in embedded frames and calls made between servers, such as server-side conversion interfaces, are not affected; (v) cookies set by the server, and cookies marked HttpOnly, cannot be deleted by the App. The Merchant is responsible for checking, in a browser, which requests and cookies appear before consent.

10. Server and application logs

Two kinds of technical logs exist. (i) Application logs: for each request it handles, the App’s own code writes one log line with the HTTP method, the request path without its query string, the response status, the response size and the duration; it also writes operational and error messages, some of which contain the store domain. Application logs contain no IP addresses, names, email addresses or session parameters. (ii) Hosting infrastructure logs: our hosting provider keeps ordinary access logs for every request reaching the App, in the same way as any web server. Each entry contains the request time, the method and path, the response status and duration, the requesting IP address and the browser user-agent string.

These logs are generated by the hosting infrastructure, not by the App’s own code. They are used only to keep the App secure and available and to diagnose and fix faults. They are not linked to Consent Records, are not used to identify Visitors, are not used for analytics, statistics, advertising or profiling, and are not disclosed to anyone outside the sub-processors listed in section 16, one of which generates and holds them.

Retention: the period the hosting provider applies to our service plan, after which the logs are deleted by the hosting provider. We do not set that period and will state it on request. Location: the hosting provider is a company established in the United States, and its data processing addendum states that its primary processing operations take place there; we therefore cannot exclude that these logs are processed in the United States (see section 17). The legal basis is Article 6(1)(f) GDPR, our legitimate interest in the security and availability of the App.

When a Visitor makes a choice, and for the default state that applies before any choice, the App transmits the consent state only to Google Consent Mode v2: granted or denied, per category, across all seven signals, namely ad_storage, ad_user_data, ad_personalization, analytics_storage, functionality_storage, personalization_storage and security_storage.

We transmit to Google no identifier and no personal data: no consent identifier, no page path, no region code, no store domain, no name, no email address, no IP address — nothing beyond the granted or denied state per category.

What Google does afterwards, and any processing Google performs in connection with the Merchant’s own Google tags, products or accounts, is governed by the Merchant’s own agreements with Google. We are not a party to those agreements and have no control over that processing.

The App also transmits the Visitor’s choice to the Store Platform’s customer privacy interface, so that the platform and any other app or tag relying on it can honour that choice. This transmission consists of the consent state. The Store Platform’s own processing of that signal is governed by its own terms and privacy documentation.

13. Aggregated statistics

The App shows each Merchant statistics about that Merchant’s own store only: banner impressions, response rate, acceptance rate, and a breakdown by region. They are derived from the Consent Records of that store and are presented as counts and rates, not as records about identifiable individuals.

We do not build, publish or sell cross-merchant benchmarks, industry reports or any other aggregated product derived from Merchants’ data.

The App also shows the same aggregated figures on a three-dimensional globe in the Merchant’s admin interface. The globe is drawn in the Merchant’s browser by a library included in the App; no external map service is used. A point on the globe stands for the Visitors of a country or region: it is placed at a fixed reference point of the country (its geographic centre) or, for Romanian counties, of the county (the county seat), not at the location of any Visitor. The country table in the admin interface loads country flag images from flagcdn.com, which therefore receives the IP address and user-agent string of the Merchant’s browser; this is being replaced by images included in the App.

14. Retention periods

DataKept forThen
Consent Records12 months from the eventDeleted
Session (access token and refresh token)Until the App is uninstalledDeleted
Dashboard languageUntil the App is uninstalledDeleted
Subscription dataKept after uninstall, marked with the uninstall date, so that the period already paid can be honoured on reinstallDeleted on the shop data erasure notification
Scan DataUntil 12 months after the item was last seen; a new scan replaces the script entries and rebuilds the expected cookiesDeleted (automatic daily task); all deleted on the shop data erasure notification
Marker that the store used the App before the script-blocking functionsUntil the shop data erasure notificationDeleted
Application logs and hosting infrastructure logsThe period applied by the hosting provider (section 10)Deleted by the hosting provider
Browser MarkersOn the Visitor’s device until the Visitor clears them (section 6)—

On expiry. Deleted Consent Records are no longer available in the register, in CSV exports or in statistics. A Merchant who needs to keep evidence of consent for longer than 12 months must export the register before expiry; once records are deleted we cannot restore them.

On uninstall. The sessions of the store (including the access and refresh tokens) and the dashboard language are deleted immediately, and the App ceases to have any access to the store. Consent Records, Scan Data, the subscription data and the other store data are not deleted at that moment, so that the Merchant’s evidence of consent and paid period are not lost if the App is reinstalled shortly afterwards; they are kept until the Store Platform’s shop data erasure notification, which arrives approximately 48 hours after uninstall (section 15). The banner configuration, the cookie list and the subscription state are held as application-owned metafields on the Store Platform and are removed there when the installation ends.

Backups. Our hosting provider takes routine database backups for disaster recovery. Data deleted under this section may therefore persist in those backups for a short period until the backups themselves expire in the ordinary rotation. Such backups are not used for any other purpose and are not accessible to anyone outside the sub-processors listed in section 16.

15. Mandatory platform notifications

The App responds to the Store Platform’s mandatory compliance notifications: the customer data request notification, the customer data erasure notification, and the shop data erasure notification sent after uninstall.

On receiving the shop data erasure notification we delete, in a single database transaction, all data of that store held in our database: the sessions, all Consent Records, the dashboard language, the subscription data, the Scan Data and scan state, and the marker described in section 7.

Merchants should note the practical consequence of section 9: because the App holds in its register no name, email address, telephone number, IP address, order data, customer account or device identifier, a customer data request or customer erasure notification will generally find no identifying customer data in the App to return or to erase.

16. Sub-processors and location of the data

Sub-processorRoleLocation of processing
RailwayHosting and databaseEuropean Union region
The Store Platform providerThe platform on which the App runsAs governed by the Store Platform’s own terms and privacy documentation

The database in which Consent Records, Scan Data and sessions are stored is hosted in a European Union region. The hosting provider is a company established in the United States (see section 17).

The providers of the tags that the App loads or holds back at the Merchant’s instruction (for example Google, Meta, Microsoft) are not our sub-processors: no data passes from our servers to them.

Apart from these sub-processors, we disclose data to no one. There is no advertising network, no data broker, no analytics vendor, no email provider and no artificial-intelligence vendor in our processing chain for the App. We remain responsible to Merchants for the processing carried out by our sub-processors in providing the App.

17. International transfers

Our application server and database are located in a European Union region. Our hosting provider is a company established in the United States; its data processing addendum states that its primary processing operations take place in the United States and that transfers outside the European Economic Area rely on the EU-U.S. Data Privacy Framework, to the extent the recipient is certified under it, or otherwise on the standard contractual clauses adopted by the European Commission. To the extent the hosting provider’s logs, which contain IP addresses, are processed in the United States, this is a transfer to the United States on those mechanisms. Apart from this, we do not transfer Visitor Data or Merchant Data outside the European Economic Area for any purpose of our own.

Three points fall outside our control and require attention:

  • The Store Platform. The App runs on the Store Platform. Any processing or transfer carried out by the Store Platform as part of operating its platform is governed by the Store Platform’s own terms, privacy documentation and data processing addendum, to which the Merchant is a party.
  • Google. As stated in section 11, we transmit only the granted or denied consent state, with no identifier and no personal data. Any further processing or transfer by Google is governed by the Merchant’s own agreements with Google.
  • Tag providers. Where the Merchant has the App load the Google tag, the Meta Pixel or the Microsoft Advertising tag, the provider receives data directly from the Visitor’s browser. Any processing or transfer by the provider is governed by the Merchant’s own agreements with it.

If we ever intend to process data outside the European Economic Area, this Policy will be amended under section 23 before that change takes effect, and the transfer mechanism relied on will be stated.

18. Rights and how to exercise them

Subject to the conditions and exceptions in the GDPR, data subjects have the right of access (Article 15), to rectification (Article 16), to erasure (Article 17), to restriction of processing (Article 18), to data portability (Article 20), to object to processing based on legitimate interests (Article 21), to withdraw consent at any time where processing is based on consent (Article 7(3)), and to lodge a complaint with a supervisory authority (Article 77).

If you are a visitor of a store

Address your request to the Merchant operating that store, not to us. The Merchant is the controller of Visitor Data and its contact details are published in that store’s own privacy policy and legal pages. Where a Merchant forwards us such a request as its processor, we assist the Merchant in responding under Article 28(3)(e) GDPR. We do not respond directly to Visitors about a Merchant’s store data, because we are not entitled to do so.

A practical limit, stated plainly

Because the register holds no name, email address, telephone number, IP address, order data, customer account or device identifier, we have no means of identifying which Consent Record, if any, relates to a given individual. The consent identifier is a random pseudonym generated by the Store Platform and we hold no key linking it to a person. In relation to Consent Records we are therefore generally unable to identify the data subject within the meaning of Article 11 GDPR, and the rights of access, rectification, erasure, restriction and portability may be impossible to exercise against the record itself. A Visitor who can supply the exact consent identifier may ask the Merchant to have the corresponding record located. In any event, all Consent Records are deleted after 12 months.

Changing your choice as a visitor

A Visitor who wishes to change a previous choice can do so through the consent banner, or through the floating consent control that the App leaves on the page when the Merchant has enabled it. Changing the choice creates a new Consent Record reflecting the new state.

If you are a merchant

For the Merchant Data for which we are controller, send your request by email to [email protected]. We respond under Article 12(3) GDPR, without undue delay and in any event within one month of receipt, extendable by two further months where necessary, in which case we will tell you of the extension and the reasons for it within the first month.

Where we have reasonable doubts about the identity of the person making a request, we may ask for additional information needed to confirm it, under Article 12(6) GDPR, and will not use that information for any other purpose. We charge no fee, except where Article 12(5) GDPR permits it for manifestly unfounded or excessive requests.

19. Security measures

  • Encrypted communication. All traffic to and from the App uses HTTPS/TLS.
  • Restricted database access. Access is limited to the App and to the persons who need it in order to operate, secure, maintain and support it.
  • Store scan safeguards. The scan only sends ordinary read requests to the store’s own addresses, does not follow redirects to other sites or over plain HTTP, stops at a password page, limits each request to 8 seconds and each page to 2 MB, never stores cookie values, discards names that look like personal identifiers and keeps at most 80 cookie names per scan. A manual scan can be started at most once a minute per store.
  • No directly identifying data in the register. The consent register is designed to contain no name, email address, telephone number or IP address, which materially reduces the impact of any incident affecting it.

Data minimisation is itself the most important protective measure here: data that is not held cannot be compromised. The exclusions in section 9 are a design choice, not a configuration option.

No transmission over the internet and no storage system can be guaranteed to be absolutely secure. We do not claim absolute security; we claim the measures set out above.

20. Personal data breaches

Where we act as processor (Visitor Data), if we become aware of a personal data breach we will notify the affected Merchant without undue delay under Article 33(2) GDPR, with the information reasonably available to us, so that the Merchant can assess its own obligations towards its supervisory authority (Article 33(1) GDPR, within 72 hours where feasible) and towards affected data subjects (Article 34 GDPR).

Where we act as controller (Merchant Data), we will assess the breach and, where it is likely to result in a risk to the rights and freedoms of natural persons, notify the competent supervisory authority under Article 33(1) GDPR and, where the risk is high, the affected individuals under Article 34 GDPR.

Notifications are sent by email to the address associated with the Merchant’s installation and published on our website.

21. Children and minors

The App is a business tool, intended for merchants operating online stores, and is not directed at children.

The App does not knowingly process data of children and collects none of the elements by which a child could be identified. It has no means of determining a Visitor’s age, and performs no age verification, no age inference and no age-based targeting.

Where a Merchant’s store is directed at children, it is for the Merchant, as controller, to assess the applicable rules on the consent of minors, including Article 8 GDPR and the national age threshold in the relevant Member State.

22. No automated decision-making or profiling

The App carries out no profiling within the meaning of Article 4(4) GDPR, and no automated decision-making producing legal effects or similarly significantly affecting a data subject within the meaning of Article 22 GDPR.

The App does not score, segment, rank, categorise or predict anything about an individual. Recording the yes-or-no state of three consent categories is the execution of the Visitor’s own choice; it is not an inference about the Visitor. Placing a cookie or a script in a category is a classification of technical items of the store; it is not a classification of any person.

23. Changes to this Policy

We may amend this Policy, for example to reflect a change in the App’s functionality, in our sub-processors, in the location of the data, or in applicable law. Each version carries a version number and a last-updated date, shown at the top of this page.

Where an amendment materially affects the processing of personal data — in particular any change to the data categories in sections 6 or 7, to the exclusions in section 9, to the retention periods in section 14, to the sub-processors in section 16 or to the location of the data in section 17 — the amended Policy will be published before the change takes effect.

Continued use of the App after the effective date of an amended version constitutes acceptance of that version by the Merchant. A Merchant who does not accept an amendment may uninstall the App, in which case the deletion described in section 14 applies.

24. Contact

TRANSYLVANIA MARKETING LTD SRL

Str. Crișanei 2, 550012 Sibiu, Romania

Tax ID (CUI) 43230933

[email protected]

https://transilvaniamarketing.ro

Visitors of a store should first read section 18: their request must be addressed to the Merchant operating that store.

25. Competent supervisory authority

We are established in Romania. Our supervisory authority is:

Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal (ANSPDCP)

B-dul G-ral. Gheorghe Magheru 28-30, Sector 1, 010336 Bucharest, Romania

+40 318 059 211 · +40 318 059 212

[email protected] · www.dataprotection.ro

Under Article 77 GDPR a data subject may also lodge a complaint with the supervisory authority of the Member State of their habitual residence, place of work or place of the alleged infringement. Nothing in this Policy restricts the right to an effective judicial remedy under Articles 78 and 79 GDPR.


End of Policy · version 1.5