Privacy Policy
This policy explains how your personal data is processed when you use the catalogtopia.com website and the Catalogtopia application at app.catalogtopia.com. It is organised under the headings of Türkiye's Personal Data Protection Law No. 6698 (KVKK) and the EU General Data Protection Regulation (GDPR).
Last updated:
1. Data controller
The data controller is Highone Group LLC (a limited liability company organised in New Mexico, USA), which operates Catalogtopia.
- Address: 1209 Mountain Rd Pl NE Ste 13537, Albuquerque, NM 87110, USA
- E-mail (including KVKK applications, privacy and data deletion requests): info@highonemedia.com
2. Scope
This policy covers two services: catalogtopia.com (the website and these legal pages) and app.catalogtopia.com (the application in which businesses analyse their product catalogues). Catalogtopia is a service for businesses; it processes the data of the people who open an application account on behalf of a company or a sole proprietorship.
3. Data we process
| Category | Data | Source |
|---|---|---|
| Account | Name, e-mail address, whether the e-mail is verified, an irreversible hash of your password (scrypt). The password itself is never stored. A record that you accepted the Terms of Service and the Privacy Policy at sign-up: the terms version (the Terms of Service page's last-updated date), when you accepted and in which language; no IP address or browser information is written to it. | Sign-up form |
| Session | A session cookie; in our database only the SHA-256 hash of the session key, its expiry, its last activity and a device summary (browser family, operating system, device type — no version or model). No IP address is written to the session record; the server's access logs keep the IP address and browser information separately (see "Server logs"). | Your browser |
| Account security | If you turn on two-step verification: your authenticator's secret key (encrypted) and the last accepted code step; only irreversible verification values of the recovery codes (the codes themselves are not stored). When you ask to change your e-mail address: the old and new address and only SHA-256 hashes of the links (a link works once). Your account's security events (for example password changed, session ended, two-step verification on): the action, the time and a short detail (for example the verification method used); no address, IP, code or password. An account recovery started at a support request: the time, a short reason, a hash of the cancel link (and, for an e-mail recovery, the new address). | You / the application |
| Activity records | Who performed which action in the application (user identifier, action, target, time). No IP address is written to these records. | The application |
| Store and catalogue data | Product information from the Shopify store you connect or the CSV/XML feed you add (title, description, brand, price, stock, image links, etc.), a raw copy of the source, and the feed address. If you put personal information into product data (e.g. a brand that is a person's name), that is processed too. | Shopify / your feed |
| Connection keys | Shopify and Meta access keys — encrypted with AES-256-GCM. | Your connection |
| Meta catalogue information | The Meta catalogue ID and name; the catalogue items' IDs, retailer_id and retailer_product_group_id values, review and visibility statuses and Meta's error codes. | Meta (through your connection) |
| Meta connection information | The identifiers of the Meta business that approved the connection; a keyed hash of the identifier of the Meta account that made the connection (not the identifier itself); a record of the connection-removal and data deletion requests Meta sends us (kind, time, status, confirmation code — no Meta identifier and no content). | Meta (through your connection) |
| Product images | Images you upload to your products' galleries and product images we copy from the sources you connect (Shopify, feed). Before storing them we remove the information embedded in the file: location (GPS) and camera details (EXIF), XMP, IPTC, comments, secondary images attached to the file and unknown extra data. The colour profile is kept. Images are kept at an address that anyone who knows it can open. We do not recompress an image needlessly; we re-encode only WebP files, files over 8 MB, or images that have to be rotated. Video upload is not offered. | You / Shopify / your feed |
| Records of writes to Shopify | For each image send you approve, its preview: the images to be sent and their order, a digest of the preview (SHA-256), the user who approved it and when. For each image sent, its ID and status on Shopify: ready, failed, or Shopify's error code from a closed list. The gallery order last verified there. | The application / Shopify |
| Shopify privacy notices | A record of Shopify's mandatory privacy notices: the notice's ID, its topic (customers/data_request, customers/redact, shop/redact), when it was received and processed, and its status. The store address is kept only until the notice is processed. Fields that carry customer information (name, e-mail, phone, orders) are never recorded. | Shopify |
| Google connection and Merchant Center information | The access keys of your store's Google connection — encrypted with AES-256-GCM; the ID of the Merchant Center account you choose; the feed label and language your catalogue is linked with; for Google's processed products, their offer IDs, the data source each is built from, their destination statuses (context and countries) and the structural part of the issues Google reports: code, severity, resolution type, affected attribute, context and countries. Google's description, detail and help-link texts are not stored. | Google (through your connection) |
| Records of corrections sent to channels | For each correction you approve: for which product and with which fields it was sent to Google or Meta, and how the channel's read-back shows it (pending, verified, failed, unsupported, withdrawn). Of the random key in the address of the Meta supplementary feed, only its SHA-256 hash is kept. | The application / Google / Meta |
| Catalog-management consent | The user who gave it, the workspace, the catalog, the channel, the time and the terms version; when management is turned off, the time it was. | Your choice |
| Channel send records | Per product, the record ID Catalogtopia assigned, the values last verified, the send status and the channel's refusal reason (a closed list of codes; the channel's raw error text is not stored). | The application and the channel's answer |
| Alerts | What the daily check found (by rule, source or connection identifier; never product content), a record of each person's daily digest e-mail (the day, the organisations it covered, the number of items, the e-mail provider's message ID), and your alert e-mail preference. | The application |
| Uploaded CSV files | The catalogue file you upload is kept on our server, in a directory nobody else can read, under a random name until it is imported; its original name is not kept. The record keeps only its size, a SHA-256 digest, the user who uploaded it and the time. The products imported from it are kept like products from a feed. | You |
| Server logs | On both sites: IP address, time of the request, the address requested, response code, referring page (Referer) and browser information. On app.catalogtopia.com only the path of the address requested and of the referring page is written; the query part (after "?", for example the one-time codes in links) is not. | Your browser's request |
| Preferences stored in the browser | On catalogtopia.com only: your theme and language preference (in your browser's localStorage; never sent to us). | Your choice |
4. Data we do not process
- We do not read your Shopify store's customer or order data. The permissions requested from Shopify are in section 7.
- We do not read user, advertising, pixel or event data from Meta.
- We do not process payment information (there is no paid plan at present).
- We use no analytics, advertising or tracking tool; we do not sell your data or use it for advertising.
5. Purposes and legal bases
| Purpose | Data | KVKK Art. 5 / GDPR Art. 6 |
|---|---|---|
| Opening your account, signing you in, e-mail verification and password reset | Account, session | Entering into and performing the contract (KVKK 5/2-c; GDPR 6/1-b) |
| Account security — two-step verification, sessions, security notices | Account security, session, account (e-mail) | Performing the contract (KVKK 5/2-c; GDPR 6/1-b); legitimate interest — security (KVKK 5/2-f; GDPR 6/1-f) |
| Analysing your catalogues, showing issues and what Meta and Google report; writing titles to Shopify on your instruction, sending the product images you approve to Shopify, writing the price changes you approve to Shopify and passing the corrections you approve to Google and (where this feature is turned on for your account) Meta; for catalogues where you chose "Let Catalogtopia manage this catalog", sending your product information to Meta and Google and keeping it up to date; importing the CSV file you upload | Store/catalogue data, connection keys, Meta and Google catalogue information, images, correction records, uploaded files | Performing the contract (KVKK 5/2-c; GDPR 6/1-b) |
| Telling you by e-mail about new items in your sources and channel connections that need attention (you can turn this off) | Account (name, e-mail), alerts | Performing the contract (KVKK 5/2-c; GDPR 6/1-b) |
| Security of the service, preventing abuse, debugging | Server logs, activity records, session, request rate and failed sign-in counters | Legitimate interest (KVKK 5/2-f; GDPR 6/1-f) |
| Legal obligations and protecting rights | The data concerned, as far as necessary | Legal obligation; establishing a right (KVKK 5/2-ç, 5/2-e; GDPR 6/1-c, 6/1-f) |
We do not use your data for automated decision-making or profiling.
We send service e-mails only: account, security, alert and trial notices. We do not send marketing e-mails.
6. Meta (Facebook) data
When you connect your Meta catalogue, we read from Meta only the catalogue ID and name and, for the catalogue's items, their IDs, retailer_id and retailer_product_group_id values, review and visibility statuses and error codes. Meta's error description texts are not stored. We use this information only to show it to you in the application as "Meta reports"; it does not enter Catalogtopia's health score.
Your Meta access key is stored encrypted, is never sent to a browser and is used only for requests to Meta. To see that a connection is still valid, we make one light identity query to Meta per connection at most once a day.
The Meta supplementary feed. Writing corrections to Meta is not turned on for any customer account today; it runs only in Catalogtopia's own test account. Where this feature is turned on for an account and started for a catalogue, we attach a supplementary feed named "Catalogtopia corrections" to the Meta catalogue's main data source and ask Meta to fetch that feed's file from an address at Catalogtopia: once when it starts, then at most once an hour when the file has changed. The file holds only the items' content IDs and the corrections you approved: title, description, Google product category, colour, size, gender, age group, material and pattern. Price, stock or the content ID are never changed, and your main feed at Meta is not changed either. The file's address carries a random key, and we keep only a hash of that key. To see whether a correction shows at Meta, we read those fields of the items from Meta. When the supplementary feed is stopped, the feed is deleted at Meta and the address stops answering. Whether Meta then removes the values it took from the file is something we cannot yet confirm by reading Meta, so our records and our screens show it as "removal requested, not verified at Meta".
Sending products to Meta (Catalog management). When you choose management for a catalog and approve the first send, we add your products to, and update them in, the Meta catalog you mapped, through Meta's Catalog Batch API. The fields sent are the list in the Terms of Service. Each product's ID on Meta is a permanent ID Catalogtopia assigns, so a repeated send creates no duplicate. We check each product we send by reading it back from your catalog: title, description, link, the main image link, price, currency, stock status, condition, brand, GTIN, MPN, colour, size and review status. We do not change products another source created on Meta.
A Meta connection belongs to a store and is managed on the Data Sources page of the application. "Disconnect" on the store's Meta card deletes that store's encrypted Meta access key immediately and ends the connection. The catalogue mapping and the item statuses already read from Meta are not deleted by this step: the mapping counts as unverified and is verified with Meta again when the store reconnects. "Disconnect" deletes our access key and asks Meta to cancel that key (the request is not sent if the same Meta account is used by another connection). Catalogtopia may still appear in Meta's Connected apps list. To remove it there too: Business Settings → Connected apps → Catalogtopia → Remove.
When you remove Catalogtopia in Meta, the connection becomes "Connection removed" as soon as Meta refuses our access key with an error saying the app was removed. If Meta sends us a data deletion request or a notice, we process it when we receive it; if not, we detect the removal at the daily connection check. The 24 hours start the moment we see Meta's refusal. This timer starts when we detect the removal, not when you remove the app in Meta; the daily check, the job queue or service delays can affect when the deletion completes. The connection is not shown as deleted until the deletion has completed. When the time is up, the data that came from Meta for that connection is deleted automatically: the Meta access key and the connection record, the Meta business identifiers, the catalogue mappings, the item statuses read from Meta and the supplementary feed records. We ask Meta once more before deleting. Other reasons, such as a password change, an expiry or a temporary error, delete nothing; the connection stays "needs reconnecting". Reconnecting the same store within the 24 hours cancels the deletion. If you do not want to wait, use "Delete Meta data now" on the Data Sources page; it first shows what will be deleted, with counts, and asks you to confirm.
When Meta sends us a data deletion request, we verify it with Meta's signature and give Meta a confirmation code and the address of a public page that shows only the request's status. If the Meta account in the request matches a connection cryptographically, the data is deleted at once. If it does not, the request is not applied to any connection by guesswork: the data goes through the automatic deletion above, and as a backup you can sign in and enter the confirmation code on that store's Meta card. Your own catalogues, products, Shopify, XML and CSV sources, store and workspace are not affected by this deletion. The minimum records needed for security or legal obligations may stay (the request record and activity records); they contain no access key and no content from Meta, and their retention is in section 12.
Catalog management and Meta's requests. When you remove Catalogtopia on Meta (deauthorization), no product is sent to Meta through that connection and sends waiting in the queue stop. On a verified data deletion request, the records of products sent to Meta through that connection are deleted too, and the catalog's Meta management ends. Your Shopify, XML/feed and CSV source data, your products and your Google data are not deleted, and no other workspace's records are touched. The products in your Meta catalog are not deleted because of this request; you can delete them yourself in Meta Commerce Manager.
You can always make a deletion request by writing to info@highonemedia.com from the e-mail address registered to your account as well. What can be deleted today and how to make the request: Data Deletion Instructions.
7. Shopify data
When you connect your Shopify store we read its product data. Catalogtopia's Shopify App Store app asks for both the read_products (product reading) and write_products (product writing) permissions at installation, and uses the writing permission only to write the changes you approve: title corrections and product images (including the image order; in this app, image sending is turned on at installation). It does not write prices. When you connect your store from your Catalogtopia account, installation asks only for read_products; if you separately and explicitly turn on writing to Shopify, the write_products permission is requested and is used to write only three things: the title corrections you approve, the product images you approve and the price changes you approve. We ask for no other Shopify permission. The Shopify access key is stored encrypted.
Sending product images to Shopify. When this feature is turned on for your account, you see a preview before the images of a product or a catalogue are sent to Shopify:
- Shopify's current order and the order after the send are shown side by side.
- Images that will not be sent are shown with the reason. For example, images over Shopify's limit are not sent: those with an edge over 4472 pixels or a total over 20 megapixels.
- A preview is valid for 30 minutes and covers at most 200 products at a time.
Nothing is sent until you approve the preview. On your approval:
- The images in your gallery are given to Shopify by their public Catalogtopia addresses. Shopify downloads each image from that address and keeps its own copy.
- Images that came from Shopify are never added again; only their order is set.
- Your gallery's order is applied on Shopify. Images you added directly on Shopify that Catalogtopia does not hold are not deleted; they stay in place after ours.
- After the send, the order on Shopify is read back and verified.
If a product's image order on Shopify has changed since the preview or since our last verified send, the product is shown as a "conflict". A conflicting product is not sent unless you tick its box.
An image that has been sent stays on Shopify. Catalogtopia does not delete images from Shopify today: removing an image from your gallery does not delete its copy on Shopify. You can delete that copy in your Shopify admin.
Shopify's privacy notices. Shopify sends apps three mandatory privacy notices. We verify each with Shopify's signature, and a notice whose signature cannot be verified is not recorded.
- Customer data request and customer data erasure (
customers/data_request,customers/redact): Catalogtopia never reads or keeps your store's customer or order data, so there is nothing to export or erase. We note that the request was answered in an activity record. That record contains no part of the request (no customer ID, e-mail, phone or order). - Shop data erasure (
shop/redact): Shopify sends this notice 48 hours after you remove the app from your store. If you reinstalled the app in the meantime, nothing is deleted. If you did not, that store's Shopify access key, permissions, store address and Shopify store ID are deleted at once; the store's products are at once treated as "no longer in the source" and leave the health score, the issues and the counts; and the store address is removed from old activity records. Following Shopify's shop data erasure request, the product records from that store and the image copies belonging to those products, backups included, are permanently deleted within 30 days at the latest of receiving the request.
Disconnecting the store's Shopify connection in the application deletes the Shopify access key at once. For a deletion request, you can use the routes in the Data Deletion Instructions.
8. Google Merchant Center data
When you connect a store to Google, you sign in with your Google account and give Catalogtopia the Merchant Center permission (Google Merchant API). From Google we read only the IDs and names of the Merchant Center accounts you can reach and, for the products processed in the catalogue you link, their offer IDs, data sources, destination statuses and issues; of the issues we keep only the structural information we need (section 3) and do not keep Google's description texts. When we read: when you connect and when you choose the Merchant Center account (the account list); for each catalogue you link, once every 24 hours, on a schedule; when you ask ("Read from Google"; also when you link a catalogue and when the supplemental data source is created); after actions such as approving or undoing a correction; and, until a correction we sent shows at Google, at most once a minute for verification, for at most 6 hours (a correction not shown within 6 hours counts as failed, never as verified). A read that could not finish is tried again at growing intervals: the first wait is at most 1 minute and doubles each time, up to 60 minutes; when Google asks us to slow down we wait as long as it says, at most 24 hours. When Google refuses the access, or a Merchant Center permission is missing, the read is not repeated on its own: it stops until you reconnect Google, or fix the permission and press "Read from Google". Google access keys are stored encrypted and are never sent to a browser.
Sending corrections to Google. When this feature is turned on for your account, we create an additional data source named "Catalogtopia corrections" (a supplemental data source) in your Merchant Center account and send the corrections you approve to that source only: Google product category, title, description, colour, size, gender, age group, material and pattern. Price and stock are never sent. We write nothing to your primary data source or its rules; you add our supplemental source to your primary source's rules yourself, in Merchant Center. We verify that each correction we send shows at Google by reading the processed product again; when you undo a correction, we delete its counterpart in our source. Before sending a correction we read that the Merchant Center account you chose is still reachable, and only the structure of the account's data sources: each source's ID, type (primary, supplemental or other), input (API, file, the Merchant Center interface or automatic feed), feed label, content language, and whether a supplemental source's name matches ours. We also read, from Google's account list, whether the account is an advanced account that manages several clients. We do not keep the sources' names, file names, fetch addresses, user names or passwords.
Sending products to Google (Catalog management). For a catalog where you chose management, we create an API primary data source named "Catalogtopia" in your Merchant Center account and store its ID. We send your products to that source only. We do not change, move, take over or delete the products in the data source of Shopify's Google & YouTube channel or of any other app. We check that each product we send has been processed on Google by reading back the processed product and its status; if Google rejects a product, we show you the reason. For this we also read the list of data sources in your Merchant Center account and whether your website is verified.
"Disconnect" on the store's Google card deletes the Google access key from us at once; the Google connection, the catalogue links, the product statuses read from Google and the delivery records are deleted too. Today we do not revoke the permission at Google: a single revocation at Google removes every permission your Google account gave Catalogtopia and could break your other connections too. You can remove it yourself on your Google Account's permissions page (myaccount.google.com/permissions). The corrections you approved in Catalogtopia are not deleted. Our supplemental data source in Merchant Center, and the corrections in it, stay at Google after a disconnect; you can delete them in Merchant Center.
We use the data we receive from Google, and anything derived from it, only to provide and improve the features described in this section, which you see and use in Catalogtopia. We do not sell it. We do not use or transfer it for advertising, including retargeting and personalised or interest-based advertising; we do not transfer it to advertising platforms, data brokers or information resellers; and we do not use it to determine credit-worthiness or for lending. We transfer it only as needed to provide these features, for security purposes (for example, investigating abuse), to comply with applicable law, or as part of a merger, acquisition or sale of assets after obtaining your explicit prior consent. People do not read it unless you have given your affirmative agreement, it is necessary for security purposes (for example, investigating a bug or abuse), it is necessary to comply with applicable law, or it is aggregated and used for internal operations in accordance with applicable law. Catalogtopia's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. You can also remove Catalogtopia's access from your Google Account's permissions page (myaccount.google.com/permissions).
9. Etsy data
Today: the listings file. You upload your Etsy listings with the listings file you download yourself from Shop Manager on Etsy (CSV). According to Etsy this file holds your active listings only: title, description, price, currency, quantity, tags, materials, image addresses and, if you have them, SKUs. We process this file like any other CSV file (sections 3 and 12). For this path we never connect to Etsy.
The Etsy API connection (closed at the moment). When connecting your Etsy shop through Etsy's API becomes available, these rules will apply:
- We read only your own shop's listings; we do not access any other shop's data.
- We ask Etsy for three permissions only:
listings_r(reading your listings),shops_r(seeing that the connected shop is yours) andlistings_w(writing a fix you approve to your listing). We do not ask for order, buyer, e-mail or address permissions. - Etsy access keys are stored encrypted and are never sent to the browser.
- We never show listing content from Etsy more than 6 hours older than on Etsy; if it is older, we read it from Etsy again first. We do not keep Etsy content longer than needed to provide the service.
- When you disconnect, we delete the Etsy access key and the listing copies we took from Etsy.
We use Etsy data only to provide this service to you: not for market or competitor analysis, comparisons between shops or training machine-learning models; we do not sell it or give it to third parties. We process Etsy members' data on your behalf and only for the service we provide to you. If this data is breached, or we suspect it has been, we tell Etsy and you within 24 hours of discovering it at the latest.
10. Security
- All traffic is encrypted with HTTPS.
- Passwords are hashed with scrypt; session keys are kept in the database only as hashes.
- Shopify, Meta and Google access keys are encrypted with AES-256-GCM and are never sent to a browser.
- Each customer account's data is separated from the others by row-level security in the database.
- Database backups are stored encrypted (GPG).
11. Service providers and transfers abroad
We work with the providers below to run the service. We do not sell your data. Data sent to services operated outside Türkiye is transferred abroad.
| Recipient | Purpose | Data | Location | Legal basis |
|---|---|---|---|---|
| Hosting Dünyam Bilişim Teknolojileri Ticaret Ltd. Şti. | The server hosting the application, database, logs and backups. | All data processed in the service. | Türkiye. | Performance of a contract (KVKK 5/2-c; GDPR 6/1-b); legitimate interest in security (KVKK 5/2-f; GDPR 6/1-f). |
| Cloudflare | Domain name service (DNS); encrypted database backups; storing product images and their backups and serving them from media.catalogtopia.com. | Encrypted backups (Cloudflare cannot read their content); product images; your browser's IP address when an image loads. | Abroad. | Performance of a contract (KVKK 5/2-c; GDPR 6/1-b); legitimate interest in security (KVKK 5/2-f; GDPR 6/1-f). |
| Resend | Sending account confirmation, password, security, team, trial and alert e-mails. | Your e-mail address and the content of the e-mail (e.g. a link, the workspace name). | Abroad. | Performance of a contract (KVKK 5/2-c; GDPR 6/1-b). |
| Google Workspace | Receiving and answering the e-mails you send to our contact address. | Your e-mail address and what you write. | Abroad. | Legitimate interest (KVKK 5/2-f; GDPR 6/1-f). |
| Amazon Web Services | Receiving mail sent to @catalogtopia.com addresses. | Your e-mail address and what you write. | Abroad. | Legitimate interest (KVKK 5/2-f; GDPR 6/1-f). |
| Meta Platforms | Only if you connect it: signing in to your Meta account and reading your catalog information. | Access token and read requests (§6); for catalogs where you chose Catalog management, the product information listed in the Terms of Service. | Abroad. | Performance of a contract, on your instruction (KVKK 5/2-c; GDPR 6/1-b). |
| Google (Merchant Center) | Only if you connect it: signing in to your Google account, reading Merchant Center and the corrections you approve (§8). | Access token, read requests, the product corrections you approve; for catalogs where you chose Catalog management, the product information listed in the Terms of Service. | Abroad. | Performance of a contract, on your instruction (KVKK 5/2-c; GDPR 6/1-b). |
| Shopify | Only if you connect it: reading product data and writing the title, image and price changes you approve to your store (§7). | Access token, read requests, the product changes you approve. | Abroad. | Performance of a contract, on your instruction (KVKK 5/2-c; GDPR 6/1-b). |
When you give us a product feed or image address, our server sends a request to it. Your personal data is not sent in that request; the address's owner sees our server's IP address.
12. Retention
The table below shows how the system actually behaves today; only measured periods or periods configured in the system are given.
| Data | Today |
|---|---|
| Account, catalogue, product and connection data; raw copies of the source; activity records | Kept as long as your account is open. When you delete your account in the application, deleted on the timeline in section 13; in activity records, what identifies you is blanked. |
| The data of a store removed from Shopify | When Shopify's shop data erasure notice arrives (48 hours after the removal), the access key and the store's identifiers are deleted at once. Following Shopify's shop data erasure request, the product records from that store and the image copies belonging to those products, backups included, are permanently deleted within 30 days at the latest of receiving the request. (section 7) |
| Records of writes to Shopify (preview, approval, the images' status on Shopify and the verified order) | No automatic deletion. When a product or an image is deleted, its status record goes with it. |
| The record of Shopify's privacy notices (ID, topic, time, status) | No automatic deletion. The store address and ID are removed from the record once the notice is processed. No customer information is ever recorded. |
| Your data that came from Meta | Deleted automatically 24 hours after we see that Meta removed the connection, and at once on a data deletion request that matches fully (section 6). |
| The record of requests from Meta (kind, time, status, confirmation code) | No automatic deletion. Contains no Meta identifier and no content. |
| Data from a Google connection (access key, connection, links, product statuses, delivery records) | Deleted at once when you disconnect the store's Google connection (section 8); with an account deletion request, those of the workspaces that will be deleted are deleted at the request (section 13). Our supplemental source in Merchant Center stays at Google. |
| The Meta supplementary feed and its delivery records | When the supplementary feed is stopped, the feed is deleted at Meta; the record stays as "stopped" and the delivery records count as withdrawn (removal requested). Deleted with the workspace. |
| Catalog-management consent and send records | Sending stops when management is turned off or the connection is removed; the records are deleted when the workspace or account is deleted. On a Meta data deletion request, the send records that belong to Meta are deleted (section 6). We do not delete the products on the channel. |
| Alerts and daily digest records | No automatic deletion; they contain no product content. Your digest records are deleted when you delete your account. |
| An uploaded CSV file | Deleted as soon as its import ends, whether it succeeded or failed. A file left half-uploaded or never imported is deleted within about 3 hours at the latest. The record keeps only its size, digest, the user who uploaded it and the time. |
| Session | A session unused for 7 days expires; its record is deleted when you sign out. Expired session records are not cleaned up automatically today. |
| Password reset and e-mail verification links | Valid for 1 hour. |
| Two-step verification key and recovery codes | Until you turn two-step verification off or delete your account; turning it off deletes both. Making new codes deletes the old ones. |
| Security events, e-mail change and account recovery records | Until your account is deleted; deleted with it. An e-mail change link works for 24 hours, the dispute link sent to the old address for 7 days. |
| Failed sign-in attempt counters | At most 24 hours; up to 1 more day in the server's disk log. Kept only with a secret-keyed digest (HMAC-SHA-256) of the e-mail address or of the account's identifier; neither the address itself nor an IP address is written. |
| Request rate counters | To prevent abuse of sign-in, sign-up, password reset, two-step verification, invitation, file upload, account deletion and similar requests, a secret-keyed digest (HMAC-SHA-256) of your IP address is kept in a 1-minute counter; for the security reports your browser sends, at most 10 minutes. The IP address itself is not written. For the requests you make while signed in, your account's internal identifier is kept in a 1-minute counter for the same purpose. These counters stay up to 1 more day in the server's disk log. |
| Product images | An image you remove from a gallery, or one the source no longer lists, is deleted from the main store after 30 days; it stays in the media backup for at most 30 more days. From removal to full deletion the total can therefore be up to about 60 days. |
| Backup of product images | Daily; in the same backup store as the encrypted database backups (Cloudflare R2), in a separate area. An image deleted from the main store stays in the backup for at most 30 days. |
| Server logs (nginx) | Deleted after 14 days. |
| System logs | No time limit; rotated by a disk size limit. The application writes no e-mail address, IP address or Shopify notice content to these logs. The database server's own log file (error messages and the access records below) is deleted after 30 days. The database is set not to write the content of a refused row into its error messages; the text of a failed query, and a value of the wrong format, can still appear in the error log. |
| Records of our team's database access | Our team reads the database by hand only through a separate, read-only access role and pre-reviewed query templates. Every query of that role is written, with its time, the role used and the database's name, to the database server's own log file; the role cannot switch this off. The records contain the text of the query, not its result; queries carry no e-mail address, name, telephone number or address, only internal identifiers. A log file is deleted 30 days after its day (on the 31st day at the latest). |
| Encrypted database backups | Daily backups are deleted on the server after 7 days; the same clean-up job also covers the copies in Cloudflare R2. |
| Preferences in the browser (catalogtopia.com) | In your browser until you delete them. |
13. Deleting your data
You can delete your account in the application: Settings → Account → Delete account. You are asked to enter your password again before deletion. If two-step verification is on, your code is asked too; after the request your sessions on other devices end.
- What is deleted: your name, e-mail address, password hash, sessions and memberships. Workspaces in which you are the only member are deleted in full: stores, catalogues, products, product images, sources, connections and activity records.
- Workspaces that have other members are not deleted. Only your membership is removed. If you are the only owner of such a workspace, ownership has to pass to another member before deletion: under Settings → Team, to an active Admin, with your password (and your code if two-step verification is on).
- Shopify, Meta and Google access keys, and the passwords of password-protected feeds, belonging to workspaces that will be deleted are deleted from us at once, when you make the request; with the Google connection, the product statuses read from Google and the delivery records go too. Today we do not revoke the permission at Google: a single revocation at Google removes every permission your Google account gave Catalogtopia and could break your other connections too. You can remove it yourself on your Google Account's permissions page (myaccount.google.com/permissions).
- 7 days to undo: within 7 days of the request you can sign in and choose "Cancel deletion". If you cancel, your data stays; you will need to reconnect Shopify, Meta and Google and enter feed passwords again. The statuses read from Google are read again once Google is reconnected.
- Permanent deletion at the end of day 7: database records and product images in the main store are deleted at once (the 30-day wait for images removed from a gallery does not apply on this path). Copies in the media backup are gone within 30 days at the latest, encrypted database backups within 7 days. From the request to full deletion therefore takes at most about 37 days.
- Activity records (security records): the rows are not deleted, but everything that identifies you is blanked: who performed the action and the details. Only the kind of action and its time remain.
- Deleting your account does not remove the app from Shopify or the business integration from Meta. You can remove those separately in your Shopify admin and in Meta's settings. Images already sent to Shopify stay in your Shopify store.
You can also send your deletion request by e-mail, from your account's e-mail address to info@highonemedia.com. We act on a request sent by e-mail only when it comes from the e-mail address registered to your account; we do not act on a request from another address until your identity has been verified. We answer requests made by e-mail within 30 days at the latest (KVKK Art. 13).
Your Shopify store's data also has Shopify's own route. When you remove the app in your Shopify admin, Shopify sends us the shop data erasure notice 48 hours later, and deletion starts by itself as described in section 7. Copies on Shopify of images sent to Shopify stay on Shopify; you can delete them in your Shopify admin.
What can and cannot be deleted from the application today, and how to make the request: Data Deletion Instructions.
Reports and export. If Reports is turned on for your workspace, you can download a report on the Reports screen as a CSV file. Only people with the "analyst" role or a higher role in your workspace can do this. The file holds that report's table from the screen, from your own workspace's data only; depending on the report type, it also has an ISO-format date column or a rule-code column:
- analysis dates and catalogue health scores;
- issue counts per rule;
- Auto-Fix results: the product name, the product's ID in your store, the status and the delivery status per channel;
- a summary of your catalogues.
The file has no column for people's names or e-mail addresses. Access keys, Catalogtopia's internal IDs, image links and free-text error messages from Meta or Google are not written to it either. Product names and product IDs are copied as they are in your store; if personal information was entered in those fields, it will appear in the file too. The file is not kept on our servers. Each export is written to the activity records. The record shows who downloaded which report, for which catalogue (for the catalogue summary: for the workspace), when, for which date range, how many rows, and whether our server finished sending the file; it never holds the file's content. The retention of activity records is in section 12.
In an agency workspace, members see and can export only the data of the clients they have access to.
14. Your rights
Under KVKK Art. 11 you have the right to learn whether your personal data is processed and, if so, to request information about it; to learn the purpose of processing and whether it is used accordingly; to know the third parties it is transferred to; to request its correction if it is incomplete or wrong, and its deletion or destruction; to request that these actions be notified to the recipients; to object to a result against you arising from analysis by automated systems; and to claim compensation for damage caused by unlawful processing.
If the GDPR applies to you, you also have the rights of access, rectification, erasure, restriction of processing, data portability and objection (Art. 15–21), and the right to lodge a complaint with the supervisory authority of your country.
Send your requests by e-mail to info@highonemedia.com from the e-mail address registered to your account; we do not act on a request from another address until your identity has been verified. Your request is concluded free of charge within 30 days at the latest. If you are not satisfied with the outcome you may complain to Türkiye's Personal Data Protection Board (KVKK Kurulu).
16. Children
Catalogtopia is a service for businesses; it is not intended for people under 18 and we do not knowingly process children's data.
17. Changes
When we update this policy we change the "Last updated" date at the top of the page. We also notify significant changes to your account's e-mail address.
18. Contact
For every privacy question and request: Highone Group LLC, 1209 Mountain Rd Pl NE Ste 13537, Albuquerque, NM 87110, USA — info@highonemedia.com.
Our policy documents
| Document | Last updated |
|---|---|
| Privacy PolicyHow personal data is collected, used and protected. | |
| Terms of ServiceThe terms that apply when you use Catalogtopia. | |
| Data Deletion InstructionsHow to ask for your data to be deleted. | |
| Cookie PolicyCookies and preferences stored in your browser. |


