Privacy Policy — Voltky and the Voltky Chrome Extension

Who runs Voltky: NYBarginHunter LLC
Postal address: 20 South Oaks Blvd, Plainview, NY 11803, United States
Governing law: New York, United States
Effective date: 4 November 2026
Contact: support@voltky.com
Data protection contact: none appointed
Terms of Service: https://app.voltky.com/terms. This policy is part of them.

The term 'Etsy' is a trademark of Etsy, Inc. This Application uses Etsy's API, but is not endorsed or certified by Etsy.

What Voltky is

You have something to sell. Voltky helps you write the listing from photographs and puts it on your own accounts on several marketplaces. When the item sells, Voltky can end its listings for you on eBay and Facebook. On eBay it uses eBay's official API. On Facebook the extension does it, in your own browser, and Voltky gives that job only to a version of the extension that can do it on that marketplace. On Mercari the extension is built to do it too, but Voltky gives that job only to version 9.72 of the extension or newer, and the Chrome Web Store serves 9.67. On Poshmark the extension is built to do it too, and Voltky gives that job to the version of the extension the Chrome Web Store serves, but no take-down there has been proven live yet. Voltky is built to end listings on Etsy too, but no take-down there has been proven live yet. On Etsy that means setting the listing to inactive through Etsy's official API, which you can undo on Etsy. It works only for an Etsy shop you have connected to Voltky. On Depop it cannot: you end those listings yourself.

eBay is two things here, and it is easier to read the rest of this page knowing which is which. eBay is where most of your existing listings and sold history are read from. It is also a place we publish to, when you use the AI listing assistant. Both are true.

Six marketplaces, two different mechanisms. The Chrome extension works on four of them — Facebook Marketplace, Mercari, Poshmark and Depop — by filling their own forms in your own browser. eBay and Etsy are handled by our server through their official APIs, with no extension involved. That is why the extension covers four marketplaces while this page names six. Posting to Etsy is not yet open on Voltky.

The two people this page is about

You, the seller. You made an account and chose to use Voltky. Most of this page is about you.

Your buyer. When one of your eBay items sells, that buyer's name, address and phone number arrive in Voltky so you can print a shipping label. Your buyer never agreed to anything with Voltky. They have their own section, and we keep it separate on purpose.

Your photographs — the whole story, in one place

This is the part of Voltky that surprises people, so it is all here rather than spread across the page.

We keep the original file. When you upload photos to the AI listing assistant, the file is re-encoded and stored on our server, along with the draft it belongs to — your note, the AI's output, and the item details.

The link to each photo is public. Every stored photo has a web address that works for anyone who has it. There is no sign-in check on it. It has to work that way: eBay's servers fetch your photos directly from us when your listing goes live, and eBay has no Voltky account. The only thing protecting the file is a long random code in its address — too long for anyone to guess. But a link that leaks is a link that works.

Outside Bulk ListBot, we keep it after your listing sells, and after your listing ends. Nothing expires. Nothing is cleaned up.

Outside Bulk ListBot, nothing deletes a photo while it is on a draft, and you cannot ask the app to. There is no delete button for other drafts. A photo you take off a draft is deleted from our server once that change is saved. Photos taken off a draft before we added this stay on our server until that draft's photos are next changed, and are deleted then. A photo still on a draft is the plainest example of the "indefinitely" in our retention table.

Bulk ListBot deletes its photos. Photos the AI could not match to an item are deleted as soon as the photos are sorted. Soon after an item is listed on eBay, Voltky asks eBay whether it has its own copy of every photo. If it does, Voltky deletes the photos from our server. If eBay does not have its own copy, Voltky keeps the photos, as it does for other drafts. Listings you never post or change are deleted, with their photos, 30 days after you sent them. While you can open the Bulk ListBot page, you can delete them sooner there.

Why this is not a switch we can simply flip. People ask us to delete photos once the listing is published. We cannot do that as stated, because publishing is not one event. The same stored file is fetched again, from the same public link, every time you later cross-list that item to another marketplace — Facebook, Mercari, Poshmark and Depop each download it at their publish time, which can be days after the eBay listing went up. A photo deleted after the first publish would come back as a broken or missing image on the next one, and that failure is quiet rather than loud. If we build deletion, it has to be keyed on something later than "published" — the last marketplace having fetched the file, a fixed retention window, or your request. Outside Bulk ListBot, we are not promising it here, because it does not exist yet. If it is built, this section and the retention table below change with it.

Your photos are sent to our AI provider twice, or three times with Bulk ListBot. Once when you press Generate — up to five photos plus the note you typed. Then again, automatically, with no button to press: whenever an eBay category is chosen or changed, the first three photos go a second time, along with the draft's title, brand, condition, colour and size. That second one also fires on a draft where you never pressed Generate at all. With Bulk ListBot, a small copy of every photo in the folder goes first, with each photo's file name, so the AI can sort the photos into items.

We have not agreed any restriction with our AI provider about what happens next. Our code sends no instruction to them about retention or training. What they do with the photos after they arrive is governed by their terms, not by ours.

We strip the hidden data out of every photo. The camera make and model, the serial number, the time it was taken and any GPS coordinates are removed before the file is stored, and are not in anything sent to our AI provider. This was tested, not assumed.

Photos you post in Community are seen by other members. They are stripped of hidden data, location included, before they are stored, are shown only to signed-in members, and are deleted with the post, or when we erase your data at your request.

We do not look at what is in the picture. No Voltky code inspects the image content; a Research photo is sent to eBay so that eBay's image search can. If a photo happens to show a room, a face, a document, a packing slip or a shipping label, it is stored and sent exactly like any other image — including, in the case of a label, your buyer's name and address.

Photos you take in Research are the exception: we do not keep them. Each is re-encoded without its hidden data, sent to eBay's image search to find similar listings, and dropped. They never go to our AI provider.

What else we collect from you, and why

Your account. Your email address, and a scrambled version of your password that cannot be turned back into the password. Voltky also keeps a scrambled (one-way) form of the internet address your account was created from, only to limit how many accounts one address can create, and never the address itself.

Your listing content. Titles, descriptions, prices, categories, conditions, sizes, weights and dimensions, plus the eBay inventory and sold history we sync for you.

Your ship-from address. Your name, street, city, state and postal code, as you typed them into Settings. Needed to quote shipping. This one is stored in plain text, not encrypted.

Keys and connections you choose to add. Your eBay tokens, your Etsy tokens, your EasyPost key and your Telegram bot token. These are stored encrypted. When you connect eBay we also keep your eBay username and eBay's identifier for your account, not encrypted, so that eBay's notice that your eBay account closed can be matched to your Voltky account. Everything except eBay is optional, and each one exists only because you connected it.

Your AI connections. If you connect an AI app on your Profile page, such as Claude, Voltky keeps the app's name, the address on the app's own site that Voltky sends you back to after you press Allow, and when you pressed Allow. Voltky never stores the sign-in codes and keys it gives the app, only a scrambled (one-way) form of their secret part. When your AI app renews its key, the new key is worked out from the old one with a secret only our server holds. Voltky also keeps each cross-list request your AI makes: the item, the marketplaces it asked for, and whether you posted it or dismissed it. Voltky gives your AI nothing from Etsy, and your AI cannot ask for an Etsy post. Etsy's rules need Etsy's written OK first.

Billing, if you pay us. Your Stripe customer id, subscription id, status, plan and renewal date. Your card details never reach us — they go straight to Stripe.

A record of the work we do for you. Every cross-listing job the extension runs, and a ledger of AI generations used against your allowance.

Support tickets. When you open a support ticket, Voltky keeps what you write, any screenshots you add, and our replies so we can help you. Screenshots are stripped of hidden data, location included, before they are stored. Only you and Voltky's support can read them. They are erased with the rest of your data if you ask us to erase your account. Screenshots are deleted after the ticket has been closed for 90 days; the written messages stay.

No marketplace login can be saved on our server. Saving one needs a Connect page in Settings to open a browser window on the server's screen, for you to sign in there. The server app.voltky.com runs on has no screen, so that window cannot open and nothing is saved.

Sharing and following on Poshmark run in your own browser. Start sharing, Start following and Start unfollowing, on the Likers & Offers page, run in a Poshmark tab in your own browser, through the extension. No browser on our server is used for them. To follow or unfollow, the extension reads the Poshmark usernames on a followers or following page. Before each click it sends Voltky that username and waits for Voltky's yes. When it is done, it sends the usernames it clicked or skipped, and how each one went. Voltky keeps these usernames, and the activity lines on the Likers & Offers page that name them, so it never clicks the same person twice in one pass and can keep to the daily limit. If you follow the followers of another closet, the closet name you type is kept too. Nothing deletes them by itself. They are erased with the rest of your data if you ask us to erase your account.

If you close your eBay account, Voltky asks you what to do with your eBay data. eBay notifies us automatically when an eBay account closes. Voltky then asks you, on every page, to keep your eBay data or delete it now. It asks only when eBay signed the notice and the notice is about the eBay account you connected. If you do not answer within 30 days, Voltky deletes it. Your eBay data means your eBay connection (its tokens, your eBay username and eBay's identifier for your account) and your eBay listings that were never cross-listed. Your sales history stays, and it holds no buyer details. Your Voltky account and your listings on other marketplaces stay. What we write down about the notice is described under "Other people's information" below.

Server logs

Our server writes a log file. It rotates nightly and is kept for 14 days, then deleted automatically. Each line is also sent to the log stream of Fly.io, the company whose computers Voltky's server runs on, and Fly.io keeps that copy under its own retention. In that window the log can contain:

Notes about what a marketplace form looked like when a fill failed — text read from the page, up to 2,000 characters. Our server blanks what it can recognise as personal before a note is written to the log. A US phone number written with its area code, an email address, a nine-digit ZIP code, and a ZIP code beside the word "zip" or "postal" are blanked where they stand. A street address, a PO box or a state-and-ZIP pair is blanked together with the whole list entry it sits in, because a name usually stands beside an address. So is any entry holding your full name as you gave it to us — on your account, or as your ship-from name — your account's email address, or the street or ZIP code of your ship-from address. Any other run of six or more digits is blanked too, apart from a Mercari or Poshmark listing's own number, Voltky's own job number and a timing in milliseconds. It cannot recognise a name it was never given. A name that is not the one you gave us, one word of a longer name, or a one-word name of three letters or fewer can still appear when it stands by itself on the form. Nor can it recognise a street written without its number, or a five-digit ZIP code with neither a state nor the word "zip" beside it. It knows a street address by how it is written: a number, one to four words, and then a street word such as Street, Avenue or Road. An address that ends in no such word (123 Broadway), one the form cut off before that word, and one whose "way", "place", "court", "drive", "lane", "square", "trail" or "circle" is written without a capital letter can still appear, unless it is the ship-from street you saved with us. So can a state-and-ZIP pair whose state is not in capital letters. A note logged before this redaction existed was written as it was read, and ages out with the rest of the log.
Failed sign-in attempts: the email address that was tried, and the IP address it came from. Successful sign-ins record your user id and IP, but not your email.
An attempted sign-up, if sign-ups are closed at the time — that includes the email address that was tried. Sign-ups are open by default, so this line only appears on a deployment that has closed them.
Progress ticks while a form is being filled, eBay order ids when a label is bought, and Stripe checkout session ids when you buy credits.
The identifier from an eBay account-closure notice (see "Other people's information").
Your own Poshmark closet name, and the numbers of the Voltky accounts that use it, when Voltky confirms the closet is yours.
In one rare case, the Poshmark username of an account the extension clicked without Voltky's yes (see "Other people's information").
For each deal search, the search settings Facebook used for each word, by its place in the list and never the word itself. Never your location.
For each change your AI makes through the AI connection: the name of the action, your account number, the connection's number, and the id numbers of what changed, such as a keyword or a cross-list request. Never what your AI wrote, and never a code or key. The log also notes when you press Allow or Disconnect, and when Voltky ends a connection.

Password reset tokens are no longer written to the log. Only a fingerprint of one is.

Your buyer's address is never written to our logs. That is structural rather than lucky: no code path anywhere sends an order, an address or a shipping destination to the log. The order fetch logs a count and nothing else. The only notes that quote page text come from listing forms, and the ones the extension writes while it fills a Depop, Facebook, Mercari or Poshmark form are redacted as described above before they are logged.

Your IP address

It reaches our log as described above. It also reaches every outside service your browser contacts while a Voltky page is open — see the two tables below. This happens on every page, including the sign-in and sign-up pages — before you have an account at all. There is no cookie or consent banner anywhere in the app.

What Voltky keeps from Etsy

Posting to Etsy is not yet open on Voltky. This section says what Voltky keeps once it is, and you connect your own Etsy shop.

Voltky works for you, as your service provider. For the data from your Etsy shop, Voltky acts on your behalf. It uses that data only to do what you ask in Voltky, such as creating a listing in your shop. It does not sell it, and it does not use it for its own purposes.

Everything goes through Etsy's API. You connect your shop by signing in to Etsy yourself and allowing Voltky. Voltky never sees your Etsy password, the Voltky extension does not work on Etsy, and Voltky does not visit Etsy's website for you.

Until you disconnect, Voltky keeps:

the two keys Etsy gives Voltky to reach your shop, an access token and a refresh token, stored encrypted, and the time the access token expires;
your Etsy shop's id number;
the shipping profile you picked, if your shop has more than one: its id number and its name, so Voltky does not ask each time. Press Change in Settings to forget it;
which of Voltky's Etsy apps made the connection, as a fingerprint of Voltky's own key, and when Etsy last refused to renew it, so Voltky can tell you to reconnect. Neither comes from your shop, and Disconnect erases both.

For each item you post to Etsy, Voltky keeps:

the new Etsy listing's id number and its link;
when it was posted, and whether you marked it ended;
the number of the Etsy category chosen for it. Its name is not kept: Voltky reads it from Etsy's category list whenever it shows it to you.

These are kept with that item in Voltky while your Etsy shop is connected, so Voltky can show you where the item is listed and, when the item sells somewhere else, set that one listing to inactive or remind you to end it. Before it changes a listing, Voltky checks the listing's id against these records, so it changes only the listing this item created. Disconnecting Etsy erases them.

Voltky keeps nothing about your buyers. It does not read your Etsy orders, receipts or anything about the people who buy from you.

What Voltky reads and does not keep. When you post an item, Voltky reads your shop's shipping, processing and return settings, and whether your shop is on vacation. They are used for that post and not saved, apart from the shipping profile you pick. When Voltky ends a listing for you, it reads only whether your shop is on vacation, and it changes only the listing's state, to inactive. Your answers to Etsy's questions about who made the item, when it was made and whether it is a craft supply are sent to Etsy and not saved. Your photos are fetched from where the item already lives, sent to Etsy and not stored again.

How fresh Etsy's own data is. Voltky reuses Etsy's category list for up to an hour, and a category's attributes for up to six hours, before reading them from Etsy again. Both are held in our server's memory, not in the database.

In the server log. The log, described under "Server logs" above, can hold an Etsy listing's id, the text of an error Etsy sent back, the id numbers of the attributes Voltky set on a listing and of the values Etsy stored for them, and a note that you confirmed you made an item. That note says only that you confirmed, not what you answered.

Disconnecting Etsy

Press Disconnect Etsy in Settings. Voltky then erases both tokens, their expiry time and your shop's id, forgets the shipping profile you picked, and makes no more calls to your shop. It also erases its record of each listing it made for you: the listing's id, its link, when it was posted, whether you marked it ended, and its category. Voltky then no longer shows those items as listed on Etsy, sets them to inactive, or reminds you to end them when they sell. Your listings on Etsy stay on Etsy.

Disconnect does not tell Etsy. To remove Voltky's access on Etsy's side too, remove it in your Etsy account settings.

If your Etsy data is exposed

If we find that someone who should not have it has got hold of data Voltky holds from your Etsy shop, we will tell you and Etsy within 24 hours of finding out. A person will write to your Voltky account's email address from support@voltky.com.

Your buyer's information

If you are a buyer and you found this page: this section is for you. You bought something from a seller who uses Voltky. You never agreed to anything with us, so here is what happens to your details, in plain terms, and what you can do.

What arrives, and when

When we sync a seller's eBay orders, eBay returns for each order: the buyer's eBay username, and their name, street address, city, state, postal code, country and phone number. We do not ask eBay for a reduced version — eBay's order call returns the whole block.

This is not limited to the moment a seller opens their Orders page. A background sync that runs with nobody present also receives the full block, as does the analytics call that reads order totals. Neither of those two reads the buyer's fields, but both receive them.

Where it is kept

Nothing eBay sends us about a buyer is written to our database. We checked every column of every table in both of our databases for anything buyer-shaped — name, address, street, recipient, phone, postal code, ZIP, city. There are none. The shipping-label records we do keep hold a cost and an order id, with no name, no address, no tracking number and no label link.

Your order details are held in our server's memory only, and never written to our database or our logs. That is structural rather than lucky: no code path anywhere passes an order, an address or a shipping destination to a log file.

There is no timer on it. It is dropped when the server restarts, or when that seller's orders are fetched again — and a re-fetch simply replaces it with a fresh copy of the same address. eBay returns every paid, unshipped order from the last 60 days, so an unshipped order's buyer stays in memory for as long as our server keeps running. Our server is not restarted on a schedule.

It is also dropped when a label purchase completes and eBay accepts the tracking number, which normally happens moments after the seller buys the label. If that last step fails — eBay errors, or the shipping provider returns no tracking code — it stays in memory like any other cached order.

One exception you should know about, because it is the same thing by another route: a photo a seller uploads can incidentally show a packing slip or a shipping label with a buyer's name and address on it. We do not look at what is in a photo. Those files are kept indefinitely unless the seller takes the photo off its draft (the photographs section above says when that deletes it), are reachable by anyone who has the link, and are sent to our AI provider. See the photographs section above.

Where it goes

We have tried to make this list complete. If you find something that reaches a party not named here, that is a bug in this page and we want to hear about it.

To the seller's own browser, so they can see who to ship to. The address travels both ways — from our server to their browser when the Orders page loads, and back to our server when they ask for shipping rates or buy a label.
Through Fly.io. Voltky's server runs on Fly.io's computers, and every request to the app, in both directions, passes through Fly.io's network on its way to our server. That includes the ones carrying the address, and the memory the address is held in.
To EasyPost, the shipping-label provider, when the seller presses Get Rates or Buy: name, street, city, state, postal code and country, along with the seller's ship-from address and the parcel's weight and size. This only happens if that seller has saved their own EasyPost key — Voltky has no EasyPost account of its own.
To eBay, automatically, right after a label is bought: the eBay order id, the tracking number and the carrier, so the order is marked shipped. No setting turns this off.

Your details are not sent to our AI provider. None of the places where Voltky calls an AI model carries order data, an address or a phone number. The only way a buyer's details could reach it is inside a seller's photograph, as described above.

What we hold back

The phone number is never forwarded to a shipping provider. To be exact: we do receive it from eBay, and we do show it to the seller on their Orders page. Both label paths leave it out of what they send, and the seller's browser does not even include it in the request.

After it leaves us

Once an address is at EasyPost or at eBay, it is held under their policies and their retention periods. We cannot recall it or delete it there.

The purchased label is a further step: Voltky opens the label document directly from the shipping provider's own file host in a new browser tab. That document carries the buyer's name and full address. We do not store that link, do not sit in front of it, and cannot expire or revoke it. Anyone who gets hold of the link can open the label. Sellers: do not share it.

Two smaller points

Mercari and Poshmark order cards carry no buyer identity at all. Those cards are built on our side with an empty buyer name and an empty address, by design. Separately, the extension does visit a seller's own Mercari order-status pages — which are pages about a transaction with a buyer — but it takes only two things from them: the time the item sold and the price it sold for.

A second shipping route exists in the code but is switched off. eBay's own logistics service would receive the buyer's full name and address. It is disabled and has never been used: zero labels of that kind exist in either database.

If you are a buyer and you want something done

Your order details are not stored on disk anywhere in Voltky — no name, no address, no phone number in any database or log file of ours — so on the order itself there is nothing for us to delete. The order record lives with your seller and with eBay, and they are the faster route for anything you need. Two narrow exceptions are described above and we are not going to bury them: a seller's photograph can incidentally show your address, and if you close your eBay account we log an identifier for 14 days.
If you want to ask us anyway, write to support@voltky.com. A person reads it. We send no automatic replies.

Who is responsible for what. The seller decides to sell the item, decides to buy a label, and decides which shipping provider to use. On their buyer's order data they are the controller; Voltky handles it on their instruction and for no purpose of its own.

Other people's information

eBay account-closure notices. eBay sends us an automatic notice whenever an eBay account is closed. These are about any eBay account holder — usually people who have no relationship with Voltky at all, including buyers. What we write down is a shortened form of eBay's own identifier for that person, in the clear, plus a scrambled form of their username. It sits in our log for 14 days. We ignore a notice that eBay did not sign. If we cannot check its signature at that moment, we ask eBay to send it again. If the closed eBay account is one a seller connected to Voltky, the log line also names that seller's Voltky account. That seller is then asked in the app to keep their eBay data or delete it now.

Poshmark usernames. When a seller follows or unfollows on Poshmark through Voltky, the extension sends Voltky the Poshmark usernames of the people it clicked, or was about to click. These are other Poshmark members, who have no relationship with Voltky. Voltky keeps only their usernames, with that seller's account, and the name of any closet whose followers the seller chose to follow. Nothing deletes them by itself. They are erased with the rest of that seller's data if the seller asks us to erase their account. In one rare case, a click Voltky had not said yes to, the server log also holds that username, as described under "Server logs" above.

Everyone who receives data

Two separate things happen, and mixing them up is the usual way a list like this goes wrong. Some data leaves your browser as you use the app. Other data leaves our server. Both are below.

Contacted by your own browser

Who	What reaches them	When	Can you avoid it?
Fly.io, where Voltky's server runs	Every request between your browser and our server passes through Fly.io's network, and our server, database, photos and logs are on Fly.io's computers. Everything you send us reaches them	Every page, every action	No
jsDelivr and Google Fonts	Your IP address, browser user-agent and the page you are on	Every page load, including the signed-out sign-in and sign-up pages, before you have an account	Not unless we host those files ourselves. There is no consent banner. The home page at `/`, the `/privacy` page, the `/terms` page and the `/refunds` page are the four pages that load neither
Google Analytics	The page you visited, where your visit came from (including any campaign tags in the link), your browser and your rough location. It also sets its own cookies in your browser	On voltky.com and on the sign-in and sign-up pages, while Voltky has Google Analytics switched on. Nothing from inside the app after you sign in is sent to it	Yes. Install Google's opt-out add-on (tools.google.com/dlpage/gaoptout), or use a blocker that stops Google Analytics
eBay's image host (`i.ebayimg.com`)	Your IP address, browser user-agent and the page you are on, once per photo shown	Every time you open Inventory or Orders — your listing photos are loaded straight from eBay, not copied through us; and when Research shows you listings to pick from — those are other sellers' photos, loaded with no referrer, so eBay learns your IP address and browser but not the page	No. Your inventory is the core of the product. Research's photos, yes — typing a name shows no listings to pick from
Poshmark's image host (`di2ponv0v5otw.cloudfront.net`)	The same	The same, for items you imported from Poshmark	No
Mercari's and Depop's image hosts (`u-mercari-images.mercdn.net`, `media-photos.depop.com`)	The same	The same, for items you imported from Mercari or Depop	No
Facebook, Mercari, Poshmark, Depop	Your listing, typed into their own forms by the extension, in the sessions you are already signed in to	You cross-list to that marketplace	Yes — per marketplace
Facebook (from your own browser)	Your search words, your search distance and your top price, sent by your own browser while you are signed in to Facebook	You turn on the deal scanner (Pro)	Yes — scanner only

At the time of the audit, the inventory table held 6,153 photo links pointing at eBay's image host and 280 pointing at Poshmark's. Loading a page of your inventory contacts those hosts once per photo shown. They therefore learn your IP address, your browser, and which Voltky page you were on when it happened.

Contacted by our server

Who	What reaches them	When	Can you avoid it?
Anthropic	A small copy of every photo in the folder you picked, with each photo's file name	You press Start on the Bulk ListBot page	Yes. Only Bulk ListBot does this.
Anthropic (our AI provider)	Up to 5 of your photos, plus the note you typed	You press Generate on the AI listing page. With Bulk ListBot: in the background after you press Start, for each item.	Yes — the hand-filled listing page sends nothing to the AI for a listing you write there
Anthropic	The first 3 of the same photos, plus the draft's title, brand, condition, colour and size	Automatically, when an eBay category is chosen — there is no button. Again on every category change, and even for a draft where Generate was never pressed	Only by not using the AI listing page
Anthropic	Your listing title, its eBay category and its item specifics. No photos	Working out the matching category on another marketplace, when we have not seen that category before	Partly. On the inventory cross-list screens it is automatic and cannot be declined. On the AI listing page it is automatic too, but only for a draft that has already used one of your AI listings, and at most twice per marketplace for that draft. The hand-filled listing page does not ask the AI for a listing you write there
Stripe	Your account email or stored Stripe customer id, your Voltky user id, and which plan you picked. No card data passes through us	You press Subscribe, Buy credits, or Manage subscription	Yes — every account starts on Free and never touches Stripe
Google Workspace (our email provider)	Your account's email address and a one-time password-reset link, which expires after one hour. Sent from support@voltky.com	When a password reset is requested for your address on the Forgot password page — normally by you, but the page does not require you to be signed in, so anyone who knows your address can request one	Not entirely. The email only ever goes to your own address, and the link does nothing unless it is opened from your inbox within the hour. A request you did not make does not change your password
EasyPost	Your buyer's name and street address, your ship-from address, and the parcel's weight and size — authenticated with your own EasyPost key	You press Get Rates, then Buy	Yes, for you — nothing happens unless you save an EasyPost key. Your buyer cannot avoid it
eBay	Your listing content and your eBay token, for publishing, revising, ending and syncing. After a label purchase, the order id, tracking number and carrier	Using Voltky at all	No — this is what the product is
eBay (search, categories, finances)	Search keywords, a free-text category query, or a date range	The deal scanner (only when price checks are on), the category picker, expense reconciliation	Search and finances are optional; the category lookup is not
eBay (Research)	Photos you take in Research are sent to eBay's image search to find similar listings. Voltky does not store them. Their hidden data — location, camera, time — is removed first. Also the barcode number you scan or type, and the search words you look up	You take a photo, scan or type a barcode, or look up the numbers in Research	Yes — Research is optional, and typing a name sends no photo
Etsy	Your Etsy tokens, your listing content, and the raw image files of up to 10 photos	You connect Etsy and post an item. Posting to Etsy is not yet open on Voltky	Yes, entirely — opt-in
eBay's, Poshmark's and Depop's image hosts	A request from our server for each of your own photos, with no cookies attached, so the file can be forwarded to Etsy	Each Etsy push. (Separately from the browser-side loads in the table above)	With the Etsy lane
Poshmark's and Mercari's image hosts	A request from our server for each photo of an item you imported from Poshmark or Mercari, with no cookies attached, so the extension can download it from us	You cross-list that item to another marketplace	Not if you cross-list that item
OpenStreetMap's address lookup service	Your postal code	Setting up the deal scanner's location	Yes — deal scanner only
The AI app you connect (for example Claude)	What your AI asks for: your listings and where each is live, ended or sold; your sales, with no buyer details; your cross-list requests; and whether a deal search is running, how many searches are left, and whether your browser is open. Also your deal-scanner keywords, prices and finds, but not while the deal scanner is hidden. Nothing from Etsy	Only after you connect it on your Profile page, and only when your AI asks. Your AI can also add or remove keywords, turn them on or off, set or clear their prices, start a deal search and mark finds right or wrong, but not while the deal scanner is hidden. It can stop a deal search at any time. It can ask to cross-list an item. Nothing is posted until you press Post in Voltky	Yes: do not connect one, or press Disconnect

The Chrome extension

The extension does the cross-listing work in your own browser, using the marketplace sessions you are already signed in to. It signs into nothing and never handles a marketplace password.

Permissions it asks for

Versions before 9.71 ask for three; 9.71 and later ask for a fourth:

tabs — to open a marketplace tab, bring it to the front for the moments a page will not accept typing while hidden, put you back on the tab you were on, and close it when the job is done.
storage — to hold the listing while it is being published and the result afterwards. A marketplace page's own security rules block the extension from reporting to us directly, and a successful publish navigates the page away before any request in flight can finish. See below for exactly what is held, and for how long.
alarms — two repeating alarms, thirty seconds apart: one checks Voltky for queued work, the other re-sends a publish report our server refused. Chrome shuts down an idle extension, and an alarm is what wakes it. If you are not signed in to Voltky, the check returns immediately and no request is made.
scripting — from version 9.71. To run one function, shipped inside the extension, on your own Facebook Selling page (www.facebook.com/marketplace/you/selling) in a background tab the extension opened itself. It asks Facebook for your Available list, and for your Sold list searched by the first words of your own item's title, with the same requests that page makes when you scroll or search it. It also runs one function on the Facebook page where Voltky posts your item, in the tab it opened. It watches for Facebook's answer to Publish and keeps only your new listing's number, so Voltky can save the link for you. If Facebook opens a new page after Publish, the extension keeps that number in memory for the new page (see "What it stores" below). From version 9.73 it also runs one function on your own Poshmark sales page (poshmark.com/seller-hub/sales), in a background tab the extension opened itself, to read your orders there. When Voltky posts your item on Poshmark, it also runs one function in that Poshmark tab. It reads only your Poshmark name, so Voltky can find your new listing in your own closet. That name is not sent to us. From 9.74, when the Scanner is on, it also runs one function on the Facebook Marketplace search page for your words. It sends Voltky the listings it finds. Your Facebook sign-in keys never leave the page. It runs on no other page. Facebook's session tokens are used inside those pages and are never read out of them, stored, or sent to us.

Where it runs

On app.voltky.com (our own app), on Facebook Marketplace's create, "you" and item pages, on its search page when the Scanner is on (9.74 and later), on www.mercari.com, poshmark.com and www.depop.com. It also fetches images from i.ebayimg.com (your own eBay photos) and media-photos.depop.com (photos of items you imported from Depop), and reads your shop list from webapi.depop.com, which is Depop's own API.

Its script on our own app runs on every Voltky page — including the Orders page, where your buyer's name, address and phone are on screen. It reads nothing there. That script contains no code that reads the page at all: it checks for a marker tag, records our address, and passes listings through.

What it reads on a marketplace page

The listing form it is filling — the fields, the dropdown and option labels, and a read-back of what actually landed in each one.
Your listing's title and status, so the server can be sure it is acting on the right item before it ends a listing. To confirm a Mercari take-down, the extension re-reads that one listing's page in your signed-in Mercari tab and keeps only its listing number and status. On Depop it keeps only your listing's address, the address the read ended on (another listing's, if Depop redirected it there), the HTTP status Depop answered with, and your listing's own sale status and its title, from the anonymous request at point 3 below; the name and location the page also shows are never taken from it or sent anywhere.
Your new Facebook listing's number, from Facebook's answer when you post. Nothing else in that answer is kept or sent.
Your Facebook Selling page (9.71 and later): which of the listings Voltky cross-listed for you are still on your Available list, and, for one that is not, whether Facebook's own Sold list shows that exact listing sold. Because a listing you relisted on Facebook stays sold under its old number, it also counts how many other listings with the same words are on your Available list. Voltky changes eBay only when Facebook itself says that listing sold. Your other Facebook listings are not sent to us: only that count is.
Facebook Marketplace search results for your words (9.74 and later, only when the Scanner is on): for each listing, its number, title, price, town, delivery, whether it is sold or pending, when it was posted, one photo link, and a coded number for its seller. The seller's name and id are not sent to us. For each word, the search settings Facebook used: sort order, distance, price limits, days back, pickup or shipping, condition and category. Never your location.
Your Poshmark sales page (9.73 and later): for each order, its number, status, title, price, cover photo link, and whether it is a bundle. Voltky uses these to see which of your items sold on Poshmark. Your buyer's name and address and the shipping label stay on the page. They are not sent to us.
Your whole shop, when you ask us to import it. Only version 9.73 or later of the extension is given a Poshmark import. It first reads your Poshmark username from the page, to check the closet is your own. Then the Poshmark importer scrolls your entire closet and reads each live item's id, title, price, size, listing link and image link. The Mercari importer pages through your active listings, then reads each imported listing's own page once, with the anonymous request at point 3 below, for what it says: its title, description, price, photo links, brand, condition, size, category, shipping weight, who pays shipping, box size and when it was last changed. The Depop importer reads your whole product list through Depop's own API. For each live listing it keeps the description, photos, price (and the earlier price, if you reduced it), brand, size, colours, condition, category, quantity, parcel size, who pays shipping, Depop's number for the listing, its age, source, occasion and material tags, and when it was last changed. Depop's photo links include your shop's number, so that number is kept inside them. It does not keep your location, which that list also shows.
Mercari sold dates. It visits your own Mercari order-status pages and takes two things: the time the item sold and the price. Nothing else on those pages is read.
Like counts on your own Mercari and Poshmark listings (9.68 and later), so Voltky can show your listings' likes and send offers to likers when you press Send offers. On Mercari it reads every count at once from your Active listings page, in a tab it opens for that, and keeps only each listing's number and its count. It reads each listing's own page only when that read fails. On Poshmark it takes the count from the anonymous listing request at point 3 below. A Poshmark listing page also carries the names of the people who liked it: those are never sent anywhere.
Poshmark's Make Offer to Likers tool, on your own closet, when you press Send offers for Poshmark listings. It checks the closet is your own, and reads each chosen listing's price and offer price in the tool. It ticks only the listings you chose. It sends Voltky each offer and its listing's price, and waits for Voltky's yes before it presses Submit, once. Then it tells Voltky which listings Poshmark marked Done. Done does not mean the offer was delivered: Poshmark can still skip it.
Your own closet in Poshmark's Share to Followers tool, when you press Start sharing. It checks the closet is your own. It reads each listing's id and title, and Poshmark's count of what was shared. It sends Voltky each listing's id and title before it is shared, and waits for Voltky's yes. Then it sends which ones were shared or skipped, and Poshmark's count. It also sends your own Poshmark name, Poshmark's id for your account, and how many listings it loaded.
The Poshmark usernames on a followers or following page, when you press Start following or Start unfollowing. It reads them on your own following page, or on the followers page of your closet or of the closet you name. It sends Voltky each username it is about to click, then the ones it clicked or skipped. It also sends your own Poshmark name and how many rows it loaded.
Diagnostic notes when a form will not fill. These contain text read from the page, and if your name or address is part of the form's own furniture it can appear in one. The extension sends such a note to Voltky's server as it read it, and our server blanks what it can recognise as personal before writing it to the log — "Server logs" above says exactly what that covers and what it cannot. One Mercari diagnostic, about your own Mercari order pages, is redacted in your browser before it is sent: that redactor blanks anything shaped like an email address, a phone number, a street address, a state-and-ZIP pair, or any run of six or more digits.

What it sends, and where

Everything the extension sends goes to Voltky's own server, except for the marketplace requests listed at points 3 to 9 below. Here is the complete list:

Job checks, claims and results, to Voltky's own server, carrying your Voltky session cookie. With a Selling-page read: the ids of your cross-listed Facebook listings still on your Available list, and, for each cross-listed listing that is not, the id, title and sold/pending flags Facebook's Sold list shows for it, with the count of other listings carrying the same words. With a deal search: the search results listed under "What it reads" above. With a Poshmark share: each listing's id and title before it is shared, then which were shared or skipped, and Poshmark's count. With a Poshmark follow or unfollow: each username before it is clicked, then the ones clicked or skipped. With a Poshmark offer to likers: each offer and its listing's price, which listings Poshmark marked Done, and how many of your own clicks and keys it blocked.
Publish results, to Voltky's own server.
Anonymous, signed-out requests to a public Poshmark, Mercari, Facebook or Depop listing page, to read whether your listing is still live, on Poshmark its like count, and, for a Mercari listing you imported, what it says. These send no cookies.
Your own photos, downloaded from eBay's image host or from Voltky, so they can be uploaded to the new marketplace. For an item you imported from Depop, they come straight from Depop's image host (media-photos.depop.com) instead. That request sends no cookies, but Depop can see which marketplace's page asked for the photo. Anything that is not an image is refused.
Your closet, read from Poshmark's own pages, and, only when a like count is read in a Poshmark tab rather than by the request at point 3, that listing page, read again. These are made from a Poshmark page, so they carry your Poshmark cookies, as any request from a page on poshmark.com does. They go to Poshmark, and to nobody else.
Your Depop shop, when you import it. First your own shop page on www.depop.com, to find your shop's number. That request names your Depop username and carries your Depop cookies, as any request from a page on depop.com does. Then your shop list, read from Depop's own API by that number, which sends no cookies. Older versions of the extension read that list with your Depop cookies and your Depop username instead. Both go to Depop, and to nobody else.
Your Facebook Available and Sold lists, read from your own Facebook Selling page. The Sold-list request, and the Available-list request that counts relisted listings, carry a search made of the first words of your own item's title. When the Scanner is on (9.74 and later), also Facebook Marketplace's search for your words, your search distance and your top price: the search page, and at most one more page of its results. These requests are made from a Facebook page, so they carry your Facebook cookies and that page's own form tokens. They go to Facebook, and to nobody else.
To confirm a Mercari take-down, that one listing's page on mercari.com, read from the Mercari tab that ended it. Mercari only shows a deactivated listing to its seller, so this request is made from a Mercari page and carries your Mercari cookies. Only the listing's number and status are kept from the answer. It goes to Mercari, and to nobody else.
Whether you are signed in to Mercari, Poshmark and Depop, when Voltky's setup page asks: only while Voltky has that check turned on, and only until step 3 is done. The extension opens no tab. It reads each one's sell-form page once, a request that carries your cookies for that marketplace, and keeps only yes, no or not sure for each. A yes marks step 3 done; nothing else from those pages reaches Voltky. Facebook is not checked. It goes to Mercari, Poshmark and Depop, and to nobody else.

How the destination is decided. The address the extension reports to is the address of the Voltky page you last had open, recorded by the extension only while it is running on a Voltky page. It is never taken from a marketplace page. There is no other address in the extension's code. The old developer fallback to your own machine (localhost) was removed on 16 October 2026.

No site can send the extension instructions through Chrome. The extension declares no channel for that, so no web page can reach it through Chrome's messaging system. The one exception is deliberate and narrow: the extension's own script on the Voltky app page accepts messages from that page only, checked against the page's own address, because that is how you press "list this" and the app tells the extension what to do.

Progress updates while a form is being filled. The extension sends Voltky a percentage and a one-line status it wrote itself, such as "Setting the item condition". These are not scraped from the marketplace page. One Mercari update includes a count of your own photos. There is no setting to turn this off. We keep them in memory for an hour, and a shortened copy sits in the server log for 14 days.

One tab address is sent. When a job finishes, the extension reads the address of the tab it opened itself and sends a shortened copy — 160 characters — with the result, so we can say truthfully where the tab ended up rather than guess that a listing died. It reads the address of no other tab. To put you back where you were, it does look up which tab in that window was active before it took over, and uses nothing but that tab's internal number — not its address, not its title, not its contents.

While an offer to likers runs on Poshmark, your own clicks and keys in that tab are blocked (9.69 and later). An offer to likers cannot be taken back, so a stray click or key must not change it. Once the offer run is under way, and until its tab closes, the extension stops your clicks, taps, key presses, pastes, drops and form submits in that Poshmark tab. Its own presses still go through. It counts what it blocked and sends Voltky only that number. In the tab, it also notes the first kind of input it blocked and whether you touched the offer window. Neither is sent. This part of the extension loads on every poshmark.com page, but it does nothing until an offer run turns it on.

What it stores in your browser, and for how long

The extension uses chrome.storage.local, and chrome.storage.session, which is kept in memory only. It holds one key for each Facebook tab you post from in the background: your new Facebook listing's number, until the next Facebook page in that tab sends it to Voltky. If that page never comes, the key is removed when you close that tab or Chrome. No web page can read it. The extension never uses chrome.storage.sync, so nothing it stores leaves your machine through Chrome. chrome.storage.local has fourteen keys in total. These are the ones that matter:

The listing it is about to publish — title, description, price, photo links, a token and a timestamp. For Mercari it also includes the postal code your shipping is quoted from, and — only if you are listing a phone and typed one in — the IMEI of the device you are selling, because Mercari's form requires it for phones. The extension reads no identifier from your computer, your browser or your phone. The extension checks how old one of these is and throws it away when it is stale — five minutes for Mercari and Poshmark, twenty for Depop — but that check only runs the next time you visit that marketplace. If you never go back, the listing stays in your browser's storage indefinitely.
A record of each Facebook publish — one entry per cross-list, holding the date and time. Nothing ever removes these. They build up for as long as the extension is installed.
Which Voltky address you are signed in to. Rewritten on every visit, never removed. No personal data.
The current job, its progress and its result, removed as they are used. One exception: if our server refuses a Poshmark publish report, that report is kept and retried — up to six times over about seventeen minutes, and it survives a browser restart before being dropped.
A short-lived marker while a Poshmark publish is in flight, holding the listing title, your Poshmark name and the ids of same-title listings already in your closet, so we do not publish twice.

There is no button that clears any of this. The extension offers no way to erase its own storage. To remove it, uninstall the extension or clear its storage from Chrome's own settings.

What we do not do

Things we checked in the code, and can show you

No analytics, no telemetry, no crash reporting, no advertising code in the extension or on any page of the app you see once signed in. The one exception is Google Analytics, which voltky.com and the sign-in and sign-up pages can carry (see the table of services your browser contacts above). We searched for every common one by name and found no other.
The extension has no access to your browsing history, your cookies, your downloads, your bookmarks or your network traffic. None of those Chrome interfaces appear anywhere in it. It never records what you type or where your mouse moves. It notices your own clicks and key presses in three places only: on the Facebook tab where it posts your item, the time of your last tap or key press, to tell your move from Facebook's; on Depop's posting page, whether you pressed Post or closed Voltky's note; and on Poshmark, while an offer to likers runs, to block them (see the extension section).
To be exact about cookies, because it is easy to misread: the extension cannot read cookies. Some of its requests do carry cookies that your browser attaches by itself — your Voltky session cookie when it reports to us, your Depop cookies when it reads your own Depop shop page, your Poshmark cookies when it reads a page on poshmark.com from a Poshmark tab (point 5 above), your Facebook cookies when it reads your own Facebook Selling page or searches Facebook Marketplace for your words (point 7 above), your Mercari cookies when it reads back a listing it has just ended on Mercari (point 8 above), and your Mercari, Poshmark and Depop cookies when it checks whether you are signed in (point 9 above). It cannot see the contents of any of them.
Nothing it stores is synced off your machine by Chrome.
Your buyer's address is in no database table and no log file of ours — with one exception we would rather state than let you discover: if it is visible on a label or packing slip in a photo you upload, it is in that photo file like anything else in the frame.
Your buyer's phone number is never forwarded to a shipping provider.
The hidden data in your photos is removed — no GPS, no camera serial, no capture time.

Things we promise

We do not sell your data, and we do not give it to anyone for their own purposes.
We do not use it for credit, lending or insurance decisions.
We use it to run the features you asked for. Note that those features include the deal scanner, which is about buying rather than selling, and which sends your postal code and your search keywords to the services named in the table above.

How long we keep things

What	How long
Server logs	14 days in our log file, then deleted automatically. The copy in Fly.io's log stream is kept under Fly.io's own retention
Buyer names, addresses and phone numbers, as eBay sends them	In server memory only, never on disk. No timer: until the server restarts, until that seller's orders are fetched again, or until a label purchase completes and eBay accepts the tracking number. Two things outlive all of that and we cannot expire either: the label document held at the shipping provider, and a buyer's address that happens to be visible in an uploaded photo
Fill-progress updates	1 hour in memory; 14 days in the log
Depop fill notes	15 minutes in memory; the log copy lives 14 days
Your uploaded photo files	Indefinitely while they are on a draft, except Bulk ListBot photos. A photo taken off a draft is deleted when that change is saved. One taken off before we added this is deleted the next time that draft's photos change. Bulk ListBot photos are deleted once eBay has its own copy, or 30 days after you sent them if the listing was never posted or changed. If eBay does not have its own copy, they are kept like other photos.
Your photo drafts	Indefinitely, except Bulk ListBot drafts. Bulk ListBot drafts that were never posted or changed are deleted after 30 days, or when you delete them on the Bulk ListBot page.
Your support tickets	What you and Voltky's support write: indefinitely. Screenshots are deleted after the ticket has been closed for 90 days
Your listing inventory and sold history	Sold history and active listings: indefinitely. An ended eBay listing is removed from Voltky automatically once it has been ended for at least 90 days with no sale or activity here in that time, unless it was cross-listed, imported from another marketplace or made with AI ListBot; those are kept indefinitely. A listing whose end date Voltky cannot confirm with eBay stays until it can, or until you tell Voltky to keep or remove it. To learn end dates Voltky asks eBay for your ended listings' item numbers, end dates and status. Nothing changes on eBay. A removed listing stays in the database backups until newer copies replace them; its item number is kept with your account's settings as long as that copy, so it can be put back. You can delete an individual item
Your job history	Indefinitely
Your ship-from address (plain text)	Indefinitely
Your eBay, Etsy, EasyPost and Telegram credentials (encrypted)	Indefinitely, unless you disconnect — see below
Your AI connections: the app's name, its return address, and the scrambled forms of its codes and keys	Until you press Disconnect on your Profile page, which deletes it at once. A connection also stops working 90 days after you pressed Allow, 30 days after your AI app last renewed it, or when you change your password or press Sign out everywhere. Its record is deleted later: when your AI app next tries to renew it, or when Voltky clears out old sign-ins, which it does each time an AI app signs up to Voltky
Cross-list requests from your AI	Indefinitely. Nothing deletes them
Each AI app's sign-up with Voltky: a random id and the app's return address, naming no seller	One nobody pressed Allow for is deleted once it is a day old, the next time an AI app signs up. One that was used is kept indefinitely
Poshmark usernames from your follow and unfollow runs, and the activity lines that name them	Indefinitely. Nothing deletes them
Each Etsy listing Voltky made for you: its id, link and category number	While your Etsy shop is connected, with the item it belongs to. Disconnecting Etsy erases it
Your billing and AI-credit records	Indefinitely, including after you cancel, so "Manage billing" keeps working
The scrambled (one-way) form of the internet address your account was created from	Indefinitely, also after your account is erased, because the limit on how many accounts one address can create is for life
The deal scanner's results: the listings it found and its alerts	30 days, then deleted automatically. They stay in the database backups until newer copies replace them
The deal scanner's browser folder on our server	Indefinitely. Nothing removes it. Removable by hand on request. It holds no marketplace login: none can be saved on app.voltky.com
Database backups	Taken once a day by the app itself, and by hand before an update. The newest 14 are kept in the backups folder on our server; older ones are deleted. Copies we take off Fly.io, onto a computer of ours, are kept until we delete them. Separately named snapshots taken before risky changes are never pruned; the oldest are from August 2026 and are on the computer Voltky ran on before it moved to Fly.io. Before each day's removal of ended listings, a copy of the whole database, every account's data, is also taken; up to the newest 30 of those are kept, one for each day something was removed, so not 30 calendar days
Category matches learned from your listings	Indefinitely, and they are shared. See below
What the extension stores in your browser	See the extension section. Two items stay until you uninstall

Where a row says "Indefinitely", it means what it says: there is no timer, no expiry job and no delete button. It does not mean "as long as necessary".

A note about learned categories. When we work out that a particular eBay category matches a particular Mercari or Poshmark category, we remember it. That memory is shared across everyone using Voltky — it has no owner attached — and some entries are AI suggestions nobody has confirmed yet. It holds no personal information: it is category-to-category only. If you asked us to delete your data, this contribution would stay, because there is nothing in it that identifies you to remove.

If you cancel, or stop using Voltky

Cancelling a subscription moves you to the Free plan. It deletes nothing. Your listings, your photos, your drafts, your job history, your ship-from address and your connected credentials all stay exactly as they are, under the retention above, and your billing record is kept so that "Manage billing" keeps working. If you want any of it removed, you have to ask — see the next section.

What you can ask for today, and what we cannot yet do

You can do these yourself, right now:

Disconnect eBay. This erases the stored eBay tokens.
Disconnect Etsy. This erases your Etsy tokens, your shop's id and Voltky's record of the Etsy listings it made for you. To remove Voltky's access on Etsy's side too, remove it in your Etsy account settings.
Disconnect an AI app on your Profile page. Its access ends at once, and Voltky deletes its record of the connection. What your AI already read stays with the company that runs it.
Hand back your own eBay developer credentials by switching to our built-in app, which deletes them and the tokens made with them. This is for eBay only. Etsy has no such option: every Etsy call uses Voltky's own Etsy app key, with your own Etsy sign-in.
Delete an individual inventory item, or an individual shipping cost you entered by hand.
Remove what the extension stored by uninstalling it or clearing its storage in Chrome.

These are not possible today. We would rather say so than promise them:

We do not offer account deletion. There is no delete-my-account button and no code behind one.
We do not offer a data export. There is no download-my-data feature.
Outside Bulk ListBot, we cannot delete a draft, or the photos on one, for you yet. There is no delete path for other drafts. A photo you take off a draft is deleted; the photographs section says when, and why more than that is harder than it sounds.
Blanking a saved key in Settings does not remove it. Your EasyPost key and Telegram token are only overwritten when you type a new value, so an empty box leaves the old value in place. To have one removed today, ask us.
Email to us is handled by a person, not by software. The only email the app sends by itself is a password-reset link, and only when a reset is requested for an account, so nothing acknowledges a message to us automatically.
We cannot revoke a shipping-label link once it has been created.

If you ask us to erase your data, here is exactly what that means today. A person does it by hand, and that is not the same as everything disappearing.

Removed: your account row, your listing and sold-history rows, your photo drafts and the photo files on disk, your ship-from address, your stored credentials, your AI connections and your AI's cross-list requests, your job history (with the Poshmark usernames from your follow and unfollow runs), your billing and credit records, and the deal scanner's browser folder on our server.
Not removed, and we will tell you so rather than imply otherwise: database backups already taken before your request; the 14-day window of server logs, which ages out by itself; the copy of those logs in Fly.io's log stream, kept under Fly.io's own retention; the shared category memory described above, which contains nothing that identifies you; the scrambled form of the internet address your account was created from, which still counts toward the three accounts that address can create; each AI app's sign-up with Voltky, which names no seller; anything already delivered to eBay, Etsy, Stripe, EasyPost, our AI provider or the AI app you connected, which is held under their policies; and anything the extension put in your own browser, which only you can clear.

Changes to this page

If we change what we do with your information, we will change this page. The only email the app sends by itself is a password-reset link, so we will not email you about a change — checking this page is the only way to see one.

How to reach a human

Email support@voltky.com. A person reads it. The product sends only password-reset links, so nothing will reply to you automatically.

How this page was checked

This page was written from a line-by-line audit of Voltky's source code and databases on 18 September 2026 — 143 data flows traced, every claim tied to a specific line of code, and every reassuring sentence handed to someone whose job was to disprove it. Twenty-three were disproved and removed. A second review then raised 70 further objections to the draft of this page — 27 of them blocking — and all 70 were answered before publication: each one either changed the text above, or was checked against the code and found not to apply.

Where this page says "nothing deletes a photo while it is on a draft", that is a description of our code, not a figure of speech. If you find a sentence here that the product does not do, write to us and we will correct it.