Privacy policy

This Privacy Policy describes how Instorax collects, uses, stores, and shares information when you visit the storefront, switch theme or language, search the catalog, subscribe to launch updates, or contact support on WhatsApp, email, or Telegram. It is written for a static catalog of social, mail, and AI accounts. Last updated 8 November 2026. If you do not agree, please do not use the site or send an order.

Instorax is the controller of information we collect through this website and through the order channels we publish. Third parties such as Google Translate, payment rails, and messaging apps (WhatsApp, email hosts, Telegram) are independent controllers of data you give them directly. We do not sell your personal information as a product. We use it to run the catalog, answer tickets, deliver SKUs, and improve the storefront.

1. Scope

This policy covers home.html and every catalog, article, About, FAQ, Blog, Contact, Refund, Terms, and Privacy page on the Instorax static site. It covers the header search box, the theme switch, the language control, the footer newsletter field, and messages you send to published support channels. It does not cover destination platforms (Instagram, Gmail, Discord, ChatGPT, and others) after you receive credentials. Those services have their own policies.

It also does not cover websites you reach by mistake that copy our logo. Check that you are on the Instorax pages you bookmarked. We will never ask you to paste order files into an unofficial form.

2. Information you provide

When you use Contact or the footer form, you may send a name, email address, and message. When you order, you send a SKU title, quantity, payment reference, and whatever identity the messaging app already attached to your account. We use that thread to confirm spec chips (2FA, PVA, mix IP, year, submail), to deliver files, and to run replacements under the Refund policy.

You may also type a search query such as “Gmail” or “Discord.” Search is processed in the browser and on our pages to help you find listings. Avoid putting passwords or credential files into the search box or into public comments. Use the order thread for sensitive files.

3. Information collected automatically

Like most sites, our pages and any embedded tools may receive technical data: browser type, language, approximate time, pages viewed (for example Home, Gmail PVA, an article, FAQ), and device class (desktop or mobile). We use this to keep layouts working — four article cards on a large screen, two on a small screen — and to debug broken links.

The theme control stores a preference (light or dark) in localStorage under a key used by Instorax. The language control stores your choice (English, 中文, Portuguese, Russian) in localStorage and may set a translation cookie so Google Translate can keep the page in that language. These preferences stay on your device unless you clear storage.

4. Cookies and similar storage

Instorax uses localStorage for theme and language. Google Translate may set a googtrans cookie so a selected language persists as you move from Home to a product page. If you use a live chat widget where it is present, that vendor may set its own cookies. Payment processors and messaging apps set cookies on their own domains, not on our static files.

You can block cookies in your browser. The catalog will still render. Translation and some third-party widgets may not remember state. Clearing localStorage resets theme and language to defaults.

5. Google Translate

The header language menu loads Google’s translation scripts. If you select 中文, PT, or RU, page text is translated in the browser. Google may process page content to provide that service under Google’s own terms. SKU titles you paste into an order should remain the original English card names so support can match Gmail, Instagram, Discord, and the rest of the live list. Translation is a reading aid, not a change to the contract language of a listing.

6. How we use information

We use information to: display the catalog; remember theme and language; respond to Contact and newsletter requests; match an order line to a card; deliver credential files on the same thread; process replacements and refunds; prevent abuse of support channels; and keep legal records required for digital supply. We do not use order threads to train public AI models. We do not publish your ticket on Blog or social comments.

Launch-update emails, if you subscribe, carry product news and offers. You can stop them by replying on that email thread or using Contact and asking to be removed from the list. Transactional messages about an open SKU are not marketing; we still send those until the order is closed.

7. Sharing

We share information with people and tools who need it to complete your request: support specialists on the desk, payment processors for the rail you chose, and messaging platforms you already used to write to us. We may share information if required by law, to protect Instorax or other buyers, or to complete a replacement that you asked for.

We do not sell lists of emails or order titles. We do not share credential files with other customers. If a specialist must move a ticket from WhatsApp to email, we will say so on the original thread rather than silently forwarding your pack.

8. Credential files and order secrets

Files we send you are the product. You must store them securely. We retain enough of the order record (SKU, quantity, timestamps, payment reference) to handle a refund or replacement claim. We do not keep extra copies of delivered files longer than needed for that desk. If you forward a pack to a teammate, you are responsible for that teammate’s handling. Instorax is not your internal password manager.

Never post delivered files in a public Discord, a screenshot on social media, or a search box. If a pack is exposed publicly, it may be unusable and may fall outside replacement, because the defect is disclosure after delivery rather than a catalog mismatch.

9. Newsletter and Contact forms

The footer form asks for an email to send launch updates. Use a mailbox you control. We use the address only for that list and for replies if you wrote a question in the same form. Contact page messages are read by support. Include a SKU title if the message is about an order; do not paste full credential dumps into the first Contact note if a safer order thread already exists.

10. Retention

Theme and language data stay in your browser until you clear them. Newsletter emails stay until you unsubscribe. Order threads stay as long as needed to finish delivery, replacement, refund, accounting, and dispute response. We then reduce what we keep to the minimum needed for legal records. Server logs, if any, are rotated on a short cycle unless they are part of an open security review.

11. Security

We use HTTPS where the site is served over a proper host, dual-theme pages that do not need extra account passwords to browse, and a rule that specialists confirm SKU names before sending files. No method is perfect. You should use unique passwords on your own mail and messaging accounts, avoid public Wi-Fi when downloading packs, and inspect files in the delivery window described in the Refund policy.

If you believe a message that uses our brand is a phishing copy, do not enter payment details. Compare the URL, write to the Contact channel you already used, and ask us to confirm. Instorax will not ask you to install unknown desktop remote-control software to “complete a refund.”

12. International visitors

The catalog is used from many countries. Information may be processed where our specialists, email host, or translation provider operate. If you are in a region with extra privacy rights (access, correction, deletion, export, objection to marketing), send a request through Contact with “Privacy request” in the first line. We will need enough detail to find your email or order thread. We may refuse requests that would expose another customer’s pack.

Google Translate, messaging apps, and payment rails may move data across borders under their own rules. Read those products’ policies if that matters to your organisation’s compliance program.

13. Children

The storefront is aimed at professional buyers. We do not knowingly collect personal information from children. If you believe a child sent us an order or a newsletter signup, contact us and we will delete the record we control.

14. Third-party pages

Links to Instagram social profiles, Telegram, YouTube, X, Gmail product pages, ChatGPT, and other destinations are for navigation. Their privacy terms apply when you leave Instorax. Embedded logos and chips on our cards are labels for SKUs, not a claim that those platforms endorse the listing.

15. Your choices

• Browse without sending an order.
• Leave the language on English so Google Translate is not invoked.
• Clear localStorage to drop theme and language.
• Unsubscribe from launch updates.
• Ask support to close an order thread once delivery is complete.
• Request access or deletion of Contact form data we hold.

Some records must stay for refunds, chargebacks, and accounting. We will say so if we cannot delete a payment reference that is tied to a completed digital supply.

16. Changes

We may update this Privacy Policy when the catalog, translation, or support stack changes. The date at the top will change. Continued use of the site after an update means you accept the revised policy for new visits. For open orders, the policy in force at payment still guides that ticket unless a law requires otherwise.

17. Contact for privacy

Use the Contact page or the email / WhatsApp / Telegram desk published for orders. Write “Privacy policy” in the first line. Do not attach unrelated credential files to a privacy request. If your request is about a specific Gmail or Discord SKU, include the title and date only.

This policy should be read with the Terms of Use and the Refund and Replacement Policy. Together they explain how Instorax runs a spec-led catalog without turning your ticket into public marketing copy.

18. Search, theme, and language data in practice

When you type Gmail, Discord, or Instagram into the header search, that query lives in the page request and in your browser history. Do not paste passwords there. The dark and light theme switch writes only a preference flag on your device. The language menu may call Google Translate; you can stay on English and avoid that call. None of these controls are used to build a public profile of you.

If several people share a computer, the stored theme and language will follow the last user of that browser. Use a private window if you need a clean catalog visit. Clearing site data removes Instorax localStorage keys and translation cookies we set for language persistence.

19. Order-thread hygiene

Support reads SKU titles, quantities, and payment references so a Gmail-with-submail line is not mixed with a Discord age line. We do not need your destination-platform backup codes in the first message. After files arrive, keep the thread until the inspection window in the Refund policy closes. Then you may ask us to stop using that thread for marketing; transactional closure notices may still be sent.

Agencies should name one operator on the channel. If a teammate takes over, say so on the thread before we send a replacement pack. Privacy requests from a new address about an old Telegram identity will need enough dates and SKU names for us to connect the records without exposing another customer.

20. Analytics and live widgets

If a live chat or similar widget is present on a page, that vendor processes the chat text under its own policy. Do not paste full credential files into chat unless a specialist on an existing order thread asks for a specific line to verify a Gmail or Instagram mismatch. We prefer the original WhatsApp, email, or Telegram order channel for packs.