Privacy Policy

Curio LLC ("we," "us," or "our") operates the Curio mobile application (the "App"). This Privacy Policy explains what information we collect, how we use it, and the choices you have.

By using Curio you agree to the collection and use of information described in this policy. If you do not agree, please do not use the App.

1. Information We Collect

1.1 Account Information

When you create a Curio account we collect your:

• Email address
• Display name
• Profile photo (optional)

Passwords are handled by Firebase Authentication and are never stored by us in plain text. If you sign in with Apple (on iPhone and iPad) or with Google, they share basic account details with us, such as your name and email address; with Apple, you can choose to share a relay email address instead of your own.

When you allow notifications, the App saves your device's push notification token to your profile so that we can send them.

1.2 Collection Content

You create and manage the following data within the App:

• Collection names, descriptions, and cover images
• Item names, descriptions, photos, UPC/barcode codes, condition ratings, purchase prices, current values, dates acquired, tags, notes, and custom field values
• For an item with more than one copy, the copy details you add: how many copies are in each group, what each copy cost, in US dollars or another currency you choose (for example euros or yen) with an optional US dollar figure, and the date you got them. Curio also saves your device's time zone with these details, so their dates match your calendar. Copy details are stored with the item, like its purchase price and date acquired, and like them they can be accessed by other signed-in Curio users. The App shows them to people who can view the item, as it shows the purchase price. Per-copy rows (how many, what you paid each, when) appear only in reports and exports you make of your own items.
• Trade listings and trade notes

When you apply a market value from Curio's price check, the item also records which source the value came from and when, so Curio can keep that value up to date.

Your set progress counts the sets across all your collections. It is recorded for items an import or a sync created and for a card added through photo recognition; an item you type in records nothing. A Magic: The Gathering card identified from a photo also keeps its set code as a custom field on the item.

1.3 Social and Community Data

• Follow and follower relationships
• Comments on public collections
• Direct messages with other users, and when you have read them
• Activity feed entries (new collections, items, milestones, badge achievements, and trade listings)
• Leaderboard rankings for public collections

1.4 Price and Value Data

• Price watches and alert thresholds you configure
• Daily portfolio value snapshots
• Price check results derived from in-app data and from the pricing providers listed in Section 3

1.5 Device Permissions

• Camera: used to take photos of collection items and to scan barcodes. Access is requested only when you initiate a scan or photo capture.
• Photo Library: used to import images for your items. Access is requested only when you choose to add a photo from your library.
• Face ID / Touch ID: used for biometric sign-in and to unlock your Handoff Packet. Biometric data never leaves your device; only a success/failure result is returned to the App. On iPhone and iPad, your credentials are stored in the encrypted iOS Keychain; on Android, fingerprint or face unlock is used the same way, and your sign-in is kept in encrypted storage on the phone.
• Notifications: the App asks before it sends you notifications.
• Apple Music (iPhone and iPad): used to find and play albums from your collection.

1.6 Usage and Device Information

When you use Curio, the App automatically collects some information about how it is used and about your device. We collect this through Google Analytics for Firebase on iOS and Android, and through Firebase Crashlytics on iOS. This information includes:

• App usage events, such as when the App is opened, which screens are viewed, and how long a session lasts, plus specific in-app actions we measure: when the upgrade screen is shown and which feature prompted it, when you start or complete a purchase from it, when an import, sync, or account connection (for example Discogs or Goodreads) starts, succeeds, or fails and how many items it added or updated, how many AI identifications you have used this month, how much of your storage you are using, when you share your monthly statement card (the month only), when you save notes on your copies (how many groups), when you add, open or delete a document (its kind and where it came from), and when you make a buyer's packet (where you started it and how many documents it has).
• Purchase and subscription events, such as the product purchased and its price.
• Device and app information, such as device model, operating system version, app version, language, and a random app instance identifier created by Firebase. On iOS this can include the identifier for vendor (IDFV). On Android this includes your device's advertising ID, unless you have deleted or reset it in your device settings.
• Approximate location, such as your city or country, which Google Analytics derives from your device's IP address. Curio does not use your device's location services for this.
• Crash reports (iOS only), describing the technical state of the App when it stops unexpectedly.

These events do not include the names, descriptions, photos, notes, or prices of your items, the content of your messages or comments, or your name or email address. We do not attach your Curio account ID to analytics events.

1.7 Country or Region

When you are signed in, the App reads the country or region set on your device (for example "US" or "GB") and saves that two-letter code to your Curio profile. We use it to choose prices from the right regional market, for example a European edition of a video game rather than a North American one, and, in a Handoff Packet made while your region is outside the US, to add a note that Curio records values in US dollars. It is not based on GPS or your IP address. If you change your device's region, the saved code updates the next time you open the App. On many Android phones this setting comes from your first system language, so it may not match where you live.

Your country or region code is stored in your profile record. Like other profile information, that record can be accessed by other signed-in Curio users, although the App does not display the code to them.

The App also saves the language it is shown in (for example "de" or "ja") to your profile, so that notifications and explanations our servers write reach you in that language. Like your region code, it is stored in your profile record, which other signed-in users can read.

1.8 Sales, Trades and Gifts

When you record that you sold, traded, gave away, donated or lost an item, Curio keeps a sale record so it can list what you have sold, show your gains and losses, and create your sales export. A sale record contains:

• what happened (sold, traded, gifted, donated or lost), how many copies, and the date;
• the amounts you enter: what you received, your fees (platform, payment, shipping and other), what the item cost you, and, for an item you were given, its value when you received it. Amounts are kept in the currency you enter them in, together with a US dollar figure if you choose to enter one. Curio does not convert currencies;
• when and how you got the item (bought, gift, inherited or traded), where it sold (up to 80 characters), the type of buyer (marketplace, dealer, private sale, auction, show or other), and an optional note of up to 500 characters;
• a copy of the item's details as they were when you recorded the sale, and the name of the collection it was in. The item's photos are kept with the record, and documents you attached to the item stay with the sale record and are deleted with the last record that shows them;
• for an item with copy details, which copies the sale came from, with what they cost and when you got them, your copy notes and where you bought each copy, as they were when you recorded the sale, and whether you chose them or Curio chose them for you. Like the rest of the sale record, this is visible only to you; and
• if you edit a record, the figures it had before each edit (up to 20 edits).

A sale record has no field for the buyer's or recipient's name or contact details. Please do not enter other people's personal information in the "where it sold" or note fields.

Other Curio users cannot see your sale records, including for items in collections you share with them. Sale records are stored with the rest of your Curio data on Firebase (Section 3.1). We do not send them to any other service, and they are not included in analytics events (Section 1.6).

1.14 Grading Costs and Grading Submissions

When you open grading costs on an item, or type values into it, we keep a record of that answer: the values you entered (what you'd sell it for ungraded, shipping, insurance and a selling fee), the fees and dates we used, and your app language. Only you can read it. It is kept until you delete your account.

When you open grading costs, the App sends your app language with the request so the sheet can be written in it. It is kept with that grading record.

If you record a grading submission, we keep what you entered (the grader, service, dates, declared value, fees, submission and certificate numbers and the grade it came back with) and a copy of the item's AI pre-grade at the time you sent it. Only you can read these records. They are kept until you delete them or your account.

Grades you record as returned may be counted, without your name or your item, in the grade ranges Curio shows next to other people's AI pre-grades. Ranges are shown only when at least 20 results from at least 5 people make them up. You can turn this off for any submission.

If you turn on a reminder for a grading submission, we send one push when the grader's estimated date has passed.

1.9 Information We Do Not Collect

Curio does not collect your precise location, contacts, microphone audio, health data, or browsing history, and it does not request access to your device's location services. The approximate location described in Section 1.6 is derived from your IP address and is not precise. A document image the App can't convert is uploaded as it is, so any location details already inside it stay with it (Section 1.12).

If you choose a contact for a Handoff Packet, the App copies only that contact's name, phone and email into the packet details on your device.

1.11 Blocks, Reports and Community Guidelines

You can block another collector. They can no longer message you, and the App stops showing you their messages, listings, matches, posts and comments. Curio does not tell them, but they may notice that their messages don't send. Only you can see who you blocked.

You can report a collector, a message, a conversation, a listing, or a community post or comment. A report holds who made it, what was reported, the reason and your optional note (up to 500 characters). So that a report can be reviewed even if the content is later changed or deleted, Curio keeps a copy of what was reported: the message, post, comment or listing and its photos, or the collector's name and photo. Curio staff review reports and may warn a collector, remove content, or close their account. The person you report is not told who reported them. Our email notice of a report contains only reference numbers, not the reported content.

Before you first send a message, list an item for trade or post in a community, the App asks you to accept Curio's Community Guidelines, and Curio records which version you accepted and when. You can read the Community Guidelines at https://curio-collections.com/community-guidelines.html.

1.12 Documents You Attach

You can attach receipts, certificates and other documents to an item, as a photo or a PDF. Curio keeps the file, its kind, the label you give it, its size and the date you added it. Only you can open your documents; people you share a collection with cannot. Documents count toward your storage, like photos. Curio does not read what a document says and does not send it to any other service.

A photo you attach is saved again on your device as a JPEG at most 3,000 pixels on its longest side, which removes its location and other photo details, before it is uploaded. A PDF is uploaded as it is. If your phone can't read an image to convert it, the App uploads it as it is, with its own photo details; this can happen only to a JPEG, PNG, HEIC or HEIF file of up to 10 MB. Until an upload finishes, the App keeps a copy of the file on your device so it can try again. That copy is deleted once the document is saved or removed, when you cancel the upload, when you sign out or delete your account, and otherwise after a week.

To show a document, the App downloads it to a temporary file on your device and deletes it when you close it. On iPhone and iPad, if the App closed first, the copy is deleted at a later start once it is an hour old, or at sign-out. On Android, if you choose Open in another app, that app gets a copy, which Curio deletes from its own storage after a day; the other app may keep its own. Every such copy is deleted when you sign out or delete your account.

A document is deleted when you delete it, and when you delete its item, unless a sale record still shows it, in which case it is deleted with the last such record. All your documents are deleted with your account.

1.13 Copy Notes

You can add a note and where you bought each copy of an item. Only you can see them, unlike copy counts and costs (1.2), which other signed-in users can see. Copy notes of copies you merge or remove are deleted with them. When you delete an item, or the last sale record that shows its copy notes, our weekly cleanup deletes them. All your copy notes are deleted with your account.

1.15 This Website

This section is about the Curio website at curioapps.net, not the App. Browsing the website does not create a Curio account, and nothing you do here is added to the collections, items or other account data described above.

With your permission, we use Google Analytics to count visits to the website and to see which pages people find useful. It records the pages you open, the site or search that sent you, your approximate location derived from your IP address, and the kind of device and browser you use. It sets a cookie in your browser so that a repeat visit is not counted twice. We do not use it to advertise to you, we have not linked it to any advertising account, and Google's advertising features are turned off for this website.

In the United Kingdom, Switzerland and the European Economic Area, nothing is stored on your device and no analytics cookie is set until you choose Accept on the banner we show you. Elsewhere, analytics runs unless you choose Decline, and declining stops it and removes nothing else from your visit. You can change your answer at any time with the Cookie settings link in the footer of any page on this site. Your choice is kept in your browser's own storage rather than in a Curio account, so clearing your browsing data makes us ask again.

If you write to us with the support form on this website, we receive the name, email address, topic and message you type, together with your browser's user agent string and the address of the page that sent you to the form. We use these only to answer you. They are stored with the rest of our data on Firebase (Section 3.1) and are not used for analytics or advertising. Email admin@curioapps.net to have a support message deleted.

2. How We Use Your Information

• Provide the service: store and sync your collections, items, and photos across your devices.
• Social features: power the activity feed, comments, direct messaging, trade board, leaderboards, and follower relationships.
• Price and analytics features: calculate portfolio analytics, generate value snapshots, and run price checks.
• Regional pricing: use your country or region code to show prices from the market that matches where your device is set.
• Sales and gains: show your Sold and gone list and your gains and losses, include the items you sold or gave away in your monthly statement, and create your sales export when you ask for it.
• Monthly statement: once a month, sum up your collection in a statement you can open in the App: what it is worth, how that changed, what you added, your set progress, streak, badges and season standing, and wishlist items that reached your target price, and, once you have a few statements, how your collection has changed since an earlier one. With Curio Plus, the statement also shows how the prices we applied changed your collection's value, which items' prices moved the most and by category, and your price-watch alerts, using the price history we keep for your items. If you allow it, we send one notification when your statement is ready.
• Wishlist price checks: If you turn on a price alert for something on your wishlist, Curio's servers send its name to our pricing providers (PriceCharting, eBay and SoldComps) about once a day to check the price, on any plan. While we test the daily check, Curio keeps the names of some wishlist items it priced, with the price found and your target, kept apart from your account, for up to 90 days to check the results.
• Badges: When you check the value of items yourself, the App records which items in a collection you checked that month, to award the Price Keeper badge. It is visible only to you.
• Appraisals: An appraisal checks live prices only for items Curio has no recent price record for.
• Safety: carry out blocks, review reports, keep the records described in Section 1.11, and act on accounts that break the Community Guidelines. To limit notification spam, our servers count the message, comment and follow notifications your actions send, and to whom, for the current hour or day. Your counts are deleted with your account.
• Communicate with you: send service-related notices, respond to support requests, and deliver beta invitations.
• Improve the App: diagnose crashes and bugs, understand which features are used, and measure how people move through features such as importing and upgrading, so we can make Curio better. We use analytics in aggregate for this purpose. We do not use it to show you advertising. We count how many price checks are made each month, and how many items have a price paid, in totals that do not name anyone.

3. Third-Party Services

Curio relies on the third-party services listed in this section. We do not sell your personal information to any third party.

3.1 Firebase (Google)

We use Firebase for authentication, cloud database (Firestore), file storage (Cloud Storage), and push notifications (Cloud Messaging). Your account data, collection content, messages, and photos are stored on Google Cloud infrastructure. Google's privacy policy applies to data processed by Firebase: policies.google.com/privacy.

We also use Google Analytics for Firebase to understand how the App is used, and on iOS, Firebase Crashlytics to receive crash reports (see Section 1.6). Analytics data is associated with a random app instance identifier rather than with your name, email address, or Curio account. We do not use Google Analytics to advertise to you, and we do not sell analytics data. We have not linked Google Analytics to any advertising account. Google keeps user-level analytics data for 2 months and then deletes it automatically. You can learn how Google uses information from apps that use its services at policies.google.com/technologies/partner-sites.

3.2 eBay API

When you check a price or look up a barcode, our server sends item names, keywords or barcodes to eBay's APIs and receives listing data in return (see Section 3.5). No personal information is shared with eBay. eBay's privacy policy: ebay.com/privacy.

3.3 UPC Item Database

When you scan a barcode, the UPC code may be sent to the UPCitemdb service to retrieve product information (title, brand, images). No personal information is included in these requests.

3.4 App Stores and Subscription Management

Subscriptions are processed through Apple's App Store on iOS and Google Play on Android. Payment and billing information is handled entirely by Apple or Google and is not accessible to us.

We use RevenueCat to manage subscriptions. RevenueCat receives your purchase and subscription history and your Curio account ID so that your subscription is recognized on every device you sign in to. RevenueCat does not receive your payment card details. RevenueCat also tells our servers about your purchases and renewals, and we keep that record with your account to confirm your plan. It is deleted with your account.

Apple's privacy policy: apple.com/privacy. Google's privacy policy: policies.google.com/privacy. RevenueCat's privacy policy: revenuecat.com/privacy.

3.5 Services That Receive Some of Your Data

These services receive only what a lookup or feature you use needs. "Server" means our servers send it; "device" means the App sends it directly.

• Google (Gemini) (server): photos you choose to identify with AI, and the text of the request.
• Ximilar (server): photos of trading cards you identify, and card photos you ask to pre-grade.
• Scryfall (server and device): card names read from a photo, and the card names and ids of Curio Plus items when our server updates their prices (server); card names and ids you search or build decks with (device).
• The Pokémon TCG API (server): card names read from a photo.
• TCGdex (server and device): the card names and ids of Curio Plus items when our server updates their prices (server); card names and ids you search or build decks with (device).
• Lorcast and YGOProDeck (device): card names and ids you search or build decks with.
• PSA (server): a certificate number read from a graded slab's photo, to check it (only when our PSA access is configured).
• eBay (server): item names and barcodes for price checks and barcode lookups, from our server instead of from your device; once Curio's daily wishlist check starts, the names of wishlist items with an alert.
• PriceCharting (server): item names and barcodes for price checks. Price lookups from the App go through our server to PriceCharting. Once Curio's daily wishlist check starts, PriceCharting also receives wishlist item names.
• SoldComps (server): item names for sold-price checks; once Curio's daily wishlist check starts, wishlist item names.
• CardHedge (server): a trading card's photo or its name, set and number, to identify and price it.
• WhiskyStats (server): the text read from a whisky label, or a bottle name you search.
• Serper (Google image search) (server): a product name, to find a picture when a barcode lookup found the product but no photo.
• RAWG, and IGDB by Twitch only when configured (server): a video game's title, to fill in its details.
• The website you import from (server): the link you paste; our server opens that page to read the item.
• Algolia (server and device): your collections, items, public profile details, communities and posts, for search (server); what you type in search (device, with a key limited to your account).
• Our email delivery service (server): the Collector Spotlight nominations you send (your name, account ID and answers) and our report notices (reference numbers and the reason only), on their way to the Curio team's inbox.
• Apple Push Notification service (server): a Live Activity token and progress counts, when you batch-add items on iPhone.
• Brickognize (device): photos of LEGO pieces or sets you identify.
• Funko (funko.com) (device): the name and number of a Funko Pop! figure identified from a photo, to find its catalog entry.
• UPCitemdb and UPCDatabase.org (device): barcodes you scan.
• Open Library (device): book ISBNs you scan or import, to find covers.
• Comic Vine (device): comic titles you search or identify (when the App has a Comic Vine key).
• Numista, Letterboxd and Deckbox, and PriceCharting on Android (device): the Numista user id, feed address, set address or (Android) PriceCharting user name you enter, to sync your collection.
• Discogs (device): a record's barcode, or its artist and title, when you identify it; a release's id, to find its cover art; on iPhone and iPad, when your Discogs account is connected, a release's id to look up its Discogs marketplace figures; and, when you connect Discogs, the App signs in to your Discogs account and reads your Discogs collection to import and sync it.
• Goodreads (device): the App reads the shelf feed address you enter, to import and sync your books.
• Apple Music, Spotify and YouTube Music (device): an album's artist and title, when you tap Listen on a music item. On iPhone and iPad, the App searches Apple Music's catalog for the album; otherwise it opens that service's search for it.
• RevenueCat, Apple and Google: as described in Section 3.4.
• Google Firebase (Firestore, Storage, Functions, Cloud Messaging, Analytics; Crashlytics on iOS): as described in Section 3.1.

To limit use, we keep a daily count of your eBay and PriceCharting price lookups (your account ID, the day and a number). It is deleted with your account. eBay price search results are kept for at most about a day, without any account ID. What eBay tells us a barcode is goes into our shared barcode cache, also without any account ID.

We keep similar counts, each with your account ID, the day or month and a number, for other lookups and requests: barcode, card, whisky and sold-price lookups, imports from a link, insurance reports and catalogs, reports about other collectors, changes to copy details, AI identifications and AI pre-grades, and grading-cost requests. They are deleted with your account too.

If PriceCharting reports an error on a lookup, we log its message with the first characters of your account ID, never what you searched.

4. Public and Shared Content

Certain content you create may be visible to other Curio users:

• Public collections: visible to all users and appear on category leaderboards, including collection name, description, item count, total value, and your display name and photo.
• Trade listings: visible to all users, including item details, condition, value, and your display name and photo.
• Comments: visible to anyone viewing the public collection they are posted on.
• Profile information: your display name, photo, bio, follower count, and following count are visible to other users.
• Profile record: your country or region code (Section 1.7) and app language are stored with your profile and can be accessed by other signed-in users, although the App does not display them.
• Items and profile records: your collections, including private ones, the items in them (including details the App doesn't show to others, such as price paid and notes), their photos and their value history, your activity entries, your badges, the comments you post and who you follow can be accessed by other signed-in users through Curio's data service. Your profile record, including your email address, your plan, any creator code you used, your notification settings and the push notification tokens of your devices, can be accessed the same way.
• Wishlist prices: The last price Curio's daily check found for a watched wishlist item, and when it last checked, are stored with it. If your wishlist is public, other signed-in users can see them.
• Whisky bottles: If you add a whisky bottle identified with WhiskyStats, Curio's whisky catalog records that your account holds it, to count how many collectors hold each bottle. Other signed-in users can read that record.
• Your streak and seasonal badges are private: Your collecting streak and seasonal badges are visible only to you. Curio also uses them to build your monthly statement.
• Blocks and reports are private: nobody else can see who you blocked or reported.
• Sale records are private: other users never see them. Recording the sale of every copy of an item removes the item from your collection and ends its trade listing, as deleting it would. If the item was in a collection you share, the people you share it with see the item leave the collection, or its quantity go down, but not the sale.
• Activity feed: actions such as creating collections or items, reaching milestones, and earning badges are shown to your followers in the App.
• Featured Collectors: your profile may be featured to other users in Find Collectors, chosen automatically each week from your recent activity, followers, collections and items.

In the App, private collections are shown only to you and to the people you invite (as viewers or editors); see "Items and profile records" above for what other signed-in users can still read.

5. Data Storage and Security

Your data is stored on Firebase (Google Cloud) servers. We use HTTPS for all data in transit and rely on Firebase's built-in encryption for data at rest. Biometric credentials are stored in the iOS Keychain using the most restrictive accessibility level (whenUnlockedThisDeviceOnly), meaning they cannot be extracted from backups or accessed by other apps.

While we take reasonable measures to protect your data, no system is perfectly secure. We encourage you to use a strong, unique password for your Curio account.

6. Data Export and Portability

On iPhone and iPad, you can export your collections at any time in CSV, JSON or XLSX format. On both iPhone and Android you can export your sales for any year as a CSV file from Sold and gone in your profile. Curio Plus members can also create PDF insurance reports, collection catalogs and a PDF of their sales. Exports, appraisal reports and the sales PDF are created on your device and are not transmitted to our servers. Insurance reports and collection catalogs are created on our servers from your collection's items, values and photos. The App downloads the finished PDF to your device, and we delete our copy, and the link used to download it, 24 hours after it is made.

Curio Plus members can also make a Handoff Packet, a PDF guide to their collection for the people who would look after it. If you have saved packet details but don't have Curio Plus, for example after your subscription ends, you can still make a PDF of just those details at no charge. Both are made on your device from information already in Curio, such as your collections, values, photos and sale records, and are never uploaded to our servers.

What you enter for the packet is saved only on the device where you enter it, not in your Curio account: the name on its cover, your places and how to find them, which collections and items are kept where, the people you list and their contact details, your paperwork notes and your note. These details are never sent to our servers or included in analytics or crash reports. On iPhone and iPad, they are also included in that device's backups, so they can move to a new iPhone or iPad set up from a backup or transferred from that device. On Android, they are not included in cloud backups, but moving your apps and data directly to a new phone may copy them.

Before you share or print a packet, you can preview it inside the App. The preview has no share or copy option, and its text can't be selected. While you decide, the App keeps the PDF in temporary storage on your device. On iPhone and iPad, it deletes the file when you leave the "Before you share this" screen. On Android, it deletes a file you didn't share at that point too, but keeps a file you chose to share, print or open in another app, because the app you sent it to may still be reading it; a background task deletes that file about a day later, even if you don't open Curio again, and does the same for a file you didn't share if Curio closes before it can delete it (if you force-stop Curio in Android's settings, Android holds that task until you next open Curio, which then deletes the file). On iPhone and iPad, if Curio closes before it can delete a file, the file is deleted the first time Curio starts after the file is more than 24 hours old; on Android, the background task above does this, and starting Curio after that day deletes it too. Signing out deletes all of these files. The PDF's built-in document details, which PDF apps show as its properties, list no more than its title and Curio as the app that made it: Curio removes the entries PDF software usually adds, such as when the file was made and which software wrote it. Copies you save, send or print outside Curio are not affected, and Curio can't remove them.

The buyer's packet is made on your device, like the Handoff Packet. To include a document you attached, the App downloads it from your account to your device. Curio doesn't keep the packet or send it anywhere; the App deletes its own copy within a day.

The amount you set for "Suggest an appraisal above", the per-place totals and the collections you leave out of a Handoff Packet are saved only with the packet details on your device.

When you share your monthly statement card, the App draws it on your device and hands it to the app you choose. Nothing is uploaded. The card shows no amount, item name, photo, user name or sales count. On Android, a copy stays in the App's cache until it is replaced or the cache is cleared.

An item's History is put together on your device from the item, its copies, your sale records, documents and notes. It is not stored anywhere and only you can see it.

When you tap a PriceCharting citation in your monthly statement, it opens pricecharting.com in your browser; Curio sends PriceCharting nothing.

7. Data Retention and Deletion

We retain your data for as long as your account is active. You can delete individual items or entire collections from within the App at any time, and their photos are also removed from our servers. An item's price history stays with its collection after you delete or sell the item, so a sold item can still show it. It is deleted after you delete the collection (by our weekly cleanup) or with your account.

Copy details are deleted with their item, and with your account. If you remove an item's copy details, Curio keeps the item's purchase price and date acquired as they were last shown and notes when the details were removed. A sale record keeps the copy details it recorded until you delete the record.

Sale records (Section 1.8) are kept until you delete them, so your Sold and gone list and sales exports stay complete. Recording the sale of every copy of an item removes the item from your collection, but its photos stay with the sale record. You can put a sold item back in your collection at any time; its sale record then stays on file, marked as put back, so the same sale cannot be recorded twice by mistake. You can delete a sale record permanently from your Sold and gone list. That deletes the record and its earlier figures, and deletes the item's photos once no other record refers to them. A put-back record stays in your Sold and gone list under "Put back in your collection" until you delete it there. Deleting it removes the record permanently.

To include your alerts in your monthly statement, we keep a short record of each price or wishlist alert we sent you (the item's name, the prices and the date) until about three months after the end of the month we sent it. Price Watch shows your alerts from the last 40 days, including the alerts our servers send; when you open it, the App deletes older alerts from our servers. All your alerts are deleted with your account.

Reports, with the copies kept with them, are kept for 12 months after they are closed, and then deleted.

You can delete your account at any time from within the App: open your Profile and choose Delete Account. This deletes your account and its data right away, usually within a few minutes: your profile, its country or region code and app language, your collections, items and their photos, documents you attached, your copy notes, your grading-cost records and grading submissions, want list, decks, sale records, monthly statements, your statement alert records, report requests and report files, trade listings, price watches and alerts, your daily price-lookup counts, follows, badges, streaks, the record of which items you checked for a badge, and leaderboard entries, your messages and the conversations you were part of, for both participants, your comments, likes and community memberships, the community posts you wrote, together with the comments and likes other people left on them, any Collector Spotlight feature about you, our stored copies of the emails your nomination sent us, your blocks and your Community Guidelines acceptance, and the sign-ins you connected to other services. A community you created is deleted if nobody else has joined it or posted in it; otherwise it stays for the others, with no owner, and their posts in it stay too. You are also removed from any collection another user shared with you and from any early-access group you were in, and the follower and following counts of the people you followed, or who followed you, go down by one. Your account ID is removed from most of the lists we use to try out features, including the list for test statement notifications. If an item you added was used for an entry in Curio's shared barcode catalog, your photo and the link to your item are removed from that entry; the product's name, description and tags stay. If the deletion is interrupted, for example because the connection dropped, you can try again, and the next attempt finishes it. Until you try again, or ask us by email, the deletion stays incomplete and your account remains. If the App saves a record to your account after it is gone, for example an item, a setting or a follow saved just as the deletion ran, a weekly cleanup removes it. That cleanup does not remove community posts or communities; if one saved at that moment is left, email us and we will delete it. You can also email admin@curioapps.net, and we will delete your account and its data within 30 days of a verified request.

Handoff Packet details (Section 6) are saved only on your devices, not in your account. When you delete your account in the App and the App confirms the deletion, it also erases the packet details and packet files saved for that account on that device. If Delete Account ends because your sign-in has expired, the App signs you out and deletes its packet files but keeps the details, because it can't confirm that your account is gone. To erase them, sign in again and delete your account again, or, if your account is already gone, delete the App from that device. Details saved on another device stay there, and the App can open them only while you are signed in to your account, so erase them on that device with "Erase what you typed" before you delete your account, or delete the App from that device afterward. On iPhone and iPad, a copy in a device backup stays until that backup is replaced. Signing out does not erase packet details, and another account signed in on the same device can't see them. Packets you have already shared, saved or printed are not affected.

If you delete your account, your blocks and your Community Guidelines acceptance are deleted. Reports others made about you are kept for 12 months after they are closed, and reports you made are kept for their review without your account ID.

We keep a few records after your account is deleted: records of your purchases and of what we owe creators, which we must keep for accounting and tax, with your account's internal ID removed from them; a marker for each collection you had, holding only its ID and your account's internal ID, which stops anyone else from taking over the collection's address; logs of our automated maintenance jobs, which record what each run did: mostly IDs, such as your account's internal ID and the IDs of your items, and for a few internal checks, your plan; an index we use to match items to market prices, which can keep the IDs of items you added and the words of their names, but not your account; another user's notification counter, which can still name your account ID until that user next sends a notification of the same kind; and a few internal settings that can still name your account's internal ID, such as a price-market setting for your account or a list used to try out a server change. A test copy of a monthly statement in our job logs is removed when you delete your account, or by our weekly cleanup within a week. The nomination emails already delivered to the Curio team's inbox are not deleted by Delete Account; email admin@curioapps.net to have them deleted. Deleting your account does not cancel a subscription: cancel it with Apple or Google. A renewal or refund the store reports after your account is gone is recorded with your account's internal ID. Apple, Google and RevenueCat hold their own records of your subscription purchases; manage or delete those with them. If you connected Discogs, Delete Account deletes our copy of that sign-in but does not revoke Curio's access at Discogs; you can revoke it in your Discogs account settings.

Analytics and crash data is not linked to your Curio account, so it is not removed when you delete your account. Google deletes user-level analytics data automatically after the retention period described in Section 3.1.

8. Children's Privacy

Curio is not directed at children under the age of 13. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided us with personal information, please contact us and we will delete it promptly.

9. Your Rights

Depending on your jurisdiction, you may have the right to:

• Access the personal data we hold about you
• Request correction of inaccurate data
• Request deletion of your data
• Export your data (see Section 6)
• Object to or restrict certain processing

To exercise any of these rights, email admin@curioapps.net.

10. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will revise the "Last updated" date at the top and, where appropriate, notify you in the App. Your continued use of Curio after changes are posted constitutes acceptance of the revised policy.

11. Contact Us

If you have questions or concerns about this Privacy Policy or your data, contact us at:

Curio LLC
Email: admin@curioapps.net