_Last updated: June 24, 2026._
1. Introduction and Governance Model
The Market Yield values the privacy of its users and is committed to processing personal data with responsibility, transparency, proportionality, and respect for applicable law. This Privacy Policy explains how personal data may be collected, used, stored, disclosed, protected, retained, and otherwise processed when users access https://themarketyield.com/, including editorial pages, institutional pages, comparison guides, finance-oriented resources, jobs-related content, contact forms, and route-based landing experiences connected to the portal.
The Market Yield is operated by ActiveView OÜ, which serves as the institutional owner, controller, and central governance entity of the portal.
ActiveView OÜ Registry Code: 16639782 VAT: EE102590366 Kotkapoja tn 2a-10, Tallinn 10615, Harju, Estonia
The Market Yield is designed as an independent editorial and comparison environment focused primarily on credit cards, practical financial orientation, and jobs-related guidance. The portal may publish explainers, comparison frameworks, practical selection guides, route-based discovery pages, editorial summaries, product-data (`pd`) flows, and related resources intended to help users better understand card features, representative APR logic, fees, approval conditions, rewards structures, repayment dynamics, and employment-related pathways that may influence everyday financial choices.
Because this portal operates in a higher-sensitivity finance-adjacent context, our privacy posture emphasizes stronger clarity around the portal’s role, the limits of our function, transparency regarding optional tracking or attribution tools, and the distinction between editorial guidance and the independent actions of third-party providers. Our privacy model therefore follows a global baseline + local layer approach: we apply one central governance framework across the portal while activating local rights, consent standards, or additional disclosures where the geography of the user, the type of processing, or the applicable legal framework requires a more specific approach.
This Policy is meant to explain not only what data may be processed, but also why that processing exists in a portal that discusses credit cards, practical finance, and jobs while remaining outside the regulated role of a bank, lender, issuer, broker, employer, or recruitment agency.
2. Scope of Services and Portal Architecture
This Privacy Policy applies to personal data collected or processed through the institutional and operational environment of The Market Yield, including the following categories of surfaces:
* Primary Domain and Institutional Environment: The public environment available through https://themarketyield.com/, including home, category, editorial, institutional, and legally relevant informational pages. * Credit-Card and Financial-Orientation Editorial Surfaces: Explainers, comparisons, practical guides, rankings, educational summaries, feature breakdowns, route-based informational resources, and finance-sensitive editorial modules related to credit cards and everyday financial choice. * Jobs and Career-Information Surfaces: Articles, guides, and supporting editorial modules relating to vacancies, application preparation, hiring processes, resume strategy, and work-related practical orientation. * Landing, Auxiliary, and Product-Data Infrastructure: Campaign-linked pages, route-specific entry paths, structured discovery environments, `pd` flows, and supporting layers used to organize information journeys across relevant categories. * Contact, Submission, and Communication Points: Contact forms, request fields, survey prompts, rights-request routes, and other official entry points through which users may voluntarily transmit information. * Analytics, Security, Advertising, and Consent Layers: Cookies, consent-management technologies, analytics tools, attribution systems, anti-abuse controls, ad-tech components, and infrastructure logs used to keep the portal functional, measurable, and compliant.
This Policy applies only to The Market Yield environment where it is published or referenced. It does not automatically apply to external banks, card issuers, lenders, brokers, employers, job platforms, ad destinations, marketplaces, or other third-party services accessed after a user leaves our portal.
If you continue to a third-party issuer, bank, employer, or application platform after leaving The Market Yield, the privacy rules of that destination will govern the independent processing carried out there. Users should therefore review the external provider’s own privacy notice and terms before submitting application information, financial details, identity documents, or other personal data.
3. Institutional Disclaimer and Role Boundaries
The Market Yield operates strictly as an independent informational, comparative, and editorial guidance platform. ActiveView OÜ is not a financial institution, bank, lender, credit broker, credit card issuer, payment-service provider, employer, recruitment agency, or official representative of third-party services referenced through the portal.
Any card comparison, fee summary, rewards explanation, approval-orientation material, finance-related educational content, jobs-related guidance, or market commentary published on The Market Yield is provided for informational, educational, and navigational purposes only. We do not issue cards, grant credit, evaluate formal creditworthiness, receive applications on behalf of issuers, negotiate financial contracts, guarantee approvals, guarantee fees, guarantee rewards outcomes, hire users, or control the policies or decisions of third-party banks, issuers, employers, or platforms.
Because the portal covers credit cards and other finance-sensitive themes, users should not mistake route-level analytics, attribution tools, or monetization systems for a regulated financial-service relationship. Those technologies may support the operation of a publishing environment, but they do not convert the portal into a bank, lender, issuer, debt manager, or formal financial intermediary.
Users must validate material facts directly with the relevant issuer, provider, employer, official hiring platform, regulator, or competent authority before making financial, contractual, or professional decisions.
4. Transparency Regarding AI-Assisted Processes
The Market Yield may use artificial-intelligence tools in limited and supportive editorial or operational workflows, such as draft structuring, classification support, formatting assistance, language polishing, summarization assistance, or internal workflow efficiency.
AI assistance does not replace human supervision. Final publication, comparison framing, legal review, editorial validation, finance-sensitive disclaimer review, and institutional quality control remain subject to human decision-making. We do not present unreviewed AI output as financial guidance, credit advice, final eligibility information, or official card or employment terms.
Where AI-assisted tools contribute to route organization, internal productivity, or message triage, they do so within a human-governed framework designed to preserve accountability, reviewability, and institutional control.
5. Categories of Personal Data Collected
The Market Yield may process different categories of personal data, technical data, and operational signals depending on the route, session, and interaction context involved.
A. Data You Provide Voluntarily
* Identification and Basic Submission Data: Information such as your name, display identifier, or comparable identifying elements when you choose to send a message, request, complaint, or form submission. * Email Address and Digital Contact Details: Contact coordinates provided so we can respond to a request, continue an ongoing communication, or send an update you expressly requested. * Telephone Number and Additional Contact Channels: Optional information you may provide where a specific communication flow allows you to expand the available response channel. * Message Content and Free-Text Submissions: The substantive content you write into contact forms, support requests, surveys, feedback fields, or comparable open-text environments. * Declared Preferences and Content Interests: Information voluntarily indicated regarding language, market interest, category preference, communication choice, or route-selection logic. * Attachments or Structured Submission Elements, Where Enabled: If a route specifically supports the transmission of files or structured materials, those items may contain personal data relevant to the request. * Any Other Information You Choose to Submit: Additional data intentionally disclosed by you inside forms, questionnaires, or interactive portal surfaces.
B. Technical and Navigation Data
* IP Address and Basic Network Signals: Technical information needed to deliver content, detect abuse, support infrastructure integrity, and infer approximate territorial context. * Browser Type, Version, and Rendering Configuration: Technical parameters used for compatibility, performance analysis, diagnostic review, and stable display of portal resources. * Device, Operating System, and Access-Environment Attributes: System-level signals that help us understand how the portal is accessed and improve usability across different surfaces. * Language, Locale, and Session Settings: Browser or device indicators that help align content and compliance layers with the likely linguistic and regional context of the session. * Visited Pages, Navigation Paths, and Reading-Depth Signals: Information about how users move across editorial, institutional, comparison, jobs, and route-based surfaces to evaluate content structure and route performance. * Interaction Timing, Click Events, and Usage Timestamps: Operational records that help us assess friction, engagement, and technical stability. * Referral Information and Entry-Point Attribution: Data indicating the source, campaign, search path, publisher route, or external environment from which the user arrived. * Approximate Geolocation Derived from Technical Signals: Non-precise territorial inference used for jurisdictional analysis, regional disclosure logic, and general contextual calibration.
C. Telemetry, Attribution, and Traffic Data
* Traffic and Volume Metrics: Aggregated visit and session indicators used to understand where demand concentrates and how the portal performs. * UTM Parameters and Campaign Tags: Source identifiers used to measure how users arrive from campaigns, publishers, content distribution, partners, or other external channels. * Advertising Attribution Signals Such as `gclid`: Technical markers used to assess campaign performance and route-level attribution where permitted by applicable law. * Engagement and Comparative-Route Signals: Data used to understand whether pages, tables, comparison modules, or informational journeys are clear, useful, and operationally stable. * Consent-State and Preference Markers: Technical records indicating whether a user accepted, declined, or customized optional privacy settings where a consent layer is active. * Ad-Delivery and Frequency-Control Signals: Where monetization is present, certain technical markers may be used to reduce repetitive ad delivery, understand limited campaign reach, and support lawful operational reporting.
D. Contextual Data from Card-Comparison and Jobs Journeys
* Route-Selection and Category-Preference Signals: Data showing how users narrow or organize exploration inside structured card-comparison or jobs-related journeys. * Comparison-Interaction and Feature-Focus Signals: Contextual records reflecting how users engage with explanations of fees, APR examples, approval criteria, reward mechanics, annual charges, issuer conditions, or similar practical modules. * Landing-Flow and Step-Transition Events: Signals showing how users move through structured informational paths, including route exits, comparison-step clicks, and reading-depth patterns. * Localization and Disclosure-Fit Signals: Contextual indicators used to align finance-sensitive content, disclaimer intensity, or transparency timing with the market-facing route involved. * Safety, Anti-Abuse, and Integrity Signals: Contextual technical markers used to distinguish legitimate usage from scraping, form abuse, spam, credential-harvesting attempts, or other misuse.
The Market Yield does not collect every category of data from every user in every session. Our collection logic is contextual and proportionate to the surface used, the preference state recorded, the legal environment involved, and the specific interaction performed by the user.
6. Methods of Collection and Data Sources
The data described in this Policy may be collected through legitimate and proportionate methods connected to the user’s interaction with The Market Yield, including:
* Ordinary Navigation of the Portal: Automatic collection of technical signals generated when users visit, read, compare, or interact with portal surfaces. * Forms, Contact Fields, and Message Channels: Information voluntarily sent by users through official portal communication routes. * Cookies, Pixels, Tags, Local Storage, and Comparable Technologies: Technical tools used for functionality, analytics, attribution, advertising controls, consent persistence, and security. * Server Logs and Infrastructure Records: Technical records generated by the operation of the website for diagnostics, continuity, abuse prevention, and security review. * Analytics and Measurement Tools: Services used to understand route quality, traffic patterns, engagement, and comparative or editorial performance. * Advertising and Attribution Integrations: Technologies used to understand campaign performance, measure source quality, or support lawful monetization. * Security and Anti-Fraud Systems: Tools used to detect malicious traffic, automated abuse, excessive requests, credential-harvesting patterns, or suspicious operational behavior. * Product-Data and Structured Discovery Workflows: Route-based layers that organize comparisons, affiliate-style paths where relevant, or editorial discovery journeys connected to card and jobs content. * Operational Vendors Acting on Our Behalf: In some cases, hosting, consent, communications, or delivery vendors may generate or relay data to us as part of the normal operation of the portal.
A user who only reads a public article about card fees or job applications does not necessarily create the same data footprint as a user who arrives through a campaign-tagged landing page, engages with optional cookies, or sends a message through the contact channel. This distinction matters because The Market Yield seeks to align collection intensity with actual purpose and legal necessity rather than treating all visits as functionally identical.
We also do not require users to disclose complete financial histories, bank-account information, debt details, or employment documents merely to consult public content. If a user voluntarily submits sensitive or detailed information in a message, we will process that information within the scope of the request and with appropriate caution, but users should avoid sending unnecessary high-risk data through ordinary support routes.
7. Legitimate Purposes for Processing
The Market Yield processes data only for legitimate, specified, and proportionate purposes connected to the operation of the portal. Those purposes may include:
* Operating, Maintaining, and Securing the Portal: Keeping pages available, stable, and technically functional across different devices and access environments. * Publishing, Structuring, and Improving Editorial and Comparative Content: Organizing card-comparison and jobs-related content, improving navigation, and making guides and routes more useful to users. * Supporting User-Initiated Communications: Receiving, authenticating, triaging, and responding to contact messages, rights requests, or comparable institutional communications. * Understanding Traffic Quality and Route Performance: Measuring how pages, comparison structures, and flows perform so we can reduce friction, improve clarity, and strengthen content quality. * Measuring Campaigns and Attribution Logic: Evaluating source quality, campaign effectiveness, and lawful performance of route-based discovery surfaces. * Preventing Fraud, Abuse, and Infrastructure Misuse: Detecting bots, scraping, credential abuse, malicious traffic, spam, or other activity incompatible with legitimate portal use. * Recording Valid Consent or Privacy Choices: Preserving evidence that a user accepted, declined, or customized non-essential processing choices where applicable. * Complying with Legal, Regulatory, and Institutional Obligations: Maintaining required records, responding to lawful authority requests, and defending legal rights when necessary. * Applying Finance-Sensitive Transparency Controls: Reviewing whether comparative routes, optional tracking layers, or monetization mechanisms remain consistent with a clear editorial role rather than a misleading provider-like posture. * Applying Data-Minimization and Segregation Practices: Reducing access, granularity, or retention where a portal purpose can be fulfilled with less data.
The Market Yield does not process personal data in order to approve credit cards, underwrite financial products, calculate official lending risk, open accounts, hire staff on behalf of employers, or make regulated financial decisions about users. Even in a finance-adjacent environment, our processing remains tied to publishing, route management, communication handling, analytics, security, compliance, and lawful monetization.
Where possible, we prefer aggregated reporting, pseudonymized analytics, route-level performance evaluation, and technical segmentation between editorial, compliance, and communications datasets. This helps preserve a proportionate privacy posture in a portal whose subject matter may influence meaningful financial decisions without making the portal itself the provider of the underlying financial product.
8. Consent Management, Cookies, and Comparable Technologies
The Market Yield may use cookies, pixels, tags, local storage, and equivalent technologies to keep the portal functional, preserve technical preferences, analyze traffic, support campaign attribution, and maintain lawful monetization or route measurement where applicable.
Because this portal covers finance-adjacent topics, we seek to be especially clear that optional tracking, attribution, or advertising technologies are not the same as a financial-service relationship and do not transform the portal into a bank, issuer, or lender. They are technical tools tied to publishing, analytics, and monetization.
These technologies generally fall into the following operational categories:
* Essential Technologies: Tools necessary for core navigation, security, bot mitigation, server integrity, consent-state persistence, or delivery of site resources. * Performance and Analytics Technologies: Tools used to understand visits, route depth, reading patterns, traffic quality, editorial performance, and general portal usability. * Advertising, Attribution, and Campaign Technologies: Tools used to preserve limited attribution logic, record campaign identifiers such as `gclid`, control repetition, and support monetization where the applicable legal framework allows it.
Where local law requires prior consent for non-essential technologies, we seek to respect that requirement through banner logic, a consent-management platform (`CMP`), or another preference mechanism appropriate to the session context. Users may therefore see different disclosure or consent experiences depending on territorial signals, applicable law, and the route they use.
8.1 Technical Record of Privacy Preferences
Where The Market Yield operates a consent-management or preference system, we may retain a minimized technical record to demonstrate the validity and persistence of the choice made. That record may include:
* Exact Timestamp of the Recorded Choice: The date and time associated with the privacy or cookie preference signal captured by the system. * Approximate IP or Geo-Validation Signal: A territorial indicator used to determine which consent or notice standard governed the session. * Browser or Device Technical Identifiers Needed for Audit Integrity: Limited technical markers reasonably necessary to associate the recorded choice with the relevant session or device context. * Version Reference of the Privacy Text Then in Force: A policy-version marker allowing us to evidence which disclosure layer applied at the time the user made the choice. * Choice-State Metadata: A limited internal record of whether optional categories were accepted, rejected, or customized so the system can enforce the selected preference set.
8.2 Third-Party Tools and Browser Controls
Some cookies or equivalent technologies may be activated by third-party providers supporting analytics, advertising, attribution, security, or consent handling. Where applicable, those providers operate under their own legal framework or under instructions aligned with our role and the relevant processing context.
Users may also manage certain cookies or comparable technologies through browser controls. Disabling some non-essential technologies may affect route persistence, analytics continuity, or some personalized or attribution-related experiences, but should not prevent access to the portal’s basic informational content.
Where The Market Yield relies on Google advertising or measurement services, users may review Google’s publisher-facing explanation of how information from sites or apps that use its services is handled at How Google uses information from sites or apps that use its services.
8.3 Route-Specific Technical Context
Not every route within The Market Yield operates with the same technical emphasis. A comparison page focused on credit cards may require different disclosure timing or attribution logic from a general jobs guide, an institutional page, or a contact route. Our objective is to keep technical activation proportionate to the function of the route, the user’s choice state, and the legal framework that applies, rather than treating all portal surfaces as identical.
9. Advertising, Analytics, and Third-Party Operational Tools
The Market Yield may use third-party tools to support analytics, advertising, consent management, hosting, delivery, abuse prevention, performance review, and message handling. Depending on the service and legal context involved, those providers may act as processors, service providers, or independent controllers for certain downstream activities.
Relevant third-party categories may include:
* Analytics and Measurement Providers: Services used to understand visit volume, engagement, route depth, and content performance. * Advertising and Attribution Partners: Ad-serving or campaign-measurement environments needed to support lawful monetization or evaluate traffic source quality. * Consent-Management Infrastructure: Tools used to store, interpret, and operationalize valid privacy and cookie choices. * Hosting, Delivery, and Security Vendors: Infrastructure providers supporting availability, speed, anti-bot defenses, and system protection. * Communication and Workflow Tools: Limited operational tools used to route messages, preserve basic continuity, or process institutional contact requests.
The appearance of an advertisement, product reference, affiliate path, or comparison entry on The Market Yield does not create an official representation relationship between the portal and the third-party bank, issuer, employer, or provider involved. Likewise, use of a vendor for analytics or monetization does not mean that the vendor may use all portal data for unrestricted purposes beyond the service context.
When selecting vendors, we seek configurations proportionate to the portal’s editorial role and finance-sensitive disclosure posture. This can include limiting the data passed to a provider, narrowing retention, reducing user-level identifiers, or preferring aggregated outputs where operationally feasible.
10. Territorial Scope, Legal Bases, and Local Regulatory Frameworks
ActiveView OÜ establishes its core data-governance framework in accordance with Regulation (EU) 2016/679 (GDPR) and the applicable Estonian data-protection framework because the institutional operator is established in Tallinn, Estonia. Depending on the processing context, the legal basis for processing may include consent, legitimate interests in operating and securing the portal, compliance with legal obligations, response to a user-initiated request, or protection against fraud and abuse.
Because The Market Yield currently has material traffic and operational relevance in Spain and the United Kingdom, those markets form the principal territorial calibration of this version of the portal’s privacy architecture. Given the portal’s finance-adjacent content, this territorial layer also places special weight on transparency around comparative claims, sponsored or affiliate pathways where present, and user understanding that card features, APRs, fees, and approvals remain controlled by the third-party issuer rather than by this portal.
This finance-sensitive posture also means that The Market Yield seeks to avoid confusing a data-enabled publishing environment with a regulated financial-service relationship. Traffic measurement, consent management, comparative-route analytics, or ad attribution may support the operation of the portal, but they do not mean that ActiveView OÜ is acting as a bank, lender, broker, issuer, or debt-service provider. The core principle remains that personal data is processed to operate an editorial and comparison environment, not to underwrite credit, open accounts, or approve card applications.
10.1 Spain and the Broader EEA Layer
Spain is materially relevant to the current operation of The Market Yield and sits within the broader European privacy environment. Processing connected to Spain is therefore assessed under the GDPR, the applicable Spanish implementation framework, and the broader EEA standards for lawful basis, transparency, data-subject rights, and consent for non-essential technologies where required.
Where a sufficient territorial nexus exists, users connected to Spain may have rights of access, rectification, erasure, restriction, portability, and objection, subject to the conditions and limits of applicable law. Because the portal deals with credit-card and financial-orientation topics, we also seek to maintain clearer disclosure language around editorial comparison, optional attribution technologies, and the difference between informational guidance and an actual financial-service offer.
Where the applicable legal framework requires prior consent for optional cookies, advertising technologies, or comparable measurement tools, the relevant route should operate on that basis. We also treat the distinction between essential technical functionality and optional campaign or analytics layers as a material compliance issue rather than a cosmetic notice choice.
10.2 United Kingdom
The United Kingdom is also a materially relevant market for the portal’s current operation. Processing connected to the United Kingdom is assessed in light of the UK GDPR and the Data Protection Act 2018, together with any applicable standards relating to transparency, fairness, and rights handling where a sufficient territorial nexus exists.
Where the law applies, users connected to the United Kingdom may have rights broadly comparable to those available under the GDPR framework, subject to the structure and limits of UK law. Because the portal covers credit-card comparisons and related finance-sensitive content, we may also apply reinforced disclosure logic around editorial independence, sponsored or affiliate transparency where relevant, and the fact that card approval, pricing, rewards, and contractual terms remain under the control of the third-party issuer.
Users connected to the United Kingdom may also encounter route-level consent or notice behavior aligned with the applicable regulatory expectations for non-essential technologies, marketing-adjacent attribution, and fairness of disclosures in finance-sensitive informational environments.
Other users outside Spain and the United Kingdom may still have rights under laws that become applicable through a recognized territorial connection. The country focus above reflects current traffic and disclosure relevance, not an exclusive list of all legal regimes that could ever apply.
11. How We Share Data
The Market Yield may share personal data or related technical information on a limited and proportionate basis with:
* Hosting, Infrastructure, Delivery, and Security Providers: Vendors needed to keep the portal available, performant, and protected. * Analytics and Measurement Providers: Services used to understand traffic quality, route performance, or basic engagement metrics. * Advertising, Attribution, or Monetization Partners: Providers involved in lawful campaign measurement or monetization where the relevant legal basis exists. * Consent-Management or Preference Infrastructure Providers: Vendors used to store, interpret, or operationalize privacy and cookie choices. * Professional Advisors or Auditors Subject to Confidentiality Duties: Limited disclosures needed to obtain legal, compliance, accounting, or audit support. * Competent Authorities Where Required by Law: Disclosures necessary to comply with a valid legal order, defend rights, or respond to lawful regulatory requests.
The Market Yield does not present itself as a commercial broker of indiscriminate contact databases, and it does not claim to sell personal contact lists as a routine business model. Where data is shared, the disclosure is tied to an operational, legal, security, compliance, or monetization function reasonably connected to the running of the portal.
If a user clicks through to a bank, card issuer, employer, or other destination service, that third party may independently collect information from the user under its own rules. That downstream processing is outside the scope of this Policy.
12. International Data Transfers
Because The Market Yield may rely on distributed infrastructure and service providers located in more than one country, personal data may be processed outside the country where the user is located. Where applicable law requires additional safeguards for cross-border processing, ActiveView OÜ may rely on recognized legal mechanisms such as contractual protections, access controls, internal restrictions, or other proportionate safeguards designed to protect personal data during international transfers.
The fact that data may move across borders reflects the operational reality of modern hosting, analytics, security, communications, and consent infrastructure. It does not mean that data is disclosed indiscriminately or without role-based controls. We seek to evaluate necessity, risk, vendor posture, and available safeguards before relying on a service that may involve international access.
13. Data Retention and Deletion
The Market Yield retains personal data only for as long as reasonably necessary to fulfill the purposes described in this Policy, including operating and securing the portal, responding to communications, measuring route performance and technical quality, preserving consent, audit, and compliance records, preventing fraud or abuse, and complying with legal obligations or defending rights.
Retention periods may vary depending on the category of data involved. By way of example:
* Technical Logs and Security Signals: May be retained for shorter or rotating periods appropriate to system protection, anomaly analysis, and abuse review. * Consent-State and Preference Records: May be retained for the period reasonably necessary to demonstrate compliance, preserve a valid choice state, and support audit integrity. * Contact and Rights-Request Communications: May be retained as long as reasonably needed to answer the request, document the handling outcome, and support follow-up or legal review if necessary. * Analytics and Route-Performance Data: May be retained in aggregated, pseudonymized, or time-bounded form to support editorial and operational review without preserving unnecessary personal detail. * Legally Relevant Records: May be retained longer where required by law, advisable for claims defense, or necessary to preserve evidence concerning compliance, complaint handling, or finance-sensitive disclosure review.
Where a longer retention period is justified, that decision is tied to a documented operational reason rather than to open-ended convenience. When data is no longer reasonably needed, we may delete it, aggregate it, de-identify it where appropriate, or place it beyond routine operational use.
14. Security and Digital Integrity Measures
The Market Yield adopts reasonable technical, organizational, and administrative measures designed to protect personal data against unauthorized access, loss, disclosure, alteration, or destruction. These measures may include:
* Access Controls and Credential Restrictions: Limiting data access to those persons or systems with a legitimate operational need. * Logging, Monitoring, and Abuse Detection: Reviewing suspicious events, scraping attempts, repeated requests, and anomalous patterns that may threaten portal integrity. * Vendor and Workflow Controls: Using service configurations, permissions, and internal procedures designed to reduce unnecessary exposure. * Transmission and Infrastructure Safeguards: Applying reasonable technical protections to data moving across internet-connected systems. * Incident Review and Containment Measures: Investigating technical anomalies, responding proportionately, and preserving evidence where necessary for legal, security, or compliance purposes.
No internet-connected system can promise absolute invulnerability. Even so, we seek to maintain a security posture proportionate to the portal’s finance-sensitive subject matter, ad-tech exposure, route-based structure, and institutional obligations.
15. Rights of Data Subjects and How to Exercise Them
Depending on the law that applies to a specific user or session, data subjects may have rights that include:
* Access: The ability to request confirmation about whether we process personal data and, where appropriate, to obtain access to that data. * Rectification: The ability to ask that inaccurate or incomplete personal data be corrected. * Erasure: The ability to request deletion where retention is no longer justified or where a valid legal basis for deletion exists. * Restriction: The ability to request that processing be limited in certain legally recognized situations. * Objection: The ability to object to certain forms of processing, including some processing based on legitimate interests or certain targeted-advertising contexts. * Portability: The ability, where recognized by law, to request certain data in a portable format. * Withdrawal of Consent: The ability to withdraw consent for future processing where consent is the relevant legal basis. * Complaint to a Competent Authority: The ability to seek regulatory review where local law provides that channel.
To exercise a right, users may contact us through the official Page de contact. Before acting on a request, we may require reasonable identity verification to protect the confidentiality and integrity of personal data.
Because The Market Yield discusses products and employers that are independently operated by third parties, some privacy requests may require us to distinguish between data controlled by our portal and data controlled only by a bank, card issuer, employer, or external platform. Where a request concerns information held only by such a third party, we may explain that limit and direct the user toward the more relevant destination.
16. Children’s Privacy and Age-Sensitive Use
The Market Yield is designed primarily for adult informational use because it covers credit cards, finance-sensitive comparison topics, and work-related decisions. The portal is not directed to young children, and we do not intentionally seek to collect personal data from children in violation of applicable law.
If a parent, guardian, or competent representative believes that a child has submitted personal data to the portal in circumstances where that should not have occurred, they may contact us through the official contact route so that we can review the situation and, where appropriate, delete or restrict the data.
17. External Links and Third-Party Environments
The Market Yield may contain links or references to third-party issuers, banks, employer pages, job boards, official forms, ad destinations, or external digital services. Once a user leaves our portal, the privacy, security, and operational rules of the destination environment are controlled by that third party.
We are not responsible for the independent privacy practices, terms, financial-product conditions, hiring procedures, security posture, or content accuracy of third-party environments.
18. Complaints and Supervisory Channels
If a user believes that The Market Yield has processed personal data in a way that violates applicable law, the user may contact us first through the official portal channel so we can review the concern.
Where applicable law grants that option, users may also lodge a complaint with the competent supervisory authority, including the Estonian Data Protection Inspectorate, the relevant Spanish authority, or the competent United Kingdom authority where jurisdiction exists because of the user’s location, the place of collection, or another legally relevant territorial connection.
When a complaint concerns credit-card comparisons, finance-sensitive disclosures, or consent for optional advertising technologies, we may also review whether the concern relates to the wording of a comparison route, the clarity of an affiliate or advertising signal, or the handling of optional measurement tools rather than to the operation of a financial product itself. That distinction helps preserve an accurate understanding of our editorial role.
19. Governance and Updates to This Policy
The Market Yield may update, revise, expand, or replace this Privacy Policy from time to time to reflect legal developments, portal changes, operational improvements, territorial adjustments, or compliance needs.
The version in force will be the version published on the portal with its visible revision date. Where law requires a stronger notification mechanism, a different consent renewal path, or a more explicit disclosure update, we will seek to apply that requirement to the relevant processing context.
20. Contact Information and Institutional Support
For privacy-related questions, rights requests, or other institutional communications about this Policy, users may use the official Page de contact. Users may also consult this politique de confidentialité, our Conditions d'utilisation, and the main site, all operated under the legal responsibility of ActiveView OÜ. Our contact channel exists for privacy, legal, editorial, and comparable portal-level matters; it does not create a bank-support, card-servicing, underwriting, lending, debt-handling, recruitment, or case-management obligation.
ActiveView OÜ Registry Code: 16639782 VAT: EE102590366 Kotkapoja tn 2a-10, Tallinn 10615, Harju, Estonia
