Privacy Policy

1. Who we are and what this covers

Arub is order, shipping and listing software for people who sell on more than one marketplace at once. It is operated by Arub, Inc., a Florida corporation (“Arub”, “we”, “us”).

This policy covers:

• The public website at arub.com.
• The applications at my.arub.com, ship.arub.com, lm.arub.com and spy.arub.com.
• The Arub REST API, the Arub MCP server and the Arub Print Agent.

Together we call these “the Service”. If you are reading this because a marketplace asked you to, the sections you want are 6, 8, 9, 10 and 16.

2. The two roles we play

This distinction matters, because it decides who you ask when you want something changed or deleted.

We are a controller of your account data

When you sign up, sign in, pay us or email us, we decide how that information is used and we are the data controller for it. Ask us directly about it.

We are a processor of everything you bring in

Your orders, your buyers' names and addresses, your listings, your product photographs and your shipping history are yours. You are the controller and Arub is the processor — or, under California law, your service provider. We act on your instructions and for no other purpose. If a buyer asks us to delete their information, we will point them at you and help you carry it out, because it is not ours to decide.

3. Information we collect

Account and identity

• Name, email address, company name and the name of anyone you invite as a sub-user.
• A one-way hash of your password. We never store, log or transmit the password itself and nobody at Arub can read it.
• Sign-in records: IP address, timestamp and the app you last used, so you can see who has been in the account and we can spot a login that should not have happened.
• Your permission settings, and any support correspondence you send us.

Billing

• Billing contact details and a record of what you were charged and when.
• We do not store card numbers. Card details go directly to our payment processors, who hold them under PCI DSS. What comes back to us is a token, the last four digits and an expiry date, which is enough to show you which card is on file and to charge it again when you ask us to.

Marketplace and carrier credentials

• OAuth tokens and, where a marketplace or carrier does not offer OAuth, the account numbers or API keys you supply. These are held encrypted and are used only to make the calls the Service exists to make.
• You can revoke any of them from inside the app, or from the marketplace's own settings, at any time. Revoking stops the connection immediately.

Technical and usage

• Server logs: IP address, browser user agent, the page or endpoint requested and the response, kept for security and troubleshooting.
• Error and job records — what failed, when and with which message from the marketplace or carrier — so failures can be shown to you in plain language and retried.
• API request records for keys you issue, so you can see what your own integrations are doing.

4. Marketplace order and buyer data

This is the sensitive part, so it gets its own section.

When you connect a shop, Arub imports what it needs to ship and to list. Depending on the marketplace, that includes:

• Buyer personal information — name, shipping address, email address and telephone number, where the marketplace supplies it.
• Order contents — line items, quantities, prices, discounts, gift messages, buyer notes and personalisation text or artwork.
• Fulfilment data — the label you bought, its tracking number, the carrier, the cost and the delivery events reported back.
• Listing data — titles, descriptions, tags, attributes, variations, prices, quantities and product photographs.

Buyer personal information is used for exactly three things: producing an accurate shipping label and customs paperwork, showing you the order so you can pack it, and sending the shipping notifications you configured under your own name. It is not used for anything else, ever.

Each account gets its own database. Your rows do not sit in a shared table beside another seller's. Images and labels live in object storage and are served through signed, non-guessable addresses that expire. One customer's data is never combined with another's, and never used to inform anything shown to another customer.

5. How we use information

• To run the Service — import orders, rate and buy postage, print documents, push tracking back to the marketplace, manage and publish listings.
• To keep it working — diagnose failures, monitor queues and jobs, prevent abuse and secure accounts.
• To bill you — charge for postage, prepaid credit and, when the beta ends, subscription fees.
• To talk to you — service notices, security alerts and answers to things you ask. Product news only if you asked for it, and there is an unsubscribe link on it.
• To meet legal obligations — tax records, and responding to lawful requests.

Where the law asks us to name a lawful basis: performance of our contract with you, our legitimate interest in keeping the Service secure and working, compliance with legal obligations, and your consent where consent is what applies.

6. What we never do

Stated plainly, because vagueness here is how policies become useless:

• We do not sell, rent, licence or trade personal information. Not buyer data, not seller data, not to anybody, for any price. We have never done it and the Service has no mechanism for doing it.
• We do not use buyer personal information for advertising, marketing, retargeting, profiling or lead generation, ours or anyone else's.
• We do not contact your buyers on our own behalf. The only messages that leave Arub go out under your name, from your address, with your branding, because you switched them on.
• We do not share one customer's data with another customer, and we do not aggregate marketplace data across customers into benchmarks, market reports or trend products.
• We do not use your marketplace data, listings or images to train artificial intelligence models — ours or a third party's. See section 7.
• We do not place advertising trackers, third-party analytics beacons or advertising cookies in the applications.
• We do not use marketplace data for any purpose other than fulfilling the order or managing the listing it belongs to.

7. Arub AI

Arub AI writes listing titles, descriptions, bullet points, tags, attributes and alt text, and generates or edits product imagery. It is optional, it runs only when you press a button or queue a job, and it is billed from prepaid credit so you can always see what it cost.

How it handles data:

• Buyer personal information is never sent to Arub AI. Not names, not addresses, not emails, not gift messages, not personalisation text supplied by a buyer. The listing side of Arub and the order side are separate, and this boundary is enforced in the code, not by policy alone.
• What is sent is listing content you own: your product photographs, your existing titles and descriptions, your category and attributes, and any instruction you typed into the box yourself.
• Arub AI is delivered using specialist third-party model providers operating under commercial agreements. Under those agreements your content is not used to train their models and is not retained beyond what is needed to return the result.
• Every request carries an explicit instruction not to use or return cached content, so the result reflects what you sent this time.
• You own the output and you are responsible for reviewing it before it goes on a marketplace. Generated copy and imagery can be wrong, can misdescribe a product and can breach a marketplace's listing policy or somebody's intellectual property. Arub does not warrant otherwise. See the Terms.

8. Who else processes your data

We keep the list short on purpose. Each of these is bound by a written agreement limiting them to processing on our instruction, and none of them is permitted to use your data for their own purposes.

Sub-processors

Who	What they do	What reaches them
Infrastructure and hosting	Runs the servers and databases the Service is built on.	All Service data, encrypted at rest.
Wasabi	Object storage for product images, generated imagery, shipping labels and documents.	Images and label files. Served only through signed, expiring links.
SendGrid	Delivers transactional email — your buyer notifications, our service notices, password resets.	Recipient email address and message content.
Authorize.Net and PayPal	Process payments and hold cards on file.	Billing details and card data, direct to them. We receive a token, never the number.
Marketplaces you connect	Etsy, Amazon, eBay, Walmart, Shopify, TikTok Shop, Temu and any other shop you link.	Whatever you send back: tracking numbers, listing changes, cancellations. Governed by their own terms.
Carriers you use	USPS, UPS, FedEx and, where you use it, Shippo as the USPS provider.	Sender and recipient name, address, telephone, parcel details and customs contents.
Google (Places)	Address autocomplete, when you type into an address box.	The partial address you are typing. Sent through our server so your browser is not identified to Google.
Arub AI providers	Generate listing text and imagery on request.	Listing content and product images only. Never buyer personal information.

We will also disclose information where we are legally required to, where it is necessary to protect the safety or rights of a person, or to a buyer of the business in a merger or acquisition — in which case this policy travels with the data and you will be told before anything changes.

9. How we protect it

• In transit. Everything moves over TLS 1.2 or better. Plain HTTP is redirected, and HTTP Strict Transport Security is enforced.
• At rest. Databases, backups and object storage are encrypted at rest with AES-256 or equivalent. Marketplace and carrier credentials are encrypted with a separate application key on top of that.
• Isolation. Every customer account has its own database. There is no shared row space to leak across.
• Access control. Access to production systems is limited to the small number of people who need it, on the principle of least privilege, over authenticated channels. Passwords are stored only as one-way hashes. A password set for you by anybody else is temporary and must be changed on first sign-in.
• Granular permissions. You decide what each person on your team can see and do, down to individual screens and actions, so a packer does not need access to financial reports.
• Signed asset access. Images, labels and documents are not served from guessable URLs. Every link is signed, scoped and time-limited.
• Logging and monitoring. Access, background jobs and API calls are logged. Sign-in activity is visible to you inside the app.
• No personal information on personal devices. Buyer personal information is not stored on removable media, personal machines or in public code repositories, and is not permitted in support tickets or screenshots.
• Incident response. We maintain a written incident response plan. If we discover a breach affecting your data, we will notify you and the affected marketplace within 24 hours of confirming it, and follow up with what happened, what was affected and what we did.

No system is perfect and anyone who tells you otherwise is selling something. If you believe you have found a vulnerability, write to security@arub.com and we will take it seriously and answer you.

10. How long we keep it

Retention

What	How long
Buyer personal information	No more than 30 days after the order is fulfilled, unless we are legally required to keep it, and then only the minimum the law asks for. Tax and financial records are kept for seven years and hold the order reference, dates and amounts — not the buyer's name, address, email or telephone number.
Order and shipping history	For as long as your account is open, so your reports and history stay whole. Buyer personal information inside it is removed on the schedule above.
Listing data and images	For as long as your account is open, or until you delete them.
Account and billing records	For the life of the account, then as long as tax and accounting law requires.
Server and access logs	Up to 12 months, then deleted.
Marketplace and carrier credentials	Deleted immediately when you disconnect the account or close your Arub account.
After you close your account	Live data is deleted within 30 days of your request. Backups roll off within 90 days. After that it is gone and we cannot get it back for you, so take your export first.

11. Where it is held

Arub is operated from North America and your data is processed there. If you are in the European Economic Area, the United Kingdom or Switzerland, that is an international transfer, and we rely on the European Commission's Standard Contractual Clauses and the UK International Data Transfer Addendum, together with the technical measures in section 9, to protect it. Copies of the relevant clauses are available on request.

12. Your rights and choices

Everyone

• Get your data out. Reports export, the API reads everything, and if you are leaving we will produce a full export rather than making you scrape it. You do not need to ask permission and we will not hold it hostage.
• Correct it. Most of it you can edit yourself. Ask us for anything you cannot.
• Delete it. Ask and we will delete your account and its contents, subject only to records the law requires us to keep.
• Disconnect. Revoke any marketplace or carrier connection from inside the app at any time.

If you are in the EEA, the UK or Switzerland

You have the rights to access, rectification, erasure, restriction of processing, data portability and objection, and the right to withdraw consent where processing rests on consent. Write to privacy@arub.com and we will answer within 30 days. You also have the right to complain to your national supervisory authority, though we would rather you gave us the chance to put it right first.

If you are in California

Under the CCPA as amended by the CPRA you have the right to know what we collect and why, to obtain a copy, to correct it, to delete it, and to limit the use of sensitive personal information. We do not sell personal information and we do not share it for cross-context behavioural advertising, so there is nothing for you to opt out of — but you may still ask, and the answer will be the same. We will not discriminate against you for exercising any of these rights. In respect of the data you bring into Arub we act as your service provider and are contractually barred from retaining, using or disclosing it for any purpose other than performing the Service.

Other US state privacy laws

Residents of Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana and other states with comprehensive privacy statutes have equivalent rights, including the right to appeal a refused request. Use the same address and say which state you are in.

13. If you are a buyer, not a seller

If you bought something from a shop that ships through Arub, your details reached us because that seller uses our software. We hold them on the seller's behalf, and we cannot make decisions about them on our own.

Contact the seller you bought from. If you cannot reach them, or you do not know which seller it was, write to privacy@arub.com with the order number or tracking number and we will identify the seller, pass your request on, and make sure it is actioned. We will not use your details for anything other than answering you.

14. Cookies and tracking

There is not much here, which is the point.

• The session cookie. One encrypted cookie holds your sign-in, your CSRF token and any pending on-screen message. It slides forward for 30 days while you keep using the app. Without it you cannot stay signed in.
• Preferences. A small number of your own settings — theme, sidebar layout, rows per page — are stored against your user record or in your browser so the app looks the same on your next visit.
• No advertising cookies. No third-party advertising tags, no retargeting pixels, no cross-site tracking, in the applications or on this website.
• Fonts. This website loads its typefaces from Google Fonts, which means your browser contacts Google to fetch them. That is the only third-party request the marketing site makes.

15. Children's data

Arub is business software and is not directed at children. We do not knowingly collect personal information from anyone under 16. If you believe a child's information has reached us, tell us and we will delete it.

16. Marketplace-specific commitments

Arub connects to marketplaces through their official APIs, under the developer terms each of them publishes. These are the commitments we make to them, and therefore to you.

All marketplaces

• We access only the data needed to provide the features you switched on, using the minimum scopes the marketplace offers.
• We use marketplace data solely to provide the Service to the seller it belongs to.
• We do not resell, redistribute or publish marketplace data, and we do not use it to build competing products or datasets.
• We honour rate limits, back off on errors and never scrape where an API exists.
• Revoking our access from the marketplace's own settings takes effect immediately.
• Arub is an independent product. It is not affiliated with, endorsed, sponsored or certified by Amazon, Etsy, eBay, TikTok, Temu, Shopify or Walmart. All trademarks belong to their owners and are used only to say what we connect to.

Amazon

We handle Amazon data in line with the Amazon Services API Data Protection Policy and the Acceptable Use Policy. Specifically: personally identifiable information is encrypted in transit and at rest; access is restricted, logged and reviewed; PII is retained no longer than 30 days after order fulfilment except where retention is legally required, and then only the minimum; PII is never stored on removable media or personal devices, and never committed to a code repository; PII is not used for any purpose other than fulfilling the order; we do not share Amazon PII with third parties beyond the sub-processors in section 8, each of which is contractually bound; and we will report a security incident affecting Amazon data within 24 hours of confirming it. We maintain a written information security policy, an incident response plan and a data deletion process, and will make them available to Amazon on request.

Etsy

We use the Etsy Open API under Etsy's API Terms of Use. Buyer information from Etsy receipts is used to ship the order and for nothing else. We do not use Etsy data to solicit Etsy buyers, and we do not represent Arub as an Etsy product. Where Etsy withholds a buyer's email address, we work without it rather than trying to obtain it another way.

eBay

We use eBay APIs under the eBay API License Agreement and eBay's Developer Program terms. eBay data is used only to service the seller's own account. It is not aggregated, resold or used for market research.

TikTok Shop

We use the TikTok Shop Partner Center APIs under TikTok's developer terms. Order and buyer data is used solely for fulfilment on the seller's behalf. We do not use TikTok data for advertising, audience building or profiling.

Temu

Temu supplies buyer addresses in masked form and, where the seller is enrolled, an unmasked address for label production. We decrypt an address only to produce the shipping label for that order, we do not retain the decrypted form beyond the 30-day fulfilment window, and we handle Temu data under the data processing agreement that governs that access.

Shopify

We use the Shopify Admin API under Shopify's API Terms of Service and Partner Program Agreement, including its protected customer data requirements. We request the minimum scopes needed, use customer data only to fulfil the merchant's orders, and honour Shopify's mandatory data-erasure webhooks: on a customer redaction request we delete that customer's personal information, and on a shop redaction request we delete the shop's data within the required window.

Walmart

We use the Walmart Marketplace APIs under Walmart's developer terms, on the same basis as the above.

17. Changes to this policy

We will update this page when the product changes or the law does. The date at the top always tells you which version you are reading. If a change materially affects how we handle your data or your buyers' data, we will tell you by email before it takes effect, not afterwards.

18. How to reach us

A person reads these, not a queue.

• Privacy, access and deletion requests — privacy@arub.com
• Security reports — security@arub.com
• Anything else — hello@arub.com

Arub, Inc.
[registered mailing address]
Florida, United States