Privacy Policy

This Privacy Policy explains how Howdoicomputer, LLC ("Plukio", "we", "us") collects, uses, and shares information when you use Plukio at plukio.com (the "Service"). Plukio is a search and discovery service for independent online shops - for the shops we index, which is nearly all of them, purchases happen on the shops' own websites and we never process payments or receive payment details. A small number of shops sell directly on Plukio ("hosted shops"); their checkout runs here, and the "Payments" section below describes exactly what that means.

Information we collect

Information you give us:

• Account details - your email address, your display name, and the currency you choose to see prices in. We use passwordless sign-in (a magic email link, or Google), so we do not collect or store passwords. If you sign in with Google, Google sends us your email address, your name, and whether Google has verified your email; we do not receive or store your Google password, and we store no Google access credentials. Accounts are optional.
• Favorites and follows - the items and shops you save while signed in.
• Content you create - your messages, reports, and support requests.
• Messages - what you write to a shop or a buyer on Plukio, the item or order a message is about, and when each side read it. The other side sees your display name, never your email address. A message our filter stops because it reads as a threat or as hate is not delivered; we keep its text so a person can review it.
• Message reports - when you report a message or a conversation, the reason and anything you add, and a copy of the conversation as it stood (its latest 50 messages), so the person reviewing it sees what you saw.
• Listing reports - when you report a listing, the reason and anything you add, and a copy of the listing as you saw it (its title, first photo and shop), so the person reviewing it sees what you saw.
• Shop-claim details, if you claim a shop - the verification data needed to confirm you control the shop's domain or site.

Information we collect automatically: log and device data (such as IP address, browser type, and pages viewed); essential session / authentication cookies; outbound-click records - when you follow a "buy" link off Plukio we record which listing was clicked, when, and a session identifier, so shops can see the traffic Plukio sends them and we can understand what's useful (automated/bot clicks are filtered out); search-query records - when you search the catalog we record the query text, the number of results, and the same session identifier, so we can improve relevance and suggest related searches; and listing-view records - when you open a listing's page we record which listing, when, which part of Plukio you came from, and the same session identifier (in the Plukio app, which has no browser session, the view is recorded against your signed-in account instead, or, when you are not signed in, with no account, session or device identifier at all), so we can tell how often a listing was looked at rather than only how often it was clicked through; help-center records - on help.plukio.com we record which help page was opened and the name of the site you came from, what you searched for and how many answers it found, which answer you opened, whether you said an article helped, and whether you went on to contact support, so we can tell which questions our help pages don't answer yet; these records carry no IP address, session identifier or other identifier, and visits from automated tools are left out; and your shopping list - you can build a shopping list without an account, and until you sign in it is stored under that same session identifier: the listings you added, quantities, and any notes you typed. Unlike the three records above, this one is content you deliberately made, so signing in moves it onto your account - that is the point of signing in - and an anonymous list left untouched for 30 days is deleted.

About that third one, plainly: an earlier version of this policy said we kept no server-side history of what you looked at. That is no longer true, and we would rather say so than quietly reword it. Listing views are now recorded, for one reason: without them, "12 people clicked through to your shop" is a number with no denominator, and we cannot tell a shop owner whether their listing was seen and passed over or never seen at all. The record is the listing, the time, the referring part of Plukio, and the session identifier - in the Plukio app, your signed-in account stands in for the session identifier - not a browsing history attached to you, and not shared with anyone. Your recently viewed list, the one you see on Plukio itself, is still kept only in your own browser and is still never sent to us.

What your browser tells us about itself. Alongside each of those three records we now also keep a few things your browser sends with every request it makes anywhere on the web: which browser and operating system it reports, whether that adds up to a phone, a tablet or a desktop, the main language it asks for, and - for the first page of a visit only - the website that sent you here (the site's name, like instagram.com, never the full address and never anything after it, such as what you searched for there). We keep these so we can answer ordinary questions like "how many people reached this shop on a phone", and so a shop owner can see the same for their own listings.

Which advertisement brought you, if one did. We buy advertising in a few places, and when we do, the link in the advertisement carries a short label saying which campaign and which version of the advertisement it was. If you arrive that way, we keep that label alongside the same three records - so we can tell whether an advertisement we paid for actually brought anyone who looked at anything. In our advertisements that label is shared by everyone who clicked the same one, which is what makes it a fact about the advertisement rather than about you. If you did not arrive from one of our advertisements, we record that you did not, which is by far the most common case.

The awkward part of that, said out loud. The label travels in the web address, so anyone can put anything there - including a link built for one person, which would make the label a fact about that person after all. We cannot tell the two apart, so we treat every such label as if it were the second kind: the campaign and version names are kept for administrators only and are never shown to shops. What a shop can see is the network a visit came from - that it was Reddit rather than Instagram - and nothing about which advertisement it was.

And the unflattering half. For a short window we also keep the raw text of what your browser reported about itself, rather than only our tidy summary of it. That text is more identifying than the summary - it can carry version numbers and, on older devices, a model name. We keep it because we decide, from that same text, whether a visit was a person or an automated crawler, and we publish those figures; a decision we cannot check afterwards is a decision nobody should trust. It is kept for 14 days, administrator-only, never shown to shops, and then deleted - much sooner than the records it explains. We do not store your IP address with any of it, which is what keeps this a description of a browser rather than a way to follow a person. We keep IP addresses in only two places: the tax record of an order that includes a download, described under Payments, and the app crash reports described below, where our crash-report provider keeps the address each report was sent from.

One caveat on that deletion, because "deleted" should mean deleted. A short one-way fingerprint computed from that same text - not the text, and not anything we can show you - stays on the record for as long as the record itself does, so we can tell whether two clicks came from the same kind of client without keeping what it said. It is a fingerprint of the browser, not of you: everyone running the same browser version on the same kind of device shares it. We are naming it here rather than leaving it out because it does outlive the text, and a retention promise with an unmentioned exception is not one.

Crash reports from the Plukio app. When the iPhone or Android app crashes, freezes, or runs into an error it was not built to expect, it sends us a report so we can find and fix the fault. A report holds the technical state of the app at that moment: which part of the app's code was running, the app and operating-system versions, the kind of device (its model, and whether it is a phone or a tablet), how much memory and storage were free, the language setting, and a short list of what the app did just before - which screens' requests it made and whether they worked. A report never includes your account, your name, your email address, what you typed, the text of an error message, or anything shown on your screen, and it is not linked to your account. It carries two random identifiers the app makes on the phone: one for the installation and one for that launch of the app, so we can match a report to our own server records from the same launch. Reports go to our crash-report provider, Bugsink, which stores them in the European Union, and the address your phone sent the report from (its IP address) is stored with it.

Indexed shop information: the shop and product content on Plukio (shop names, listings, prices, images) is collected from shops' own public websites - it is published commercial information about shops, not information about you. Shop owners can control or remove it at any time (see plukio.com/bot).

How we use your information

• To operate the Service - search, favorites, follows, and messaging.
• To create and secure your account and sign you in via magic-link email or Google.
• To send transactional messages (such as magic links) and, where permitted, marketing email you can opt out of at any time. Email is delivered through our provider, Lettermint.
• To attribute outbound clicks - showing claimed shops the traffic Plukio sends them, in aggregate.
• To improve discovery - search queries, listing views, and clicks feed aggregate relevance signals (related searches, related items, trending) that never identify you.
• To tell shops how their listings performed - in aggregate, and never as anything resembling an individual's browsing history. Where a figure would be based on too few people to be anonymous, we withhold it rather than show it.
• For trust and safety - preventing fraud, reviewing reported shops, listings and reviews, verifying shop claims, and enforcing our policies.
• To comply with legal obligations.

How we share your information

• With shops you contact, and buyers who contact you: the other side of a conversation sees your display name and your messages, never your email address. Claimed shops see aggregate click statistics, not your identity.
• When you leave for a shop's website: clicking "buy" takes you to the shop's own site, which collects information under its own privacy policy. The link tells the shop the visit came from Plukio; anything you do there (including any purchase) is between you and the shop.
• Service providers: companies that operate the Service for us - Lettermint (email delivery), Cloudflare (network, content delivery, and file storage), and Bugsink (crash reports from the Plukio app, stored in the European Union). They may use your information only to provide services to us. The Service itself runs on hardware we operate, so no third-party hosting provider holds your information.
• If you sign in with Google: Google is your identity provider for that sign-in, so Google necessarily learns that you use Plukio and when you sign in, under Google's own privacy policy. This only happens when you choose Google sign-in - the magic-link option involves no identity provider beyond your own email.
• Advertising networks: Google Ads receive a report when you click through to a merchant, carrying your browser's user agent and their own cookies. This is measurement of advertising we paid for, and it is described in full under "Advertising measurement" below - including what happens to your IP address, and the countries where none of it happens at all. Google Ads also receives a report when you ask us to list your website.
• Legal and safety: when required by law or to protect the rights, property, or safety of Plukio, our users, or the public.
• Business transfers: in connection with a merger, acquisition, or sale of assets.

We do not sell your personal information, and we never have. We do not accept money for your data, and no part of Plukio's revenue comes from passing it on.

Our legal bases (EEA, UK and Switzerland)

If you are in the European Economic Area, the United Kingdom, or Switzerland, we rely on the following bases to process personal data:

• Performance of a contract - operating your account, signing you in, delivering messages you send to shops, and running a maker's Paid plan.
• Legitimate interests - running and securing the Service, measuring what people find useful, attributing outbound clicks to the shops that earned them, and building and maintaining the index itself. We index public storefront and catalog information; where a shop is run by one person, that information can also be personal data, and our interest in operating a search service is balanced against the shop owner's rights by the controls described at plukio.com/bot - including removal on request, without argument.
• Consent - marketing email, where we send it. You can withdraw consent at any time.
• Legal obligation - where the law requires us to keep or produce records, such as the tax records of hosted orders, the tax details of the makers who sell on Plukio, and the records of what makers pay Plukio.

Where we rely on legitimate interests you have the right to object, and for shop information that objection is honored as removal from the index.

Payments

For the shops we index, Plukio has no checkout and processes no payments. Any purchase you make from them happens on the shop's own website under the shop's own payment provider and privacy policy - we never see your payment details.

Hosted shops - the shops that sell directly on Plukio - are the exception. Their checkout runs on Plukio and payment is processed by Stripe: your card details go from your browser to Stripe directly, never touch our servers, and are handled under Stripe's own privacy policy. What we receive and keep is the order itself: the items, the total, and the email address you gave at checkout, because the seller needs them to fulfill your order and we need them to run the Service.

Tax records of each order. Tax laws in many places ask a marketplace to keep evidence of where each sale went, so for every hosted order we also keep: the shipping address and name, if anything ships; the billing address and name you gave at checkout; a business name and tax ID, if you entered one; the country of the bank that issued your card, and the payment method you used; and the approximate location Cloudflare, our network provider, derives from your connection (country, region, city and postal code). For an order that includes a download we also keep the IP address you checked out from, encrypted. We keep them because the law requires it (our legal basis is legal obligation) and use them only for tax: to meet our obligations and to answer a tax authority. Sellers do not see these records. The seller's own Stripe account, where your payment is made, separately holds what you enter on Stripe's checkout page, such as your billing address and any business tax ID. Our records are kept for 10 years from the end of the year of the order, including after you delete your account, and are then deleted.

Tax details of makers who sell on Plukio. Tax laws also ask a marketplace to know who its sellers are. If you sell on Plukio, we keep the tax details you give us: your legal name, your address, the country you operate from, whether you sell as a business, any registration or tax numbers, and that you confirmed them, with the country your connection came from when you registered your shop and when you saved them. We check an EU VAT number with the European Commission's VIES service, which tells us whether it is valid and, where the member state allows it, the name and address registered to it, and we keep that answer. From Stripe we keep what it tells us about your Stripe account: its country and business type, the legal name on it, whether it can receive payouts and what Stripe still needs, and the country, bank, currency and last four digits of your payout account. Our legal basis is legal obligation; we use these details only for tax and to run your shop, and we keep each version you save for 10 years from the end of the year of your shop's last sale, including after you delete your account, and then delete them.

When a maker pays Plukio for the Paid plan or a website listing. Stripe takes the payment on its own checkout page and holds your card details; they never touch our servers. We keep your shop's or your listing's Stripe customer and subscription IDs, the date it is paid through, and whether it renews. For a website listing we also keep which version of our Terms you agreed to when you started it, and when. For each payment we keep the amount and when it was paid, and the name, billing address and any business tax ID you gave at checkout. We check an EU VAT number given there with the European Commission's VIES service and keep its answer. A payment is also a sale Plukio makes to you, so its record notes the country the sale is taxed in, and for the Paid plan the tax details you had saved for your shop that day. We use the IDs and dates to run your plan or listing (our legal basis is performance of a contract) and the payment records for tax (our legal basis is legal obligation). Stripe's messages to us about a payment carry the same details and are emptied after 30 days. The payment records are kept for 10 years from the end of the year of the payment, including after you delete your account, and are then deleted.

Cookies and similar technologies

We set one first-party cookie of our own. It is signed, it is cleared when your browser session ends, and it carries: your sign-in state, if you are signed in; a random session identifier; and four things about the visit that we describe in "Information we collect automatically" above - the country Cloudflare reported, the main language your browser asked for, the site that referred you here, if any, and which of our advertisements brought you, if one did.

That is our cookie, and it is not the only cookie on the page. The advertising networks described under "Advertising measurement" below set cookies of their own, and those are not session cookies - see that section for what they are and how long they last. Everything in the next four paragraphs describes our cookie only.

That list is exact rather than illustrative. Everything in the cookie is either necessary to keep you signed in or is one of the reporting dimensions named above; there is nothing in it we have not described.

We want to be exact about that session identifier, because it is not purely technical. It is the identifier attached to the outbound-click, search, and listing-view records described above, which lets us count distinct sessions instead of raw events - so part of its purpose is measurement, not just keeping the Service working. It is random, it means nothing outside Plukio, and it is not linked to your account unless you are signed in. One deliberate exception: the anonymous shopping list described above is moved onto your account when you sign in, because losing your list at the door would be a strange reward for creating an account. The measurement records are not moved - what you clicked, searched, and viewed before signing in stays under the old identifier, unconnected to you.

Because our cookie is cleared when your browser session ends, we cannot and do not recognize you as a returning visitor. That is a deliberate choice rather than a technical limit: we could make the cookie persist and learn a great deal more about repeat behavior, and we have decided not to. We would rather say plainly that the advertising networks below do not accept that limit and do recognize you across visits, than let our own restraint imply something about theirs.

The advertisement label lives in that same cookie and dies with it, which costs us something we would rather name than hide: if you click one of our advertisements on a Monday and come back on a Thursday, Thursday's visit is not connected to the advertisement, and our own count of what that advertisement did is lower than the truth. We would rather undercount our advertising than keep a cookie that follows you between visits.

Your recently viewed list is stored only in your own browser and never sent to us.

Advertising measurement

We buy advertising, and we run the advertising networks' own measurement code on Plukio so that we can tell which advertisements bring people who actually find something. Today that means Google Ads. This section is generated from the same configuration that decides which code loads, so if this list is wrong the page is broken rather than merely out of date.

An earlier version of this page said the opposite. It said we ran no advertising code on Plukio at all, and that stayed on the page for a short while after the first of these tags went live. We would rather record the correction here than make it quietly.

Concretely, what this means for you:

• They set their own cookies, and those are not session cookies. Google's tag sets cookies beginning _gcl_ and Meta's sets one called _fbp; both typically last around 90 days. They are set and read by those networks under their own policies, not by us, and they are what lets those networks recognize a browser across visits and across other websites - the thing our own cookie deliberately does not do.
• Leaving for a shop is reported to them as a conversion. When you click through to a merchant's site, we tell those networks that a click-out happened. We report it twice by design - once from your browser and once from our server, tagged with the same identifier so the two are counted as one event - because browser reports are frequently blocked and a half-counted signal is worse than an honest one.
• What goes with that report is your browser's user agent and those networks' own cookies, and nothing else about you. Not your name, not your email address, not your account, and not what you were looking at. For the shops we index, Plukio has no checkout and sees no orders, so we could not tell an advertising network what you bought even if we wanted to - we do not know.
• We want to be exact about your IP address, because the two halves differ. The report your browser sends goes directly to those networks, so it carries your IP address the way every request your browser makes to any website does - we cannot prevent that without removing their code entirely. The report our server sends carries no IP address at all. The only IP addresses we keep are the encrypted one in the tax record of an order with a download and the one an app crash report was sent from, and neither is ever sent to anyone for advertising.
• None of this runs if you are in the EEA, the United Kingdom or Switzerland. We suppress every one of these tags, in your browser and on our server alike, for visitors Cloudflare reports from those countries. We do this instead of showing you a consent banner: a banner that we would need to remember your answer to would mean setting a cookie that outlives your session, and we have chosen not to have one of those at all.
• Their code sees the address of the page it is on. That is what any script running in your browser can see, and it means that while you are on a listing's page, its web address - which contains the listing - is visible to them. We do not send it; it is inherent to running their code at all, and it is part of the cost of this decision rather than a detail of it. What our own server sends them contains no page or listing at all: only that a click-out happened.
• Asking us to list your website is reported to Google Ads. When your request to list your website goes in, your browser tells Google Ads that a listing request happened, so we can tell which advertisements bring makers. It carries what your browser's click-out report carries, as described above. Our server sends nothing for it.
• The advertisement label still goes nowhere. Which of our advertisements brought you is recorded in our own session cookie, as described above, and is not sent to anyone.

Your rights and choices

Depending on your state, you may have rights to access, correct, delete, or receive a copy of your personal information, and to opt out of marketing. California residents have rights under the CCPA / CPRA, including the right to know, delete, and correct their information, and to opt out of the "sale" or "sharing" of personal information.

We do not sell personal information. We do "share" it, in the specific sense the CPRA gives that word. Reporting your click-out to an advertising network, with your user agent and that network's own cookies, so that the network can measure and target advertising is cross-context behavioral advertising, and California law calls that sharing whether or not any money changes hands. Naming it is the honest reading; the previous version of this page said we did not do it, which stopped being true when the first tag went live. To opt out, email [email protected] and we will exclude you; we also honor the Global Privacy Control signal where your browser sends one, and if you are in the EEA, the United Kingdom or Switzerland no advertising code runs for you in the first place.

If you are in the EEA, the UK, or Switzerland you also have the right to access your personal data; to have it corrected; to have it erased; to restrict how we process it; to receive it in a portable form; to object to processing we base on legitimate interests; and to withdraw consent where we rely on it, without affecting processing carried out before you withdrew. You may also lodge a complaint with your national data protection authority.

To exercise any of these, email [email protected]. You can unsubscribe from marketing email at any time using the link in those messages. If you run a shop we index, the fastest route is plukio.com/bot, which removes a shop without needing an account or a conversation with us.

Deleting your account

You can delete your account yourself, in the Plukio app (Settings, then Delete account) or on the web at plukio.com/account/delete. One confirmation deletes it right away and signs you out on every device. If you cannot sign in, email [email protected] from the address on the account.

What is deleted: your account and how you sign in; what you saved (favorites, the shops you follow, your collections, your shopping list and your bag); what you looked at and searched for; your settings; and your messages. Messages are deleted on both sides: the shop sees that the account was deleted, and nothing you wrote. If you signed in with Apple, we also ask Apple to revoke Plukio's access to your Apple ID.

What stays: your reviews stay up, shown as from "Deleted account", without your name or photo, so delete any you want gone first. Order records, and their tax records, stay for 10 years from the end of the year of the order, as tax law asks, and are then deleted; anything on its way still arrives. Reports you filed, and site-wide totals like views and clicks, stay without your name. If you run a hosted shop, it closes with your account and your Stripe account stays yours. As tax law asks, the shop's tax details stay for 10 years from the end of the year of its last sale, and the records of what you paid Plukio for the Paid plan stay for 10 years from the end of the year of each payment. If you list a website, its renewal stops and it stays listed until the month you paid for ends; the records of what you paid for it stay for 10 years from the end of the year of each payment.

Data retention

A report's copy of a conversation or of a listing, and the text of a message we did not deliver, are kept while a person reviews them and for 180 days after the review, and are then deleted. The record that a report was made, and what we decided, is kept longer.

We keep your information for as long as your account is active. When you delete your account, we delete your personal information right away, except what "Deleting your account" says stays, and copies in our backups within 30 days. Raw outbound-click records are kept for a limited period (currently around six months) before being reduced to daily aggregates; raw search-query records are kept for about 90 days before being reduced to aggregate search-phrase statistics; raw listing-view records are kept for about 90 days as well, before being reduced to daily per-listing counts that carry no session identifier; and raw help-center records are kept for about 90 days before being reduced to daily counts. App crash reports, with the IP address each was sent from, are kept for 60 days and then deleted; only counts of how often each fault happened are kept after that.

The raw text your browser reports about itself is kept far more briefly - 14 days - and is then deleted outright rather than aggregated. The short summary derived from it (browser, operating system, phone/tablet/desktop, language, referring site) lives with the record it describes and for the same period as that record. That gap is deliberate: the summary is what we count with, and the raw text only needs to outlive the moment someone might reasonably ask us to show our work. The one-way fingerprint described above is part of the summary, not the raw text, and lives on the same clock as the record it belongs to.

Statistics we publish

We publish some of these aggregates openly, at plukio.com/transparency. What appears there is whole-site and by day - how many browsing sessions, how many listings were opened, how many searches, how many people we sent on to a shop, and how much of that traffic was search-engine and AI crawlers rather than people. It carries no session identifier, no country, nothing about an individual shop, and nothing that can be traced back to you.

One thing on that page is text somebody typed: a short list of searches that returned no results, so that makers can see what people are looking for and cannot find. A search only appears once at least 5 separate browsing sessions have made it across at least 3 separate days - so a phrase one person searched, or a phrase searched many times in a single sitting, is never published. We use this floor because search boxes sometimes receive personal details, and a one-off search is exactly the kind of thing that must not end up on a public page. If you would rather a search of yours were not counted at all, email [email protected].

Security

We use reasonable technical and organizational measures to protect your information. No method of transmission or storage is completely secure.

Where we operate

Plukio is based in and operated from the United States, and we store and process information there. Our index covers shops worldwide, and shoppers reach us from everywhere - so if you are outside the United States, using Plukio means your information is transferred to and processed in the United States, a country whose data protection laws differ from your own. The one exception is app crash reports, which our provider stores and processes in the European Union.

Howdoicomputer, LLC is the controller of the personal data described in this policy. Our contact details are at the end of this page.

Children

Plukio is intended for adults. You must be at least 18 years old to create an account. We do not knowingly collect personal information from children.

Changes to this policy

We may update this Privacy Policy from time to time. If we make material changes, we will update the "Last updated" date above and, where appropriate, notify you.

Contact us

Questions about this policy or your information? Email [email protected], or write to Howdoicomputer, LLC, 1650 NW 21st Avenue, Portland, OR 97209.