Reading note
This is an operating disclosure, not a promise that Amazon will remove a review and not a substitute for the binding Terms of Service or Privacy Policy. Amazon alone decides whether content remains on its marketplace. Where this page and the binding terms differ, the binding terms control.
Review Magic is independent from Amazon. Amazon and related marks belong to their respective owners.
Control 01
Scope and control objective
The service is limited to policy-based review monitoring and appeal support for authorized listings.
Current production scope
Review Magic monitors Amazon product listings, collects available public review and product metadata, analyzes review text for potential policy issues, prepares evidence-backed case records, routes authorized filings, tracks Amazon-side status, and records verified outcomes and billing events.
- Client scopeA client may submit only listings it owns, manufactures, or is legitimately authorized to manage.
- Decision ownerAmazon retains sole authority over content moderation and review removal. Review Magic cannot compel or guarantee an outcome.
- Service postureThe system challenges specific policy issues. Ordinary negative product feedback remains outside the removal workflow.
- Platform statusAmazon is the current customer-facing review-removal marketplace. Future platform support is not represented as live until it is separately launched and disclosed.
Control 02
Case methodology
Each case preserves the source review, the proposed rule, the authority to act, and the observed outcome.
- 01CollectCapture available public review text, rating, date, reviewer display name, listing identifier, source URL when available, and collection time.
- 02ClassifyUse automated analysis to identify possible policy issues. A model output is a candidate signal—not a filing decision and not an Amazon decision.
- 03GroundMatch the proposed issue to cataloged Amazon policy language and preserve the exact review excerpt supporting the match. Unsupported matches fail closed or require specialist review.
- 04AuthorizeConfirm the client, listing, brand, filing identity, standing authorization, and any paid-action authority before the case can move to filing.
- 05FileA trained operator uses an official Amazon reporting or Seller Central workflow and records the filing state and available case reference.
- 06VerifyRecheck the live source. A removal is not treated as successful merely because a report was submitted or a case was opened.
- 07AccountConnect the verified outcome to the applicable included credit, introductory credit, rollover credit, success fee, or zero-dollar record.
Control 03
Decision standard
Negative sentiment is not a violation. The case must stand on the review text and a current policy source.
Required elements before filing
- Source recordThe listing and review are identifiable, the quoted evidence is traceable to the captured source text, and the review is still available for current verification.
- Policy basisAt least one specific, cataloged policy clause supports the proposed issue. Category labels alone are insufficient.
- Human reviewA specialist reviews the proposed basis and filing artifact. Automated analysis does not independently submit an appeal.
- UncertaintyBorderline evidence is labeled for review. Missing, stale, or contradictory evidence is not converted into a stronger public claim.
Prohibited operating practices
- Writing, buying, or incentivizing reviews.
- Asking a shopper to remove or change a review.
- Compensating a reviewer for changing content.
- Fabricating evidence, quotations, policy text, or case IDs.
- Automatically mass-reporting unreviewed candidates.
- Impersonating Amazon personnel or claiming privileged access.
- Targeting competitor listings without documented authority.
- Representing a candidate as guaranteed removable.
Control 05
Billing controls
The filing event and the billable outcome are different events. A submitted case is not a successful removal.
- VerificationA success fee requires a recorded, source-level verification that the review is no longer live. If the review remains live, no success fee is due for that case.
- Consumption orderSubscription removals use the applicable introductory credit, included allowance, and rollover credit before an additional success fee is assessed, subject to account budgets and caps.
- Intro offerAn eligible new legal client may start one monthly subscription with a 30-day trial and a card on file. The subscription charge is $0 at enrollment. The first removal verified within the trial window is free; additional trial removals use the selected plan's disclosed success fee. Regular plan allowances begin with the first paid period. Annual subscriptions do not include the trial: they are billed in full at enrollment and are priced at nine monthly payments for a twelve-month term.
- EligibilityThe introductory offer is one-time per legal client workspace. Subscription history prevents a canceled account from receiving a second introductory offer.
- CancellationA customer may cancel during the trial or a paid term through the supported billing flow. A trial cancellation prevents the subscription renewal charge and keeps the stated trial access through the scheduled end unless Stripe ends it sooner for a payment-method or account reason.
- Audit eventZero-dollar introductory and included removals are still recorded as billing outcomes so the case, credit, and reversal history can be reconciled.
The complete commercial terms, including plan pricing, payment authorization, caps, disputes, refunds, renewals, and cancellation, are controlled by the current Billing and Refund Policy.
Control 06
Data handling
The service separates public marketplace content from customer account, authority, and billing information.
| Data class | Examples | Purpose |
|---|---|---|
| Public marketplace data | ASIN, title, rating, review text, reviewer display name, date, public URL | Monitoring, assessment, evidence, outcome verification |
| Customer account data | Name, work email, organization, roles, settings, support communications | Authentication, tenant access, service delivery, support |
| Authority records | Approvals, filing identity, agency consent, paid-action consent | Prove who authorized a filing, fee, or access change |
| Billing records | Stripe IDs, plan, invoice/charge status, card brand and last four when supplied | Payment processing, reconciliation, disputes, accounting |
| Operational records | Case events, provider timestamps, queue state, audit events, error telemetry | Reliability, security, investigation, support, evidentiary history |
Collection and retention boundaries
Public reviews are collected from publicly available marketplace surfaces through configured data providers. Review Magic does not need a Seller Central login to read public review pages. If a customer activates an available Amazon catalog connection, that connection uses Amazon's revocable authorization flow; otherwise catalog entry uses ASIN, CSV, or Seller Central report import.
Full payment card numbers and CVV values are handled by Stripe and are not stored by Review Magic. Authentication passwords are handled by Clerk. Seller Central passwords and one-time codes must not be sent to Review Magic and are not an accepted onboarding method.
Information is retained while an account is active and as needed to provide the service, preserve case and financial records, enforce agreements, resolve disputes, and meet legal obligations. Personal data deletion or anonymization requests are handled under the current Privacy Policy, including its stated post-termination period and legal-retention exceptions.
Control 07
Service providers
Third parties receive only the categories needed for their role, subject to their own terms and controls.
| Provider | Function | Relevant data |
|---|---|---|
| Amazon | Marketplace source, catalog authorization, and filing destination | Public listing/review data; authorized catalog and case data |
| Apify / configured fallback providers | Public marketplace collection | Public listing and review data |
| Google Gemini | Candidate review analysis | Review text and limited product context |
| Clerk | Authentication and organization identity | Account and authentication data |
| Stripe | Checkout, subscriptions, invoices, and payments | Billing identity and payment data |
| MongoDB Atlas | Primary data storage | Customer, listing, case, and billing records |
| Render | API and worker hosting | Runtime data in transit and operational logs |
| Vercel | Web application hosting | Web requests and hosting logs |
| Resend | Transactional email | Recipient address and message content |
| Sentry, when configured | Application error monitoring | Error and request telemetry; sensitive values should be excluded |
Providers and configurations can change. A material change is reviewed against the Privacy Policy, security requirements, and contractual obligations before production use.
Control 08
Security and access
Controls are organized around tenant isolation, least authority, signed integrations, and recorded administrative action.
- Tenant isolationCustomer reads and writes are scoped to the legal client organization. Agency access does not replace client ownership.
- RolesClient, agency, operations, and administrator surfaces have separate access rules. High-impact actions require the relevant role and, where applicable, recorded customer authority.
- IntegrationsInternal service requests use signed authentication. Stripe and Clerk webhook handlers verify provider signatures before applying external events.
- CredentialsConfigured Amazon OAuth tokens are encrypted before storage and tied to a key version. Payment and authentication secrets remain with the applicable providers.
- AuditabilityAdministrative mutations, case events, approval events, filing state, and billing outcomes are retained as operational records.
- IncidentsSecurity, billing-integrity, and full-queue outages are escalated under the internal incident process. No Internet service can guarantee absolute security or uninterrupted availability.
Privacy, access, correction, or deletion requests may be sent to privacy@reviewmagicco.com. Security concerns may be sent to support@reviewmagicco.com.
Control 09
Amazon source material
Policy sources are maintained as external references. Amazon may revise or relocate them without notice.
- Community GuidelinesCustomer-facing rules governing reviews and other community content, including relevance and prohibited content.
- Report AbuseSeller Central reporting reference for review content that may violate Amazon policy. Authentication may be required.
- Seller Code of ConductSeller-facing conduct requirements that apply to clients and service providers acting on their behalf.
- Customer Reviews toolAmazon's public explanation of review monitoring, customer response limits, and reporting reviews that do not follow its community guidelines.
A link appearing here does not mean Amazon endorses Review Magic. The operative source is Amazon's current policy at the time of the assessment and filing.
Control 10
Example case record
The example shows the structure of a record, not a customer, guaranteed result, or promised timeline.
Illustrative anatomy
Synthetic field descriptions—not a customer case or promised result
Record structure / v1
SECTION 01
Source record
- Listing
- Marketplace + ASIN + legal client + brand
- Review
- Rating + source text + date + canonical URL
- Collection
- Provider, captured-at time, and available history depth
SECTION 02
Policy assessment
- Candidate basis
- Quoted review fragment and the rule it may implicate
- Decision state
- Supported, unsupported, or specialist review needed
- Evidence
- Source excerpt, policy citation, and model revision
SECTION 03
Authority and routing
- Authorization
- Standing client authorization · monthly removal budget
- Filing identity
- Legal identity approved for the affected brand
- Audit trail
- Actor, action, reason, and timestamp
SECTION 04
Outcome and billing
- Amazon outcome
- Pending until Amazon acts; Review Magic cannot decide it
- Verification
- Observed source state and verification history
- Billing event
- None unless a removal satisfies the verification rules
Control 11
Records and change control
A compliance statement is only useful if the running product and its records can be reconciled to it.
- Case recordSource evidence, policy basis, decision state, authority, filing state, outcome checks, and billing event remain linked.
- VersioningPolicy catalogs, terms acknowledgements, agency agreements, consent language, and this disclosure use explicit versions or effective dates.
- Material changeMaterial legal-term changes require an effective-date update and, where applicable, renewed acceptance before protected account activity continues.
- Provider driftProvider output, policy links, filing workflows, and billing events are subject to contract and guardrail tests intended to detect incompatible changes before release.
- Customer recordCustomers can inspect case status, evidence, outcome, and charges in the applicable account surfaces. Internal-only security and anti-abuse details are not publicly exposed.
Control 12
Counsel review notes
This section identifies the legal-review boundary so an attorney can distinguish previously reviewed material from later product changes.
Review status
The underlying legal framework and the then-published Terms, Privacy Policy, Acceptable Use Policy, billing terms, and dispute language were recorded as reviewed and approved on June 1, 2026. This August 22, 2026 operating statement includes later agency, authorization, catalog, and introductory-offer changes. It should be reviewed as a new disclosure version and must not be described as attorney-approved until that review is complete.
Requested review points
- Whether the public-data collection and provider disclosures remain sufficient for current operations and jurisdictions.
- Whether client, agency, filing-identity, and paid-action authority language accurately allocates responsibility.
- Whether the 30-day introductory offer, first-removal credit, renewal, cancellation, and additional success-fee disclosures are sufficiently clear and conspicuous.
- Whether the subprocessor, AI-analysis, retention, international transfer, and data-subject-right disclosures require amendment.
- Whether the described evidence, filing, verification, reversal, and audit controls create any additional record-retention duty.
- Whether the marketing descriptions of rating milestones and prompt monitoring remain appropriately qualified and substantiated.
Legal questions and redlines: legal@reviewmagicco.com. Billing questions: billing@reviewmagicco.com. Disputes: disputes@reviewmagicco.com.
Last product review: August 22, 2026 · Document version RM-COMP-2026.08.22