Privacy Policy

Updated October 30, 2026 · 2026-10-08-v1

Valencia Supply LLC DBA ReviewDoctor, 6800 Rolling Mill Rd, Baltimore, MD, United States, operates ReviewDoctor. Contact info@reviewdoctor.com or use our privacy request form.

Referral program and welcome emails

Refer & Earn stores enrolled partner account identifiers, verified email, a random referral code, tier history, referred-account attribution, eligible invoice and charge references, commission adjustments, and payout receipts. A secure, HTTP-only referral cookie defaults to 30 days and is created only after you choose to use a partner referral. The first eligible link is captured at new registration and later links do not replace it before expiry. The browser token is random; only its hash and attribution timestamps are stored. Partner payout-contact details are encrypted, and changes to program rules, partner overrides and payout receipts are audited. Bank credentials are not collected. The configured attribution window is shown on the referral landing page. Referrers see anonymized activity rather than referred account email addresses. Authorized Master Admin can inspect account and financial records. These records support program administration, abuse prevention, reconciliation and applicable recordkeeping obligations, and can be reviewed through a verified privacy request. New registrations have a transactional welcome-email receipt after email verification. Provider acceptance is not delivery confirmation, and account emails do not create marketing consent.

Appointment scheduling

Businesses can publish services, public team names and available appointment times. Booking records include your name, email, phone, selected service and team member, appointment time and timezone, email preference, booking changes, status, and a linked check-in reference when you arrive. Contact details are self-reported. Keep your private management link confidential: anyone with it can view your booking and, subject to the business's rules, reschedule or cancel it. Private access expires 30 days after the appointment starts. Optional confirmation, change, cancellation and reminder emails are sent through our email provider only when requested for that booking; they do not create marketing consent. Appointment records and delivery receipts have a one-year deletion rule after the appointment end, applied by the appointment background processor. Inactive storage can await the next run. NDA retention remains separate. Use this scheduling feature for general business appointments, not medical records or protected health information.

NDA documents and electronic signing

When a business enables NDA signing, we store its document versions, the signer's name, email, phone, typed signature, explicit electronic-signing consent, UTC timestamp, document hashes, and a linked visit reference when applicable. A signature record is appended to the reviewed PDF. Contact details are self-reported, not identity-verified. Signed documents are available only to the business owner and, for seven days, to the signer through their private download credentials. Signed documents and their supporting templates remain for future business records until deletion through a privacy request or account deletion; ordinary visitor-logbook expiration does not delete signed agreements. Contact the business or submit a privacy request for access or deletion, subject to applicable recordkeeping obligations. Signing does not grant SMS or marketing consent.

Marketing SMS subscriptions and campaigns

Promotional SMS requires a separate, optional marketing subscription; feedback permission is not reused. We store the business, mobile number, optional name, selected timezone, consent wording and date, subscription status and delivery receipts. These support messages, opt-outs, quiet hours and frequency limits. Subscriber contact details and consent wording expire after one year unless renewed; campaigns and recipient receipts are deleted after one year. STOP disables marketing messages for that sender. Replies and delivery events are processed through Twilio. The campaign preview estimates SMS segments, not total dollar charges.

Customer profiles, conversations, follow-up tasks and offers

Within each business, exact phone matches group retained check-in, loyalty, marketing opt-in and SMS activity into contact profiles. Email-only contacts remain separate. Shared numbers may represent more than one person; names are not used to infer identity. A contact profile or service interaction does not grant marketing permission. New Wi-Fi opt-ins can identify their form source; this does not track browsing or confirm a physical visit.

Incoming customer SMS and business support replies, their phone numbers and delivery status are visible to the business owner. Conversation content has a 90-day deletion rule. STOP and other opt-out controls are processed without adding a support conversation. Owners can assign follow-up tasks to active staff; staff see only their assigned tasks. Task notes have a one-year deletion rule measured from the latest update. Offer redemption receipts store a keyed contact identifier, business, offer, actor and timestamp, rather than a new copy of the phone number; offer records and receipts have a one-year deletion rule from offer creation. These counts do not establish sales attribution.

Weekly report emails are optional and off by default. Enabling sends aggregate business activity to the owner’s verified account email every seven days when processing runs; customer names and message contents are excluded. Owners can disable delivery in the weekly report screen. Report submission receipts have a 90-day deletion rule. Cleanup occurs when the existing background follow-up processor runs; provider retention and backups are separate. Deletion requests for source records and engagement records require verified, business-scoped review.

Digital menus and photo import

Business owners can publish menus, item photos, prices and business branding. Published menu content is public. With the owner’s confirmation, menu-import photos are sent to OpenAI to extract menu text. ReviewDoctor does not save those import-source photos in its photo library or public menu. Extraction results, status and image fingerprints are temporarily stored to recover interrupted requests and avoid repeat processing; they expire after 24 hours and are deleted during subsequent import cleanup. Reviewed items are added to the owner’s draft only when selected, and become public only after publishing. Menu photos intentionally uploaded to the menu image library are stored separately until the owner deletes them; referenced draft and published images are protected from deletion. OpenAI’s own processing and retention policies apply to the images it receives.

ReviewDoctor brand and data use

This Privacy Policy covers ReviewDoctor, the brand operated by Valencia Supply LLC DBA ReviewDoctor. We collect account and business details, email addresses or mobile numbers you choose to provide, optional names, feedback, consent records, check-in and visit-completion timestamps, subscription records, and delivery status information. We use this information to operate accounts and business workspaces, process subscriptions, deliver requested feedback invitations and reminders, share feedback with the business you visited, honor opt-outs, and protect the service.

Business owners and authorized platform administrators may provide a business street address and an owner or primary contact name, email, and phone number for account management and support. These contact fields are visible to the business owner and platform administrators, are not printed on customer QR signs, and do not change account sign-in credentials. Platform administrators may export business directory records for account management. An account email may also be shown from an existing sign-in record; a contact email does not verify ownership of that address.

SMS privacy

We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes.

ReviewDoctor uses your mobile number and SMS consent records only to provide the feedback messages you authorized, manage delivery, and honor your messaging choices. SMS consent does not enroll you in marketing. We share only the information needed with messaging and hosting providers, including Twilio, to deliver and secure this service. The business you visited can access its own check-in and feedback records to manage your requested follow-up. These service-related uses do not authorize third-party marketing.

Connected Google Business Profile accounts

When you choose Connect Google, Google asks you to authorize Business Profile access. Google’s management scope permits more than read access; ReviewDoctor uses it to read accounts, locations, original reviews and existing replies, and to publish business replies when you explicitly authorize posting. We store encrypted authorization tokens and selected account and location identifiers to maintain your connection. We do not permanently store Google review content, account names or location addresses from these requests. Review content stays in request and dashboard memory. Choosing AI reply posting sends the selected review text and rating to OpenAI as described below. Disconnect in Reviews & replies or Google connections deletes our saved connection (no active subscription required); you can also revoke the app in Google account permissions. Google’s own processing is governed by its policies. Google privacy policy.

Information and purposes

We use account, business, subscription and feedback details to deliver the service. Feedback at a business’s QR station is shared with that business. A business’s own privacy obligations also apply. When configured, a public scan submission stores your name, email, business name and location, selected country, check method and submission time. These are available to the service owner. Without configured security verification, the guided check runs locally and does not submit these inputs.

Marketing is optional, unchecked by default and inactive until email confirmation. Consent records include the wording, purpose, policy version, selected country and timestamps. A one-time report email requires separate permission and confirmation, and uses only the email entered for the check. It does not enroll you in marketing. We use hashed email suppression records to honor opt-outs.

Removal cases store the business owner’s case title, Google review and profile links, stated policy concern, evidence notes and links, case number, manually recorded dates, status history and update timestamps. These records are private to the business workspace and are not automatically submitted to Google. Owners can delete a case in the dashboard. We do not automatically fetch Google review text for this workflow. The optional AI tool uses text pasted by the owner as described below. Keep sensitive personal information out of case notes and public community posts.

Google API information

If live lookup is enabled after licensing review, your business search and location are sent to Google Maps Platform. We store only the selected place ID alongside your own submitted inputs. Ratings, review text, hours, photos, listing addresses and coordinates returned by Places are not saved in our scan database, logs or report drafts. Live responses use no-store caching. Coordinates exist only while the request is processed. Google content is shown during the page session; exports are disabled pending licensing review. Google’s Privacy Policy applies to Google’s processing.

Optional advertising measurement

The dental and restaurant business landing pages provide integration hooks for Google Ads and Meta measurement. These hooks require a separate, unchecked advertising-consent choice, in addition to any first-party analytics permission. Global Privacy Control blocks the hooks. Consent is recorded locally with its version and timestamp and expires after 180 days. You can withdraw it in Privacy choices. The current hooks expose only an allowlisted business industry, fixed landing-page path and signup-button position to a browser data layer and custom event; they do not load an advertising SDK or send an email address, phone number, customer feedback, health details, identifiers or URL query parameters. A signup-button click does not confirm registration or payment. Google and Meta tags are not configured by these hooks; configuring those providers and their processing requires a further privacy and consent review. No claim of active ad attribution is made.

Security, cookies and analytics

Essential session cookies and your privacy choice support the service. A language preference is stored locally in your browser when you choose a language. We may use your browser’s preferred languages as the initial default. Selecting a language does not send customer details to a translation provider. Check-in consent records store the wording shown in the chosen language. Cloudflare Turnstile loads when you start security verification; it processes security signals under Cloudflare’s privacy notice. Abuse counters use keyed hashes of network addresses and email addresses, not raw values. Hosting and API providers may separately process network and request metadata.

Optional first-party conversion analytics record scan started, scan completed, print initiated and signup, with country, timestamp and consent version. They do not use a visitor identifier. Analytics are disabled until you allow them; Reject all declines optional tracking. Privacy settings are always available. Global Privacy Control is treated as refusal of optional analytics. No advertising cookies are included in this scan implementation.

Customer review suggestions

Optional review suggestions are available after choosing Great. Not great offers customer-written private feedback and a direct Google link. AI prepares generic wording using public business information supplied by the owner, including name, business type, location, description and services/topics. If you optionally confirm which services/topics you actually used, those selections are sent to OpenAI with public business context for the requested suggestions. Topic selections remain in page/request memory and are not saved in our application storage. Your selected suggestion and copied text are not sent to OpenAI or saved. Each new visit or regeneration requests fresh AI wording after security verification. New generated wording is not saved in application storage; business context stays in the business workspace until updated or deleted. Older generic templates are no longer used by this feature. Standard suggestions are visibly distinguished from AI suggestions when AI is unavailable. Customers choose text only if it reflects their own experience, choose their rating, and decide whether to post on Google. The app cannot paste or publish for them. AI requests use store:false; provider abuse monitoring retention may still apply. Public owners should include factual business information and no customer or sensitive personal details. Keyed abuse counters expire after one day and are cleaned up when the endpoint is used.

AI and service providers

The guided check and scoring formula do not send scan data to OpenAI. Review reply drafts remain manual. The removal-case AI drafting tool sends only the review text you paste and the owner notes you provide to OpenAI after you explicitly authorize that request. ReviewDoctor does not fetch review text from Google for this tool, save the pasted text to its case database, or log AI request bodies. A generated explanation is saved only when you use it in the case form and save the case. We record timestamped authorization wording, version, country and a keyed email hash; records older than 365 days are cleaned up when this AI endpoint is used. AI request counters expire after one day. Requests use OpenAI’s store:false setting; this is not a promise of zero provider retention. OpenAI may retain content for abuse monitoring under its applicable data controls. Review the OpenAI data controls. You should be authorized to share the content and remove sensitive personal information before generating. Verify AI suggestions, source references and every claim before use. The tool does not create evidence, verify allegations, provide legal advice or submit reports to Google. Subscriptions use Stripe, account authentication uses Supabase, hosting uses Sites/Cloudflare, security verification uses Cloudflare, and configured report or confirmation delivery uses Resend. Optional feedback text messages use Twilio. Business owners should confirm their authority to process customer feedback and reviews.

Staff accounts and invitations

Owners can invite staff by email to access check-ins for an assigned business location. We store invitation and membership details, expiry and acceptance time. Invitations are sent through Resend; sign-in and email verification use the existing Supabase account service. Only the verified invited email can accept. Owners can revoke access, which is checked on every staff request. When a visit is completed we record the completing account email and timestamp with the check-in. Staff cannot use their staff role to access billing, business settings, reviews or private feedback.

Optional loyalty programs

When a business enables loyalty, customers provide their name, phone number and email and agree to enrollment before requesting visit credit. Enrollment does not subscribe customers to marketing, SMS or feedback invitations. We store business-scoped contact hashes, contact information, the enrollment consent wording and timestamps, confirmed visit credits, reward definitions and redemption records including the recording staff account. Contact ownership is not automatically verified. Visit requests require security verification and owner confirmation. A random loyalty-card credential is stored in the customer’s browser; only a keyed hash is stored on the server. Anyone with that credential can access the card’s name, balance and visit status, so customers should keep it private. Owners can see their own program’s enrollment information and manage rewards. Visit and redemption logs expire after one year (365 days); membership and remaining credits expire after one year without loyalty activity. Cleanup runs through the existing follow-up processor and loyalty requests. Turning loyalty off pauses enrollment, credit confirmation and redemption but does not immediately delete records. Request access, correction or deletion through the privacy request form. Loyalty rewards are independent of Google reviews and ratings. Alcohol reward eligibility and local promotion rules must be checked by the business before offering or redeeming them.

Check-in and feedback follow-up

When a business enables check-in, you may choose an available email or SMS channel and provide that contact information, plus an optional name, to receive a feedback invitation. We record your consent wording and version, check-in time, station and follow-up status. The business can see these records in its dashboard. Follow-up timing starts at check-in or when staff marks the visit complete, according to the business setting. Resend processes email delivery. Twilio processes SMS delivery and receives the mobile number, business name, feedback link and message text. SMS consent is separate from email consent; neither is required for receiving service. Message and data rates may apply. If enabled, one reminder follows the invitation; submitting private feedback or opening the Google review link stops the reminder. This does not confirm a posted Google review. Signed links open feedback without another check-in and allow you to unsubscribe from feedback emails for that business. For SMS, reply STOP to block texts from this business’s dedicated ReviewDoctor sender, START to allow future explicitly consented check-ins, or HELP for assistance. START does not restart old invitations. No marketing signup is included. Do not submit medical details, case information or other sensitive personal information. Check-in and check-out records, including contact information, completion timestamps and completing staff accounts, and SMS delivery logs are retained for one year (365 days) from check-in and removed by the follow-up processor after expiry. Authorized owners and assigned staff can view the dated logbook and download CSV records. A visit is included on its check-in and check-out dates; times are displayed in the viewing device’s timezone. Businesses are responsible for securely storing exports and applying their own lawful retention periods. Delivery logs store provider message IDs, status and error codes. Business-scoped email suppression hashes and sender-service-scoped phone suppression hashes are retained to honor opt-outs. Provider retention is governed by its own policies.

Business SMS registration

Business owners who authorize dedicated SMS setup provide their legal business name, registration country and country-specific registration number (US EIN or Canadian BN, provincial number or Québec NEQ), address, website, contact details, policies and consent evidence. Registration details and child-account credentials are encrypted in server storage and submitted to Twilio for verification. We store provider account, service, number and verification identifiers, approval status, provisioning records and cost authorization to run the service and prevent duplicate purchases. Uploaded blank-form consent screenshots are publicly accessible by their review links with the owner’s separate permission; never upload customer information or sensitive details. Registration and evidence are retained for service, verification and support needs; request correction or removal through our privacy request form. Pausing messages does not release a rented number.

AI business replies on Google

When an authorized business owner selects AI reply posting in the signed-in dashboard, we retrieve the selected review on demand and send its text and rating, plus the business name and industry, to OpenAI to generate a public business response. We do not send the reviewer name or profile photo. OpenAI processing follows the data controls linked above. The generated reply is sent to Google only after the owner has authorized public posting. Existing replies are checked again and skipped. A bulk run can be stopped after the current reply; replies already posted remain on Google and can be managed there. Manual bulk replies run from the open dashboard. If a business owner separately enables automatic replies, ReviewDoctor checks the authorized connected location once daily in the background and sends future unanswered review text and ratings to OpenAI before publishing generated business replies. The saved permission applies to all star ratings and reviews created after enabling, can be paused, and is invalidated by a changed location or connection. Existing replies are skipped. We store the authorization wording, version, timestamp and business/location scope, plus last-check status and hashed duplicate-protection receipts without review content. Automatic reply permission and receipts are retained while the account exists, subject to account deletion requests. Pausing stops future posts; a request already sent to Google may still finish. Provider downtime, queues and API limits can delay checks. Review text and generated replies are not permanently stored in ReviewDoctor. We keep timestamped authorization records with a hashed owner/business identifier for up to 365 days, and hashed per-review duplicate-protection records for one day; expiry cleanup occurs on subsequent reply requests. Business owners must confirm their authority to process review content and should check AI replies for accuracy. ReviewDoctor also stores its own reply-publication activity (random operation identifier, business identifier, hashed connected-location identifier, timestamp and confirmation status) for account reporting. These records contain no Google review text, reviewer details, star ratings, review identifiers or reply text, and are subject to account deletion requests. Review analytics are calculated in page memory from live Google responses. Opening a removal case carries the selected review text only in page memory for optional AI drafting; it is not automatically saved as case evidence.

Optional Clover merchant connection

When a business owner explicitly connects Clover, ReviewDoctor exchanges the authorization code with Clover on the server, verifies the authorized merchant, and stores the merchant identifier, name, environment, connection timestamp, authorization record and encrypted access/refresh tokens scoped to the selected business and owner. App secrets are encrypted separately. This connection release does not import Clover customers, orders, sales or payment information, and does not automatically award or redeem loyalty rewards. The owner may remove the saved connection from the Clover connection page; revoke provider permissions separately in Clover. Connection credentials remain until removed or an applicable verified deletion request is completed. Short-lived authorization state expires after ten minutes, is consumed once on callback and is cleaned up on later connection attempts. Clover processes authorization and merchant verification under its own terms and privacy practices.

Guest Wi-Fi portals

When a business enables a supported guest Wi-Fi portal, guests must choose Yes or No for marketing texts and separately accept the business’s guest network terms. Both choices provide the same guest access: a network authorization redirect, or the saved Wi-Fi name and password in QR-to-password mode. Yes records the displayed marketing disclosure and subscribes the submitted name, mobile number and timezone to that business’s marketing audience under our SMS terms. No does not create a marketing contact or revoke a previous subscription; reply STOP to stop existing texts. We record the business, time, choice, disclosure versions and network terms for completed forms. Portal receipts are retained for up to 90 days, with cleanup on later completed submissions or owner Wi-Fi reads. Marketing subscriber records follow the existing one-year retention period. Preview forms save nothing. We do not store device MAC addresses, raw client IP addresses or browsing history in Wi-Fi receipts. Guest Wi-Fi passwords are encrypted in storage and retained until updated or removed through an applicable account deletion request. They are revealed after a Yes or No choice and acceptance of network terms. The QR code contains no password. QR mode does not control router access; guests finish connecting in their device settings. Network providers separately process internet authorization under their own terms. Wi-Fi form completions do not confirm internet connections or physical visits.

AI food illustrations

When a business owner chooses image generation and accepts the processing notice, the selected item name, description and optional presentation details are sent to OpenAI. Prices, customer information and uploaded food photos are not included. Illustrations may differ from the actual dish and require owner review before attaching. Generated previews and request records expire after 24 hours; cleanup runs when that location uses the AI photo endpoint. Approved images are kept in the location’s menu photo library until removed, subject to saved and published menu references. Regenerating makes another paid API request; uncertain requests are not automatically retried. Published illustrations are labeled as AI-generated.

AI menu descriptions

With the owner’s explicit processing consent, selected menu item names, categories, existing descriptions and optional verified ingredient or preparation details are sent to OpenAI to suggest short descriptions. Prices, photos and customer information are not included. We request response storage to be disabled; provider processing policies still apply. Suggestions require owner review and are not automatically published. Request receipts and suggestions expire after 24 hours and are cleaned when the description endpoint is used; approved descriptions follow normal menu retention.

Visitor badge printing

When the business enables automatic badge printing or staff requests a badge, a paired Windows connector retrieves the visitor name, business name, host label, reception number and visit timestamp. It receives no visitor email, phone or custom answers. Print-job records are retained for up to 30 days and cleaned by connector polling or the follow-up cleanup runner. Windows drivers and the print spooler process the badge locally. The connector stores an encrypted access key for the current Windows user and job receipts without visitor details; acknowledged local receipts are cleaned after 30 days while it runs. Connector keys expire after 90 days and owners can revoke them. Submitted status means spooler submission, not physical printing confirmation.

Visitor reception and preregistration

When a business enables reception, we record visitor contact details, configured basic visit questions, visit type, assigned host or department, arrival and status timestamps, queue number and staff status changes. Authorized owners and assigned staff can view these records and print visitor badges. Reception check-in alone does not subscribe a visitor to messages. The queue-number TV template displays numbers and recorded call instructions, without names, contact details or custom answers. Businesses must not use custom fields for clinical or other sensitive information.

Private preregistration links act as access credentials and expire shortly after the scheduled visit date; owners can revoke them. A visitor may explicitly choose to save contact details for 30 days on a private device. The browser stores a random retrieval token; the service stores its hash and the contact details. Anyone with that device token could retrieve those details. The visitor can forget them from the reception form. Visit records and status history follow the one-year check-in retention rule. Expired preregistration and returning-detail records are removed when reception submissions or the follow-up cleanup runner execute; inactive data can await the next cleanup.

Custom forms and agreements

Businesses can publish custom forms or attach questions to visitor check-in. Submitted contact details and visible answers are stored privately for the business owner; hidden conditional answers are discarded. Forms do not subscribe respondents to marketing. Each response retains its original question version, with downloadable PDF records. A private receipt key allows respondent downloads for seven days; owner records have a one-year retention rule. Required NDAs use the separate electronic-signature workflow and retention rules. Optional form usage analytics record a random session identifier and question progress without answers or contact details, only after analytics consent and subject to Global Privacy Control. These events have a 90-day retention rule. Cleanup runs on subsequent form submissions or owner reads, so inactive storage may await cleanup. Businesses must not request clinical, financial or other sensitive information in these general-purpose forms.

Digital menu analytics

Optional first-party menu measurement runs only after analytics permission and respects Global Privacy Control. It uses a random, in-memory visit ID to count visible item cards, detail opens, category selections, searches, active viewing time, broad device type, browser language preference and labeled QR placement. A visit is not a unique person or a purchase. No contact details, precise location or cross-site identity are collected for this measurement. Only search phrases made entirely of existing public menu vocabulary are retained; other searches are grouped without their text. Menu measurement preferences use session storage and a session cookie. You can turn measurement off on the menu. Business owners see aggregate reports for their own locations. Menu activity has a 180-day deletion rule, with cleanup on measurement writes, owner analytics reads and shared cleanup; inactive storage can await cleanup. QR placement labels remain until the associated business record is removed.

Retention

Scan leads and their submitted business details have a 90-day deletion rule. Unsent guided report drafts and confirmation tokens expire after 48 hours. Abuse counters expire after one day; scan conversion events after 30 days; optional QR analytics and dashboard activity after 90 days; consent evidence after 365 days; resolved privacy requests when their submission is older than 365 days. Unsubscribe tokens are retained to keep opt-out links working; they store hashes and an internal lead ID, not an email address. Suppression hashes are kept to maintain opt-outs. Cleanup runs when scan or privacy endpoints are used, so inactive storage may await the next cleanup. A scheduled cleanup and provider backup-retention verification are still required before claiming exact deletion deadlines.

Account, business, private feedback and billing retention depends on ongoing service needs, legal obligations and verified deletion requests. Provider backup periods and a final account-retention schedule have not yet been verified. We do not claim immediate erasure of provider backups. Live Google content has no application persistence window.

Your choices and requests

Request access, correction, deletion, restriction, objection, portability or opt-out through the request form or email us. We record a receipt, review applicable rights and verify identity before disclosure or deletion. Marketing opt-outs take effect immediately in our suppression system. Scan lead deletion can be processed by the owner; account, payment and provider records require a separate review. We do not charge for making a request. You may complain to your relevant data protection authority. Legal deadlines and exceptions depend on jurisdiction.

International processing and legal bases

Our operator is in the United States and providers may process information internationally. We apply the same strict default of no optional marketing or analytics without consent in every selected or detected region. Approximate region detection uses the hosting country header and may be inaccurate; you can change the country selector. It is not a legal jurisdiction determination.

Service delivery, security and consent are the intended purposes and bases for processing; the applicable lawful bases, processor contracts, transfer safeguards, sale/sharing classification, representative requirements and local notices must be confirmed by counsel. We have not verified an adequacy decision, standard contractual clauses or other transfer mechanism for every provider. This notice is an operational disclosure, not a certification of compliance with GDPR/UK GDPR, ePrivacy, CASL, PIPEDA, CCPA/CPRA, LGPD, Australian privacy/spam law or India DPDP.

Contact

Valencia Supply LLC DBA ReviewDoctor
6800 Rolling Mill Rd, Baltimore, MD, United States
info@reviewdoctor.com