Who is responsible
feedrevive is the product name. The operating legal entity, registration number and registered address must be inserted and verified before this notice takes effect. Contact privacy@feedrevive.com for privacy enquiries.
The live website today
This public marketing website is hosted by Vercel. Visiting it sends technical request information to the hosting infrastructure, which may include your IP address, requested URL, time, browser information and security events. This is separate from the future application described below. No signup, checkout, store connection or AI processing is available through this website.
The contact form sends your name, email address, optional website, topic and message through a Vercel server function to Resend for email delivery to hello@feedrevive.com. Data is submitted only when you select Send enquiry. Our email service receives the message to handle your enquiry. The form does not create an account or marketing subscription. A time-limited signed form token and temporary request counters help prevent automated abuse; these do not use tracking cookies. Avoid sending passwords, access tokens, payment details, customer lists or sensitive personal information. Browser autofill and your email provider are controlled separately.
Purposes and legal bases
The intended GDPR mapping is: necessary website delivery and proportionate abuse prevention on legitimate interests in maintaining a secure website; answering business enquiries on legitimate interests in business communication, or steps requested before a contract where the individual is the prospective contracting party; optional preference storage on your affirmative choice; and any legally required records on the relevant legal obligation. These bases require the operator’s documented assessment and cannot be used as blanket permission for additional purposes.
Providing an enquiry is voluntary; without a reply address or enough context, a response may not be possible. No account or payment information is required simply to browse. Future account administration, invoicing, platform imports and marketing require a separate verified purpose, role and legal-basis mapping before activation. Consent to marketing must remain separate from support, purchase and service notices.
Data and purposes
The planned service would process account and contact details to manage access and enquiries; store catalog and Merchant data to diagnose feed issues; source evidence, proposals and approvals to support controlled changes; and usage, credit and transaction metadata to operate subscriptions and troubleshoot the service.
The final notice must map each purpose to its applicable legal basis. Contract necessity, legal obligations, legitimate interests and consent must be assessed for the actual processing rather than treated as blanket permission.
The contact form sends your enquiry through Vercel and Resend to our team. See the live-website section below for current processing.
Sharing and AI processing
Infrastructure, email, payment and AI suppliers may process the minimum data required for their functions. The supplier list, contracts and processing locations require verification. Cross-customer learning is off by default and requires a separate explicit opt-in with verified privacy conditions. Do not infer provider training or retention practices from this product rule.
Sources, recipients and safeguards
Current sources are your browser and information you choose to send. Future service data may come from workspace administrators and expressly connected store or Merchant accounts. Customers must give required notices to people whose information they supply. A connected merchant generally determines why its catalog data is processed; requests concerning that merchant’s data should be directed to that merchant, with processor assistance where applicable.
Authorized personnel and contracted hosting or communications providers may receive data needed for their roles. Disclosures to authorities must have a valid legal basis. Any advisers, payment processors, AI services or corporate transaction recipients require role and confidentiality review before receiving personal data. See the supplier register and verification status.
USA application storage is a plan, not a promise that all processing stays in one country. Remote support, hosting networks and supplier subprocessors can create additional transfers. Applicable adequacy decisions or properly completed transfer safeguards, risk assessments and supplementary measures must be verified. A link to a supplier’s standard DPA is not proof that feedrevive has executed it. You may request information about relevant safeguards through the privacy contact.
Retention by purpose
The optional preference remains in this browser until removed. Unsent contact text is not persistently stored by this website. Submitted enquiries are processed by our hosting and email services; the form does not add a separate contacts database. Temporary rate-limit counters expire within one hour in the running server instance. Actual hosting-log and received-email retention periods have not yet been verified; this is an outstanding disclosure, not an unlimited retention permission. Retention must be tied to delivery, handling the enquiry, security, legal recordkeeping or a documented dispute, with access restricted and deletion reviewed when that need ends.
The future application retention targets do not establish retention for this marketing website. Any mandatory accounting retention must identify the applicable legal requirement and retain only necessary records. Removing an account, ending a subscription, unsubscribing and exercising erasure rights are separate actions; none authorizes unrelated indefinite retention.
Retention and deletion
Current design targets are 12 months for detailed diagnostic/change history and security logs, and 30 days for backups and redacted AI troubleshooting traces. Provider configuration and legal recordkeeping requirements must be validated before these become operational commitments.
The plan targets deletion of active customer data within 30 days of a verified deletion request, subject to justified required records. Backups expire under a separate retention schedule. Cancellation and account deletion are different requests.
Rights, response times and complaints
Where GDPR applies, rights include access, correction, erasure, restriction, portability where its conditions apply, objection to legitimate-interest processing, and withdrawal of consent without affecting earlier lawful processing. Direct-marketing objections must be respected. Rights have legal conditions and exceptions; a draft label does not suspend them.
Requests normally require a response within one month. A permitted extension of up to two further months must be explained within the first month. Requests are generally free. Identity checks must be proportionate; do not send identity documents unless a necessary secure verification method is agreed. Where a request cannot be fulfilled, the reason and available complaint or judicial remedies must be explained.
You can complain to Sweden’s Authority for Privacy Protection (IMY), or the competent authority where you live, work or where an alleged infringement occurred. You do not need to exhaust our support process first. Contact privacy@feedrevive.com; the legal controller identity and any required representative or data protection officer remain to be confirmed.
Children, automation and changes
This site presents a business product and is not directed at children. Please do not submit children’s information. The deployed website does not make automated decisions producing legal or similarly significant effects about visitors, run advertising profiles, or send contact-form content to an AI provider. Proposed product suggestions require human review; future automated personal-data uses need their own assessment and disclosure.
Privacy requirements outside the EEA depend on the operator, customers, processing and applicable thresholds. No universal exemption or worldwide compliance claim is made. New purposes, tracking, service launches or material supplier changes require updated information and, where required, new consent before processing begins. Revision date: 26 October 2026; unresolved identity and operational details remain visibly marked.
Outstanding verification
Complete the controller identity, lawful-basis mapping, recipient and subprocessor list, transfer safeguards, local privacy disclosures, retention evidence and complaint route. Set the effective date after review.