LEGAL

Privacy Policy

What this policy covers

This policy covers Feediqo at feediqo.com: a business and ecommerce prospecting service for finding companies, professional contacts, Shopify stores, and WooCommerce stores. It covers information about Feediqo users as well as the business lead and contact records made available through the product. It does not describe a shopper, checkout, order, or Shopify merchant application.

Information about Feediqo users

Google sign-in provides an account identifier, name, email address, and profile image. We also process onboarding choices, searches, saved filters, prospect lists, private notes, pipeline status, follow-up dates, revealed-record history, exports, credit activity, subscription status, support messages, and security and request logs. PayPal processes checkout and payment-card details; Feediqo receives subscription, transaction, and payment-status information, not the full card number.

Business lead and contact data

Depending on the available record, Feediqo may hold:

Feediqo is intended for business prospecting. We do not intentionally collect shopper orders, checkout contents, consumer payment-card data, passwords, or special-category data such as health, religion, or political beliefs for the lead directory.

Where lead data comes from

Lead records may originate from licensed or acquired business-data datasets, publicly available business websites and professional or company profiles, ecommerce-store and technology observations, and enrichment datasets that associate public business contact details with the relevant company or store domain. Records from different sources can overlap, be incomplete, or become outdated. Contact availability is not a guarantee of deliverability, consent, or current employment. See our data-quality notes.

Why we process information

We use account and workspace information to authenticate users, provide saved work, deliver contact reveals and exports, administer subscriptions and credits, answer support requests, prevent fraud and abuse, diagnose failures, and comply with legal obligations. We process business lead data to operate search, filtering, record review, contact reveal, list, and export features and to correct, deduplicate, secure, and maintain the directory.

Depending on the jurisdiction and activity, processing may rely on performing our contract with a user, our legitimate interests in operating and securing a B2B prospecting service, consent where it is requested, or compliance with law. Feediqo does not make legal or similarly significant decisions about a person using automated profiling.

How information is disclosed

Feediqo makes business lead and contact records available to authorized users as the core prospecting service. Depending on local law, providing access to these records may be treated as a sale or sharing of personal information. A person may object or request removal using the contact method below.

We also disclose information when needed to service providers that operate the product, to comply with a valid legal request, to protect users and the service, or as part of a business transaction subject to appropriate safeguards. We do not sell Google account information or private workspace notes.

Service providers and processors

Providers process information for these purposes under applicable terms and may operate in countries other than yours. We use contractual and technical safeguards appropriate to the service and transfer involved.

Retention, correction, and deletion

Account and workspace information is retained while an account is active and then deleted or de-identified when it is no longer needed to provide the service. Limited billing, fraud-prevention, security, dispute, and legal records may be kept for the applicable statutory or limitation period. Operational logs are kept only as long as reasonably needed for security and reliability.

Business lead records are retained while they form part of the maintained directory. They may be replaced, corrected, suppressed, or deleted when they become obsolete or after a valid request. Verified removal requests are removed or suppressed from active search so the same record is not intentionally republished from a later import. Residual copies may remain temporarily during routine recovery processes, unless law requires longer retention.

Your privacy rights

Subject to applicable law, you may request access to information about you, correction, deletion, restriction, portability, or an explanation of the source and use of a record. You may object to processing, opt out of a legally defined sale or sharing of personal information, withdraw consent where processing relies on consent, and complain to your local data-protection authority. We may need to verify identity and the connection to a business email, profile, or domain before acting on a request. Authorized agents may submit a request where local law permits.

Feediqo users can also sign out and revoke Feediqo's access from their Google Account. Removing Google access does not by itself delete an existing Feediqo account; contact us to request account deletion.

Security

We use encryption, access controls, and monitoring intended to protect information. No service can guarantee absolute security. If you believe information has been exposed or an account has been misused, contact us promptly and do not send passwords, payment-card numbers, or access tokens.

Children and changes to this policy

Feediqo is a business service and is not directed to children. We may update this policy when the product, data sources, providers, or legal requirements change. Material updates will be identified by a revised date on this page.

Contact Feediqo

Feediqo is the controller responsible for the product described on this page. For privacy questions, account deletion, a lead-data access or removal request, or a correction, email na_zerguine@esi.dz. Include the relevant business email, profile URL, or domain and the request you want us to review. Do not send passwords or sensitive identity documents unless we specifically request an appropriate verification method.