Privacy Policy

We collect the following categories of information:

• Account information: name, email address, and authentication details you provide when you sign up or sign in. If you use Google, Apple or Yahoo to sign in, that provider sends us your name (when it shares one), your email address and an account identifier. With Apple you can choose to hide your email, in which case we receive and use an Apple relay address instead. We never receive your Google, Apple or Yahoo password.
• Store and connection data: API credentials, OAuth access and refresh tokens, and webhook identifiers you provide or authorize when connecting a sales channel (Shopify, Etsy, eBay, TikTok Shop, Amazon, PrestaShop, BigCommerce, or Facebook/Instagram) or fulfillment provider (Printify, Printful, Gelato, Gooten, Prodigi). These are stored encrypted at rest and used only to make authorized calls to that channel or provider on your behalf, strictly within the scope of access you grant and that channel's own API terms and developer policies (for example, eBay's API License Agreement and Developer Program Policies). We do not use channel or provider data for any purpose outside operating the Service for you.
• Order and product data: orders, line items, customer names/emails on those orders, product catalog data, and fulfillment status received from your connected channels and providers via API or webhook.
• Self-Fulfillment photos and barcodes: product photos you upload or keep on a product are stored with it and are public, because sales channels display them. Photos you choose to analyze with Scan product are sent for analysis and are not stored by the scan itself. A barcode you scan or type is saved on the product variant you create.
• Routing records: when RitePlaz chooses a fulfillment provider for an order (or you choose one in Compare providers), we record the order, the provider, how it was chosen, the reason and the prices and delivery times compared. These records do not include the buyer's name or address. Your routing settings and rules are also stored.
• Billing information: subscription tier, billing interval, and invoice history. Payment card details are collected and stored directly by our payment processor, Stripe; we do not store full card numbers. If you pay by Zelle or bank transfer we keep the confirmation number and note you submit, with the amount and review result, to confirm your payment. If you pay with PayPal we keep your PayPal subscription id; PayPal holds your PayPal account details. If you installed RitePlaz from the Shopify App Store and your plan is billed through Shopify, we keep the Shopify subscription id and your shop domain; Shopify handles the payment and holds your billing details.
• Usage data: sync logs, sign-in activity, and general product usage needed to operate and troubleshoot the Service.
• IP address, approximate location, and device: when you visit our public pages we record your IP address, the approximate city and country derived from it, the type of device and browser, and the pages you view. When you sign in we record the same details (IP address, approximate city and country, and device) for your account, show them to platform administrators for security and support, and include them in the sign-in notification email we send you so you can spot a sign-in that was not you.
• Referral and creator information: if you register with a creator's promo code (typed in, or filled in from a creator's link), we record which code you used and when. If you join the Creator Program yourself, we also collect your channel details, your chosen promo code, link-visit counts, commission and withdrawal records, and the payout details you provide (see Section 12).

• Operate core features: routing orders between connected sales channels and fulfillment providers, syncing catalog and inventory data, and processing webhooks.
• Choose a fulfillment provider for each order according to the settings and rules you set, and show you how the providers compare.
• Suggest product details when you use Scan product or Scan barcode in Self-Fulfillment, which you review before anything is created.
• Generate the Sales and Billing reports you request, including any CSV/PDF exports and shareable snapshot links you choose to create.
• Process subscription payments and manage your billing tier through Stripe, PayPal or, for merchants who install from the Shopify App Store, Shopify.
• Send transactional emails and in-app notifications (for example order or sync failures, billing receipts, and account security notices).
• Maintain the security, integrity, and reliability of the Service, including detecting fraud or abuse.
• Provide customer support and respond to inquiries.
• Send sign-in notifications that include the time, IP address, approximate location, and device so you can spot unauthorized access.
• Count visitors and understand traffic and sign-ups (for example total registered users, people who visited, and where visitors are located), shown to authorized administrators.
• Attribute sign-ups to the creator whose promo code was used, calculate commissions on subscription payments, and pay creators their withdrawals.
• Send marketing emails to users who are subscribed. Each includes an unsubscribe link, and you will still receive service and security messages.

We do not sell your personal information.

Reports you export or generate a share link for are frozen at the moment of sharing. Anyone with a valid, unexpired share link can view that snapshot without signing in. Share links expire automatically 14 days after creation. You control if and when a share link is created; we do not publish or index shared report links.

We share information with the following categories of third parties, only as needed to provide the Service:

• Sales channels (Shopify, Etsy, Amazon, TikTok Shop, eBay, PrestaShop, BigCommerce, Facebook/Instagram): to retrieve orders and push catalog updates and, for Shopify, Etsy, eBay, BigCommerce, Amazon and TikTok Shop, shipment tracking back (the carrier, tracking number and tracking link, and, when an order ships in more than one package, which items are in each package). The one-time eBay setup address you enter is sent to eBay to create your inventory location and is not stored or logged by RitePlaz. Facebook/Instagram receives catalog, price, and inventory updates only; RitePlaz does not retrieve order data from that channel.
• Fulfillment providers (Printify, Printful, Gelato, Gooten, Prodigi, Walmart Fulfillment Services): to submit orders for production and shipping and receive status and tracking updates. We send the buyer's name, delivery address and phone number and the items ordered. We do not send the buyer's email address to any fulfillment provider: where a provider requires a contact email, we give RitePlaz's own address (info@riteplaz.com), so the provider's messages about the order come to RitePlaz. When live price quotes are switched on, we also send an order's delivery address (and the buyer name where that provider's quote request requires it, but never the buyer's email) to the connected providers being compared, to ask what they would charge. A quote does not create an order.
• Stripe: to process subscription payments (cards, Apple Pay, Google Pay and US bank accounts) and retrieve billing/invoice data shown in Billing reports.
• PayPal: to process subscription payments if you choose to pay with PayPal.
• Shopify Billing: if you installed RitePlaz from the Shopify App Store, to charge your subscription to your Shopify bill and tell us when it starts, changes, is frozen or ends.
• Cloud infrastructure providers (including Google Cloud): to host the application, database, and background jobs that power the Service.
• Google Gemini (Vertex AI): only when you use Scan product in Self-Fulfillment. The photos you choose to analyze are sent to Google to read the product and suggest a title, description and tags. The scan does not store them, and we do not send your account details with them.
• Product databases: only when you use Scan barcode in Self-Fulfillment. The barcode number you scan or type is sent to Open Food Facts (and its sister databases for beauty, pet food and other products) and, when switched on, to UPCitemdb to find the product's details. We do not send your account details with it.
• Email delivery providers: to send transactional emails on our behalf.
• IP location lookup: to estimate a city and country from an IP address, we send that IP address (and nothing else) to a third-party geolocation service when it is not already provided by our hosting network. The result is stored with the visit or sign-in record.
• Sign-in providers (Google, Apple, Yahoo): only when you choose to sign in or sign up with one of them. The provider learns that you signed in to RitePlaz; we receive the profile details described in Section 1.
• Payout services (for example PayPal, your bank, or Zelle): only for creators, and only the details needed to send a withdrawal to the account the creator chose.
• Meta: only when a merchant connects a Facebook/Instagram catalog or turns on the Meta Pixel or Conversions API, as described in Section 11.

Apart from the public product databases, which receive only a barcode number, these providers are contractually restricted from using your data for any purpose other than providing services to us.

Where a connected sales channel requires it, RitePlaz implements that channel's data-deletion and compliance notifications in addition to the general rights described in Section 9:

• eBay Marketplace Account Deletion/Closure Notifications: RitePlaz operates a dedicated endpoint that receives eBay's mandatory notification when a connected eBay seller account is deleted or closed. On receipt, RitePlaz immediately disconnects the matching integration and permanently removes the stored encrypted OAuth credentials for that account. Order and listing history tied to that integration is retained in de-identified form (the connection record is marked disconnected rather than deleted outright) solely so your own sales history and audit trail remain intact, consistent with Section 6's retention practices — no further API calls are made to that eBay account once disconnected.
• Shopify privacy notifications: RitePlaz receives Shopify's three mandatory privacy notifications. When Shopify tells us a customer asked for their data, we tell the store's owners which orders hold it so the merchant can reply. When a customer asks to be erased, we remove that customer's name, email, addresses and phone number from their orders. Forty-eight hours after a merchant uninstalls the RitePlaz app, we remove the buyers' personal details for that store, delete the stored Shopify credentials and mark the connection disconnected.
• Scoped, revocable access: every sales-channel and fulfillment-provider connection uses that platform's own authorization flow (OAuth where available, or a store-issued API key/token otherwise). You can revoke RitePlaz's access at any time both from within RitePlaz (Integrations page) and directly from the channel or provider's own account settings; revoking access on either side stops further API calls immediately.
• Deleting your own catalog data: deleting a product from RitePlaz's Catalog page removes that product, its variants, media, and channel-listing records from our database. This does not automatically delete the corresponding listing on a connected channel (e.g. an active eBay or Etsy listing) — channel listings are managed independently through that channel's own tools, since RitePlaz does not have standing authority to remove a live marketplace listing without an explicit sync action you trigger.

We retain account, order, and billing data for as long as your account is active and for a reasonable period afterward to comply with legal, tax, and accounting obligations, resolve disputes, and enforce our agreements. Report share-link snapshots are retained only until their 14-day expiry, after which they are no longer accessible. Visit records (IP address, approximate location, device, and page) and sign-in details are kept for as long as needed for security, fraud prevention, and traffic analysis, and are deleted or de-identified when no longer needed or when you request deletion of your account as described in Section 9. We keep creator commission and withdrawal records for as long as needed for tax, accounting and dispute purposes. Sync logs (the technical record of each order, product and inventory sync shown on the Sync Logs page) are deleted automatically after 7 days. When you delete a store, we disconnect its sales channels and fulfillment providers and erase the saved access to them at once, keep the store's products, orders and settings for 30 days so you can restore it, and then permanently erase them.

Your customers' personal details are kept for a shorter time. Ninety days after an order is finished (delivered, canceled, refunded or failed), and in any case 180 days after it was placed, we remove the buyer's name, email address, shipping and billing addresses and phone number from the order, from the copy of the order received from the sales channel, and from the copies sent to and received from the fulfillment provider. For orders from Amazon the periods are shorter, as Amazon requires: thirty days after the order is delivered (or canceled, refunded or failed), and in any case sixty days after it was placed. The order number, items, amounts, status and tracking details stay so you keep your sales history and bookkeeping. Raw copies of notifications received from sales channels and providers are deleted after 30 days. Erasure on request or after a Shopify uninstall happens sooner, as described in Section 5. Routing records (the provider chosen, the reason and the prices compared, without buyer details) are kept with the order and erased when the order or store is erased. Providers you send orders to keep order details under their own policies.

We use safeguards designed to protect your information, including encryption in transit (HTTPS), hashed passwords, encryption of the access tokens and keys you give us to connect sales channels and fulfillment providers, access controls on production systems, a managed secret store for platform keys, limits on how often sign-in and other public forms can be tried, and security headers in the browser. Every request for store data is checked against the stores your account belongs to. Administrator access to account and visitor data is limited by role, requires a separate administrator password in addition to a normal sign-in, and administrator actions are recorded in an audit log. Passwords must be at least 12 characters and cannot be a commonly used password. Our database, its backups and the servers that run RitePlaz are hosted on Google Cloud, which encrypts stored data at rest. Platform-level API keys are never shown in full in the administrator interface, and we keep secrets, passwords and full payment details out of our logs.

You help protect your data too: use a strong, unique password, do not share your login, remove team members who no longer need access, and tell us at once if you suspect unauthorized access. No method of transmission or storage is 100% secure, and we cannot guarantee absolute security. If you find a vulnerability, please report it by emailing support@riteplaz.com (we will send you our secure request form) and give us reasonable time to fix it before you disclose it.

We are based in the United States and host the Service on infrastructure that may process data in the United States. If you access the Service from outside the United States, you understand your information will be transferred to and processed in the United States, which may have data-protection laws that differ from those where you live. Where the law requires a transfer mechanism, we rely on the safeguards offered by our service providers, such as standard contractual clauses, and on your consent where it applies.

Depending on where you live, you may have rights to access, correct, export, or delete your personal information, to know the categories of information we collect and disclose, and to object to or restrict certain processing (for example under the GDPR, the UK GDPR, or U.S. state laws such as the California Consumer Privacy Act). You can update account information directly from your profile, disconnect a sales channel or fulfillment provider at any time from Integrations, and request account deactivation from your profile settings. Creators can change or replace their payout details and profile in the Creator dashboard at any time, and a customer who registered with a promo code can ask us to remove that link to the creator.

To exercise a right, email support@riteplaz.com from the address on your account and we will send you our privacy request form. We will need to verify that you are the account holder, and an authorized agent must show your written permission. We aim to respond within 30 days (and in any case within the time the law requires, 45 days under the CCPA, which can be extended once where the law allows). We may keep information we need to meet legal, tax and accounting duties, resolve disputes, prevent fraud and enforce our agreements. If we decline a request you may ask us to reconsider, and you may contact your data-protection authority or state attorney general. We do not discriminate against you for exercising a right.

We do not sell personal information and do not share it for cross-context behavioral advertising. A merchant who turns on the Meta Pixel on their own product pages controls that sharing (see Section 11). Where the GDPR applies, we process personal data to perform our contract with you, for our legitimate interests in running and securing the Service, to meet legal obligations, and with your consent where we ask for it. Orders and customer details you load into RitePlaz belong to you as the merchant; we process them on your behalf, and your own customers should contact you about their rights.

The Service is intended for business use by merchants and is not directed to children under 16, and you must be 18 to create an account. We do not knowingly collect personal information from children. If you believe a child has given us personal information, tell us on the legal requests page and we will delete it.

Merchants who use RitePlaz can have product pages published at addresses beginning with riteplaz.com/s/. These pages show a product's title, description, photos, options, and price to anyone with the link, and send shoppers on to the merchant's own listing on a connected sales channel (such as Shopify, Etsy, eBay, or BigCommerce) to complete a purchase. Purchases are not made on RitePlaz, and any information you give while buying is collected by that sales channel under its own terms and privacy policy.

Merchants can upload product photos in RitePlaz (Self-Fulfillment area). Uploaded photos are stored by RitePlaz in public cloud storage so that sales channels and product pages can display them; anyone with the photo's address can view it. The original file name is not kept. Merchants should upload only images they are content to show publicly.

Merchants can also import products from a CSV file and enter stock counts, a default carrier and a tracking link pattern for their own products. A CSV file is read to create the products and is not kept as a file. Product details and stock counts are kept as part of the merchant's catalog, and stock counts are sent to the merchant's connected sales channels.

If a merchant adds their Meta Pixel ID to RitePlaz, those product pages load Meta's Pixel. The Pixel is loaded only on pages of that merchant's products, and only when the merchant has added a Pixel ID. It sends Meta information about your visit, including the page and product viewed, the selected option and price, whether you select the buy button, and technical identifiers such as your IP address, browser details, and cookies. Meta uses this information to measure visits, to match them to the merchant's Facebook/Instagram catalog, and for advertising and analytics, as described in Meta's Privacy Policy. You can manage how Meta uses this information through your Meta ad preferences and your browser's cookie and tracking controls. RitePlaz does not itself build profiles of shoppers from these pages. We do record each visit's IP address, approximate city and country, device type, and the page viewed, to count visitors and understand traffic, and, like most web services, our hosting infrastructure keeps standard server logs (such as IP address and requested page) for security and troubleshooting.

A merchant can also turn on purchase reporting by giving RitePlaz a Meta Conversions API access token. When it is on, each new order that RitePlaz receives from the merchant's sales channels is reported to Meta as a purchase. The report contains the order number, total, currency, and the products bought, plus the buyer's email address, phone number, name, city, state, postal code, and country from the order. Those buyer details are hashed (SHA-256) on RitePlaz's servers before they are sent, and Meta uses them to match the purchase to its own users and to the merchant's ads. Reporting is off unless the merchant turns it on, and the merchant can turn it off at any time. Orders that come from Amazon or TikTok Shop are never reported to Meta, and their buyer details are never shared with advertising platforms.

Merchants are responsible for providing any notices and obtaining any consent required by law for the use of the Meta Pixel on their products' pages and for reporting their orders to Meta.

Content creators who join the Creator Program give us their name, email address, password (stored only as a hash), the promo code they choose, optional details about their channel, and payout details (method and account information, stored encrypted and used only to pay them). We keep a record of the sign-ups that used their code and of the commissions and withdrawals that result.

When someone registers with a creator's promo code, we record which code they used. The creator's dashboard then shows that person's first name, a partly hidden email address, their plan, whether they are on a trial or subscribed, and the commission earned. The creator never sees their store, orders, or payment details. We count visits to a creator's link, and we set a cookie for up to 60 days that remembers the code so it can be applied when the visitor registers. Payout information is shared only with the payment service used to send the payout.

We use cookies that are necessary to sign you in, keep your session secure and remember preferences such as theme, and a referral cookie if you arrive from a creator link. We record page visits (see Section 1) for security and traffic analysis. Merchants may enable the Meta Pixel on their own public product pages; that is described in Section 11. You can block cookies in your browser, but parts of the Service will not work without the necessary ones.

We keep a written incident response procedure that covers how we detect, contain, investigate and recover from a security incident, who decides and who is told, and a review afterwards to prevent a repeat. If we learn of a breach of security that affects your personal information, we will investigate, take steps to contain it, and notify affected users and authorities where the law requires, without unreasonable delay and by email or through the Service. Laws on breach notice differ by place; our duty is limited to what those laws require.

We may keep and disclose information when we believe it is reasonably necessary to comply with a law, subpoena, court order or other lawful request, to protect the rights, property or safety of our users, the public or ourselves, to investigate fraud, abuse or infringement, or in connection with a merger, financing or sale of our business. We review requests for legality and, where the law allows, we may tell the affected user. Government and legal requests should be sent from an official address to support@riteplaz.com, and we will reply with our legal request form. We keep a record of legal requests and our responses.

RitePlaz LLC, York, Pennsylvania, United States. Email: support@riteplaz.com. Website: riteplaz.com. We may update this Privacy Policy from time to time; material changes will be announced through the Service or by email before they take effect.