LOUDave Media & FrameFlow Privacy Policy

Revision date: 26 October 2026

Scope and how to read this policy

This Privacy Policy explains how LOUDave Media handles personal data in connection with:

• The LOUDave website: loudave.com, contact forms, enquiries, requested materials and newsletters.

• Advertising and lead forms: LOUDave campaigns and forms, including Meta Facebook and Instagram lead forms.

• FrameFlow: the closed customer service at frameflow.loudave.com, accessed using access details issued to authorized customers, associated workspaces, product information and customer-requested processing. It is not offered for public self-service registration and is not intended for search-engine indexing.

• Frameflow Gallery Collector: the Chrome extension of that exact name and its product-gallery pairing, collection, export and transfer workflow.

The general website marketing provisions do not authorize marketing use of information obtained through the extension. The extension-specific restrictions below take precedence for that information, including after transfer to FrameFlow and for data derived from it.

This policy describes our processing. Product websites, image hosts and independently operated endpoints may also process data under their own privacy notices. Their involvement does not remove any responsibility we have for processing that we determine or arrange.

Controller and privacy contact

The operator responsible for processing where it acts as controller is David Kurthy, trading as LOUDave Media, as identified in our Impressum.

• Business location: 6290 Mayrhofen, Austria

• Privacy contact: creative.loudave@gmail.com

• Telephone: +43 664 111 0618

• Main website: loudave.com

• FrameFlow service: frameflow.loudave.com

When a business customer determines the purposes and means of processing its workspace data and we process it only on that customer’s instructions, that customer is the controller and we act as a processor for that processing. The applicable customer agreement and data processing terms govern those instructions. We remain responsible as controller for processing whose purposes and means we determine ourselves.

Information we handle and where it comes from

We obtain information directly from you, from your browser and device when you use a covered feature, from forms through which you contact us, from an authorized business customer administering your access, and from product pages you choose to process.

• Contact and enquiry information: name, email address, business details, message content and information you choose to send us.

• Lead and subscription information: form responses, the requested offer or material, communication preferences and records needed to demonstrate consent or honor an opt-out.

• Website technical information: IP address, browser/device information, requested URLs, referring information, timestamps and technical errors, to the extent collected by our actual infrastructure.

• Optional website analytics and marketing information: identifiers, page interactions and campaign information collected by enabled tools, subject to the consent requirements described below.

• FrameFlow customer and workspace information: issued access details, login identifiers such as the email address used for customer access, credentials and related access-validation or session information, plus information needed to administer authorized access, associate work with a customer or workspace, and provide the specific product workflow requested. Service access credentials are confidential and are distinct from the extension’s pairing token.

• Product and image information: submitted product identifiers, image files or URLs, source-page information and related product metadata.

• Extension authentication information: the pairing endpoint and bearer token, plus supplied product, expiration and target-page information.

Do not submit passwords, payment-card details, private communications or sensitive personal information through product fields, image links or ordinary support messages. Images, product metadata and URLs can nevertheless contain personal information; customers should select appropriate source material and avoid unnecessary personal identifiers.

FrameFlow is a private product-image workspace. Its offered workflows include preparing product images, background presentation, centering, branding and bulk export. Processing relates to the product material and workflow the authorized customer selects. There is no public self-service registration.

The mere availability of an AI assistant on the LOUDave website does not authorize sending FrameFlow workspace content or extension data to that assistant. Any additional external processing must be disclosed for the relevant feature before use and remain subject to the restrictions applicable to that data.

Purposes and legal bases

Where the GDPR applies and we act as controller, the relevant purposes and bases are as follows. The legal basis depends on the actual relationship and processing, not simply on a user’s acceptance of this policy.

These legitimate interests are subject to necessity and a balancing of interests and rights. They are not a blanket basis for optional tracking or unrelated marketing. For extension data, the stricter single-purpose and Limited Use restrictions below also apply.

You are not generally required by law to provide enquiry or product-gallery data. However, we cannot respond to a request without sufficient contact information, provide restricted service access without necessary access information, or complete a FrameFlow transfer without a valid pairing and selected gallery. Refusing optional analytics or marketing consent does not itself prevent access to ordinary website content.

The GDPR’s transparency and lawful-basis requirements are set out in Articles 6, 13 and 14 of the GDPR.

LOUDave enquiries, newsletters and Meta lead forms

If you contact us, request material or submit a Meta Facebook/Instagram lead form, we use the information for the purpose stated at the point of collection. A request for a guide, quotation or callback does not, by itself, authorize unrelated newsletters, audience uploads or ongoing promotional messages.

Where a newsletter or separate marketing activity requires consent, we seek it separately and record the relevant preference. You may unsubscribe using the mechanism in a promotional email or contact creative.loudave@gmail.com. We may retain the minimum suppression information needed to respect your objection and avoid contacting you again.

Meta also handles information when you use its services and forms. The applicable form should identify the requested purpose, link to this policy and describe any separately offered marketing choice. A campaign’s promotional or commercial terms remain separate from this privacy notice.

We do not sell or rent personal data. Information collected through the extension is not added to newsletter lists or advertising audiences under the general website or lead-form provisions.

Website cookies, analytics and marketing technologies

Cookies, local storage, pixels and similar technologies can store or access information on a device. Technical necessity is assessed against the service the user requests, not simply against our business preference to measure or market it.

• Strictly necessary technologies: used where required to deliver requested functionality, security, session management or record a consent choice.

• Optional analytics: Google Analytics and Hotjar, where actually enabled, can process usage information and identifiers to measure website use or understand website interactions.

• Optional marketing: Google Ads and campaign or conversion technologies, where actually enabled, can process identifiers and interaction data for their separately disclosed purposes.

• Advertising fraud protection: Clixtell can process IP addresses, device/browser signals, campaign information and interaction patterns to identify suspicious advertising activity. A fraud-prevention label does not automatically exempt all associated device storage/access from consent requirements.

Where legally required, optional storage/access and associated processing must remain off until you give valid consent. Choices must not be preselected, and refusal must be as easy and prominent as acceptance. Continuing to browse or allowing cookies in browser settings is not consent.

You can change or withdraw optional consent through the website’s cookie controls. Browser settings provide additional controls but do not replace the website’s obligation to obtain any required prior consent. Withdrawal does not undo processing lawfully carried out before it.

The website displays a Cookie Compliance interface with privacy choices including Private, Balanced and Personalized and a Customize option. It loads consent-interface resources from cdn.hu-manity.co. Use the available privacy controls to review and change your choices. A mode’s label does not authorize processing outside the information and choices actually presented.

Google Analytics and Google Ads configuration, Clixtell, the consent interface, an ElevenLabs widget and Stripe.js have been identified on the public LOUDave website. The presence of a script does not mean that every feature of its provider is enabled, that every visitor makes a payment, or that a voice conversation has started.

Where Hotjar is enabled on a page, it can process website interaction and session-analysis information. This website analytics provision is separate from the extension and does not authorize monitoring customer gallery selections or pairing credentials.

These website provisions do not authorize Google Analytics, Hotjar, Meta or other advertising/analytics services to receive extension pairing tokens, selected source-page URLs, gallery selections or other extension data. Independent website-visit analytics must be assessed and disclosed separately from the extension workflow and must not be used to bypass the extension restrictions.

The Austrian rules on necessary and non-necessary device storage/access and valid consent are explained by the Austrian Data Protection Authority.

Optional AI assistance and payment functionality

ElevenLabs AI assistance

The LOUDave website offers AI-powered assistance using ElevenLabs/ElevenAgents. You interact with an AI system, not a human. If you use text chat, the messages and relevant context are processed to generate a response. If you use voice functionality and permit microphone access, voice/audio and related interaction data are processed for that feature.

The interaction may be handled by ElevenLabs, its affiliates, its relevant service providers and the configured language-model provider. Where recording or conversation retention is enabled, the interaction can be recorded or stored, and that practice requires a clear notice before the interaction. Do not submit access codes, extension pairing tokens, sensitive information or confidential customer material in the assistant.

Conversation storage, recording and provider data-use settings depend on the deployed configuration. We do not represent the assistant as zero-retention or training-disabled without verification. Requests about conversation data should be sent to our privacy contact so the relevant interaction and configured processing can be identified.

You can contact us by email or telephone instead of using AI assistance. Our responsibilities for user notice and any required consent are described in the ElevenAgents terms; the provider’s configurable retention controls are described in its retention documentation.

Stripe functionality

The website loads Stripe.js. Stripe can handle connection and device information for the functionality and security services associated with its integration. If an offered checkout is used, Stripe also handles the payment and transaction information supplied for it.

Loading Stripe.js does not mean that every visitor submits a payment or that LOUDave receives full card details. The processing and roles depend on the integration and transaction; further information is available in the Stripe Privacy Policy.

Frameflow Gallery Collector: purpose and access

The extension supports one purpose: collecting and preparing product gallery images for the FrameFlow product intake workflow, including related local download and JSON export.

FrameFlow is a closed customer environment. Access codes or other login credentials are issued to authorized users; there is no public self-service registration. The customer interface is marked for non-indexing by search engines. Non-indexing is not itself an access-control mechanism.

The extension is intended for existing, authorized FrameFlow customers. Installing it does not issue an access code, create service access or grant entry to a FrameFlow workspace. The service access code and the extension pairing credential serve different purposes. Local download and JSON export are separate functions and do not require a successful FrameFlow transfer.

The extension requests activeTab, scripting, downloads, sidePanel and storage, together with HTTPS host access and HTTP loopback access for localhost and 127.0.0.1. These support the active product-page workflow, packaged gallery reader and manual picker, download command, side-panel interface, session pairing and connections to customer-selected product sites and paired endpoints.

HTTPS host access is broad because product sources are not confined to a fixed retailer list. This permission is not used to crawl unrelated tabs or retrieve the browser’s complete history database. Browser permission does not authorize unrelated data collection or reuse.

Extension data collection and local processing

When you request gallery detection or manually identify a gallery, the extension processes the relevant page URL, title, hostname, available product metadata such as SKU, candidate image URLs, labels, dimensions, discovery details and your selection order.

It reads relevant page content and structured product/gallery data to locate image candidates. It injects packaged extension code and styling for detection and manual selection; the reviewed extension does not download and execute remote JavaScript or WebAssembly.

The interface holds gallery results and selections in memory, associated with the relevant tab. It handles the local clicks needed to perform your commands, not general behavioral monitoring or advertising profiling.

Pairing can be provided automatically by a compatible FrameFlow page or pasted by you. Pairing information can include the endpoint, bearer token, target product name, expected SKU, expiration and target page URL. It is retained in Chrome’s session-scoped extension storage, not Chrome Sync. Pairing may open the requested product tab.

Extension transfer, local export and network requests

Transfer to a paired FrameFlow endpoint

When you confirm the product and request a gallery transfer, the extension sends the source product-page URL, detected SKU where available and selected image URLs in the chosen order. It sends the pairing token as a bearer credential in the authorization header.

The receiving service uses this information for the requested product gallery import. The receiving infrastructure also sees network metadata inherent in the request, such as an IP address and request headers.

Our production service is frameflow.loudave.com. The existing extension also supports other HTTPS FrameFlow pairing endpoints and HTTP loopback endpoints at localhost and 127.0.0.1; it is not technically restricted to a single production hostname. Check the destination and target product before transferring information.

Local download and JSON export

The local download command asks Chrome to save the selected images from their source URLs to your computer. It does not, as part of that command, upload the downloaded files to FrameFlow.

The JSON export command writes source-page information and selected-image metadata to your clipboard. That command does not itself send the JSON to FrameFlow. Other applications, clipboard managers or websites may handle the export when you permit them or paste it.

Product image hosts and Fontshare

Displaying image previews, measuring candidate images and downloading files can contact the retailer or image CDN directly. Candidate-image requests can occur during review, before you request a FrameFlow transfer. Those servers receive information inherent in network requests, which may include IP address and browser/request headers.

The interface stylesheet requests the Satoshi font through Fontshare, including api.fontshare.com. When stylesheet or font resources are fetched, Fontshare and its delivery infrastructure may receive ordinary network metadata. This is a separate external resource request, not part of sending a selected gallery.

The extension package reviewed for this policy does not embed Google Analytics or Hotjar tracking code. This statement concerns the extension package, not the separate LOUDave or FrameFlow websites.

Extension Limited Use commitments

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. We apply the following commitments to all user data handled through the extension, including scraped content and data derived, aggregated, anonymized or de-identified from it:

• Single purpose: collection, use and transmission are limited to what is necessary for the disclosed gallery workflow and directly related operation, maintenance, security, performance and reliability.

• No sale or advertising reuse: we do not sell extension data, supply it to data brokers or advertising platforms, use it for personalized advertisements or retargeting, or create unrelated marketing profiles.

• No unrelated secondary use: extension data is not repurposed for unrelated market research, generalized profiling, unrelated product development or unrelated AI-model training.

• No lending use: we do not use or transfer extension data to determine creditworthiness or for lending purposes.

• Restricted transfers: transfers are limited to what is necessary to provide or improve the disclosed single purpose, comply with applicable law, protect against malware, spam, phishing or other fraud or abuse, or carry out a merger, acquisition or asset sale after obtaining explicit prior user consent as required by the policy.

• Restricted human access: people may read extension user data only with the user’s explicit consent to access specific data, where necessary for security, to comply with applicable law, or as aggregated and anonymized information for internal operations permitted by the policy and applicable law.

These restrictions apply after extension data reaches FrameFlow and prevail over any broader wording elsewhere in this policy. A separate website marketing consent does not waive them.

The governing requirements are available in the Chrome Web Store Limited Use policy.

Recipients, service providers and customer workspaces

Data can be made available to the following recipients to the extent relevant and permitted:

• Hosting, security and storage providers: operate the website or FrameFlow infrastructure, deliver content, store customer data and protect the service.

• Communication providers: deliver requested correspondence and separately authorized subscriptions.

• Optional website analytics/marketing providers: receive only the website data permitted by the relevant consent and disclosed configuration, not extension data for advertising or unrelated analytics.

• Product websites, image CDNs and Fontshare: receive the requests described above.

• Authorized customer workspace participants: access information within the relevant customer workflow, subject to customer instructions and access controls; operator access to extension data remains subject to the human-access restrictions above.

• Professional advisers, authorities or legal recipients: receive information only where there is a lawful, necessary basis and, for extension data, an allowed Limited Use ground.

Where providers act on our behalf as processors, the required processing agreements and safeguards must govern their handling. Independently acting platforms may act as controllers for their own processing; the relevant role must be identified accurately.

The following services are relevant to the identified setup:

Hostinger’s Data Processing Addendum describes its processor role for hosted customer data, subcontracting arrangements and security responsibilities. Its Privacy Policy separately describes its own processing and its handling of website users’ data on customers’ behalf. Hostinger’s list of possible subprocessors does not mean every listed service processes every FrameFlow gallery.

We do not identify a particular Hostinger contracting entity or server region for your data solely from the Hostinger brand name. Information about the applicable arrangement and relevant recipients can be requested from our privacy contact.

Retention and deletion

We retain identifiable data only for a defined purpose and no longer than necessary, taking into account applicable legal obligations and properly justified legal claims. A deletion request is assessed against the applicable legal conditions and does not override a mandatory retention obligation.

For customer workspaces, the retention criterion is the continuing need to provide the authorized customer’s product workflow. Relevant data is assessed for deletion when the customer requests deletion, the related material is no longer needed, or the service relationship ends, subject to applicable obligations and justified legal claims. Send a deletion request to our privacy contact where the relevant interface does not provide a deletion control.

For technical logs, the relevant criteria are the need to diagnose an identified problem, maintain service security, investigate an incident or abuse, and meet an applicable obligation or justified claim. Logs must not be used as an indefinite unrelated marketing or browsing-history record.

For access credentials and server-side pairing information, the criteria are the validity of the authorized access, the pairing’s supplied expiration or revocation, and any necessary security investigation. A locally expired token is not a representation that every server-side copy has already been erased.

Backup copies follow the applicable service’s retention/rotation and restoration arrangements and may not disappear immediately when live data is deleted. This policy does not promise that all FrameFlow data automatically disappears after a fixed number of days or that uninstalling the extension starts a backup-deletion timer.

Hostinger’s DPA states a thirty-day deletion rule after termination of the applicable processing agreement, subject to the particular covered service terms. That rule concerns the Hostinger service relationship, not an automatic thirty-day expiry for each FrameFlow user’s imported data. Its Hosting Agreement describes separate service-dependent backup arrangements.

AI-assistant conversation retention and optional analytics storage follow the relevant configuration and the purpose of the interaction or valid consent. We do not equate a provider’s published default with a verified setting for this website. Ask our privacy contact for the applicable retention information or deletion assistance for a particular interaction.

Disconnecting or uninstalling the extension does not automatically erase galleries already imported into FrameFlow, downloaded files or clipboard exports. Server-side deletion must use the applicable workspace deletion process or a verified request to our privacy contact.

International processing and transfer safeguards

Personal data may be processed in the EEA or elsewhere depending on the actual provider and destination. Merely choosing an EEA server region does not establish that all provider support access, delivery infrastructure or onward processing remains in the EEA.

Where a transfer subject to GDPR Chapter V occurs, the applicable arrangement must provide a lawful mechanism, such as a relevant adequacy decision or appropriate safeguards including Standard Contractual Clauses, together with any required supplementary measures. A cookie choice or acceptance of this policy is not a blanket substitute for those requirements.

Hostinger’s published information describes processing in jurisdictions including the United Kingdom, the Netherlands, Lithuania and Cyprus, and possible service-dependent use of servers outside the EEA, including the United States, Brazil, Singapore and Indonesia. These are provider-level possibilities, not a statement that your FrameFlow data is stored in every listed country or in a verified EEA-only location.

Hostinger’s DPA includes Standard Contractual Clauses for covered transfers to non-adequate destinations where those clauses apply. Other relevant providers and external resources can involve their own international processing. We do not assume that an EEA headquarters or an advertised privacy framework covers every processing activity.

You may contact us for information about the destinations and applicable safeguards relevant to your processing, including a copy or description of the relevant safeguards subject to legitimate redactions. Hostinger explains its arrangements in its DPA and Privacy Policy.

The applicable framework is set out in GDPR Chapter V.

Security and confidential information

We apply technical and organizational measures appropriate to the processing and risk, and limit access to authorized purposes. Measures must be maintained in practice; this notice does not claim unverified certifications, end-to-end encryption, universal encryption at rest or absolute security.

The extension requires HTTPS for remote FrameFlow transfer endpoints and permits HTTP only for the specified loopback pairing endpoints. It validates the expected endpoint path and token format and checks the calling-page origin against the endpoint origin for automatic pairing.

These checks do not establish the trustworthiness of an arbitrary pairing. Keep service access codes and pairing tokens confidential, use only authorized destinations and do not include codes or tokens in ordinary support emails. No system can guarantee complete security.

Your rights and choices

Where the GDPR applies, and subject to its conditions and exceptions, you may request access, rectification, erasure and restriction of processing. Data portability applies where processing is automated and based on consent or contract, to the extent the right applies to the information concerned.

You may withdraw consent at any time without affecting the lawfulness of processing before withdrawal. Where processing relies on legitimate interests, you may object on grounds relating to your particular situation.

Direct marketing objection: you may object to processing for direct marketing, including related profiling, at any time. We will stop processing your personal data for that marketing purpose after an objection.

Email creative.loudave@gmail.com to exercise your rights. We request only proportionate verification where needed; do not send a password or pairing token. If a customer controls the relevant workspace data, we may refer the request to it or assist it in responding.

We respond without undue delay and ordinarily within one month. Where permitted because of complexity or number of requests, this may be extended by two further months, with notice and reasons within the initial month. Requests are normally free; the GDPR permits limited exceptions for manifestly unfounded or excessive requests.

You may complain to a competent supervisory authority, including where you habitually reside, work or consider an infringement to have occurred. In Austria, this is the Österreichische Datenschutzbehörde. These rights and response rules are described in GDPR Articles 12–22 and 77.

Children and service audience

Our website offerings and FrameFlow customer tools are not directed to children under 16, and the extension is intended for authorized business workflows. This is an audience statement, not a claim that 16 is the legal consent age in every jurisdiction.

If you believe a child has supplied personal data contrary to this intended audience, contact us so we can assess and address the situation.

Changes to this policy and processing practices

We update this policy when our actual processing or applicable requirements change. The revision date identifies this version; it is not evidence that an unimplemented control is already in place.

For the extension, we prominently disclose the data collected and its use before installation and obtain the affirmative, informed agreement required by the Chrome Web Store rules. New or different data practices after installation are proactively and prominently communicated; where required, new consent is obtained before the changed processing begins.

Updating this page alone is not a substitute for a required prominent disclosure or consent. The disclosure requirements are described in the Chrome Web Store Disclosure Requirements, including the updates enforced from 1 August 2026.

The extension’s Chrome Web Store listing, privacy disclosures and relevant in-product information must describe the actual workflow. This policy is not permission to start undisclosed processing merely because a broad browser permission has been granted.

Contact

For privacy questions, requests or concerns, contact LOUDave Media at creative.loudave@gmail.com. The full legal operator and postal contact are identified in the controller section above.

The intended permanent location of this policy is loudave.com/privacy-policy/. The FrameFlow homepage should link to that same policy so users can find the extension-specific provisions directly.

 

FrameFlow Image Rights and Authorized Use Terms

Last updated: 26 October 2026

Scope

This section sets out the image-use conditions for FrameFlow and the Frameflow Gallery Collector Chrome extension, operated by David Kurthy, trading as LOUDave Media. It applies to product-image collection, downloads, transfers, exports and processing requested through these services.

Although published on the same page as our Privacy Policy, these are image-use conditions, not consent to personal data processing. Publication of these conditions does not, by itself, establish that a user has expressly accepted them, and neither these conditions nor a rights declaration creates rights in third-party images.

Required rights and authorization

You may request an image-related operation only if you own the necessary rights, hold a valid license or permission covering that operation, or have another verifiable legal basis permitting it. Public availability, a source URL, attribution, reseller status, access to a product page or access to a private FrameFlow workspace does not by itself establish permission.

Your authorization must cover the operations you request, including, where relevant:

• Retrieving, downloading and reproducing the image.

• Storing it locally or within FrameFlow.

• Transferring it to the service operator and the necessary authorized service providers.

• Editing, cropping, changing backgrounds, adding branding or performing AI-assisted transformations.

• Exporting, publishing or commercially using the resulting material.

An existing manufacturer, supplier, stock-image or open license may cover multiple images. A new, individually negotiated license for each file is not required where your existing rights already cover the requested operations and intended use.

You must comply with applicable conditions, including attribution, permitted purposes, duration, territory, commercial-use restrictions, modification restrictions and limits on third-party processing. Authorization for one use must not be assumed to cover a different use.

Verification and evidence

Before requesting an operation, verify that your authorization covers every selected image and the intended use. Maintain appropriate evidence identifying the relevant images or collection, the rights holder or authorized licensor, the permitted uses and any restrictions; a source URL alone is not evidence of permission.

If permission comes from an employer, manufacturer, distributor, agency or another intermediary, verify that it has authority to grant the relevant rights. If the position is unclear, obtain clarification before requesting the affected use.

If you rely on public-domain status or a statutory permission rather than a license, verify that this basis applies to the particular image, jurisdiction and intended use. FrameFlow does not automatically determine whether a copyright exception applies.

Authorization necessary to provide the requested service

When requesting processing, you must have the authority to permit the service operator and the necessary authorized service providers to access, reproduce, store, display within the private workflow, process and export the selected material as required to perform that request. Any permission you provide is limited by your actual rights and cannot expand a third-party license.

The requested service does not, by itself:

• Transfer ownership of the images.

• Expand an existing third-party license.

• Authorize unrelated AI-model training.

• Permit the service operator to use the images in public advertising or a portfolio without separate permission.

Any additional permission must be obtained through an appropriate, separate arrangement. Personal data processing remains subject to the relevant provisions of this Privacy Policy.

Prohibited use

You must not use FrameFlow or Frameflow Gallery Collector to:

• Access, download or otherwise use protected material without the necessary authorization.

• Circumvent paywalls, login restrictions or effective technical protection measures.

• Remove or falsify watermarks, mandatory credits or rights-management information without authorization.

• Modify, publish or commercially exploit images beyond your actual rights.

• Misrepresent endorsement by a brand, retailer, creator or rights holder.

• Treat browser permissions, software access or a checkbox declaration as an image license.

Applicable source-site terms, privacy and personality rights, trademarks and other relevant rights must also be respected. A copyright license alone does not establish that every proposed use complies with all other applicable requirements.

Rights declaration in the extension

The extension includes a checkbox through which the user confirms that the selected images show the correct product and colorway and declares that they hold the rights or permissions necessary for the requested download, transfer, processing and intended use of those images.

This declaration concerns rights that must already exist. It does not grant an image license, replace authorization from the rights holder or establish acceptance of the entire Privacy Policy or these image-use conditions.

The declaration must be accurate for every image and intended operation to which it relates. If the selection, intended use or authorization changes, the user must reassess whether the declaration remains accurate.

The declaration is not automated license verification. The extension does not independently establish ownership or validate the underlying license.

The checkbox wording does not mean that every download, export or other operation is technically blocked until the checkbox is selected. The wording update leaves the existing workflow and operation-specific controls unchanged.

Rights-related information and correspondence

The checkbox wording change does not introduce a separate acceptance database, timestamped acceptance receipt or transmission of the checkbox declaration to FrameFlow. It does not add collection of a terms version, license document or rights-evidence record, and it does not affect the ordinary transfer and technical processing described elsewhere in this Privacy Policy.

If you contact us about image rights or provide supporting evidence, we process the information necessary to assess the request, administer authorized service use and address the relevant concern. This may include your contact details, the affected image or product reference, the authorization you describe and relevant correspondence.

Depending on the circumstances, the legal basis is contract performance where applicable, a properly assessed legitimate interest in handling rights concerns and legal claims, or an applicable legal obligation. We retain such correspondence and evidence only for the relevant purpose and any justified legal retention period.

Do not include passwords, access codes or pairing tokens in rights evidence or ordinary support messages. If we need additional information to assess a concern, we will request only information proportionate to that purpose.

Rights concerns and disputed material

If you discover that authorization is missing, disputed, expired or withdrawn, stop the affected use and notify the service operator. A previous checkbox declaration must not be relied upon to continue using material once you know that the necessary authorization is absent.

Rights holders and authorized representatives may report concerns to creative.loudave@gmail.com. Please identify the affected material, explain the asserted rights and provide a reliable contact method.

The service operator may request proportionate supporting information and restrict or pause disputed material while assessing a credible concern or complying with an applicable obligation. Any assessment depends on the available facts and does not constitute an automatic determination of ownership.

Responsibility

You are responsible for the accuracy of your rights declaration and compliance with the applicable license conditions. The service operator remains responsible for its own conduct and applicable obligations.

These conditions do not exclude liability that cannot lawfully be excluded, remove a rights holder’s claims or replace mandatory legal requirements. Neither these conditions nor the software guarantees that a particular image use is lawful or approved by Google.

Contact

The service operator is David Kurthy, trading as LOUDave Media, with the business location provided as 6290 Mayrhofen, Austria. For image-rights questions, contact creative.loudave@gmail.com or telephone +43 664 111 0618.