Draft written from how Chomodo currently works. It is pending legal review and may change before live payments are enabled.
Privacy Policy
This page lists what Chomodo stores about you, why, which services help process it, and how long some records are kept. It is based on how the platform works today.
1. Data we store
Account
- Name, email address, and email verification status. Passwords are stored only as hashes. If you use Google sign-in, we use the identity Google returns (a Google account identifier, your email, and your name if provided).
- Sign-in sessions (stored as hashed tokens) and short-lived verification and password-reset tokens.
Maker profile
- Seller type, contact name, studio name, country, description, support email, optional website, logo and banner images, and any website ownership check results. Most of this is shown publicly on your maker page and listings.
- For paid hosted sales, payout details (bank account, PAN, phone) are entered in Chomodo and sent to Cashfree to create your seller account. Chomodo stores only the resulting Cashfree seller ID and status, not the bank or PAN details.
Purchases and payments
- Orders with the product, price breakdown (price, Chomodo fee, seller share), currency, Cashfree order and payment IDs, and status. The same applies to listing fees, listing packages, ad payments, and gold verification payments.
- Your entitlement, download records, and license keys. License keys are stored encrypted.
- Payment card and bank details for a purchase are handled on Cashfree's checkout, not stored by Chomodo.
Content and activity
- Reviews, community posts, replies, poll votes, likes, follows, saves, wishlist items, collections, group memberships, event RSVPs, feedback, and reports you file (reports are visible only to staff).
- Support cases and messages, including any order you link to a case.
- Saved drafts of listing, maker profile, and pricing forms, so you can return to them.
- Email preferences for product and event updates and the weekly digest.
Usage and measurement
- Product views are counted once per visitor, product, and day, using a hashed key built from a visitor cookie. A record holds the day, the traffic source, and, for visits from another website, only that site's host name. A view that came from search can include the sanitized search term. Bot traffic and views of your own product by you are not counted.
- Recently viewed products are saved for signed-in members.
- Outbound clicks to a maker's own website are counted with a hashed key, not your identity.
- Ad impressions and clicks are counted with a hashed key per visitor and ad.
- Search telemetry keeps a normalized hash of the query, its length, and the number of results, not the raw query text.
- Rate limits use your user ID, or your IP address when you are signed out, in short-lived records.
2. Cookies and local storage
| Name | Purpose | Lifetime |
|---|---|---|
appagora_session | Keeps you signed in. Not readable by page scripts. | Up to 30 days |
agora_visitor | Random ID used only to avoid double-counting product views and ad impressions. Not readable by page scripts. | 365 days |
| Google sign-in state | Protects the Google sign-in round trip. Set only if you start Google sign-in. | 10 minutes |
Your browser's local storage holds your compare list and unsent form drafts on your own device.
3. How we use data
- To run your account, show listings and community content, process payments, deliver downloads and license keys, and review listings and uploads.
- To rank and recommend software: reviews, purchases, saves, referral clicks, launch freshness, and an active gold plan feed the ranking. See how gold verification and sponsored placement relate to rank.
- To show makers analytics about their own products, ads, and campaigns, such as views, sources, clicks, and spend.
- To send account and transactional email, and optional product, event, and digest email.
- To prevent abuse and fraud: rate limits, moderation, click and ad-fraud checks, and keeping an audit trail of admin actions.
- To resolve payment and delivery problems, including comparing our records with the payment provider's.
4. Who processes data for us
| Provider | What it does for Chomodo |
|---|---|
| Vercel | Hosting, and cookieless page-view counts (page address, referrer, country, browser and device type). No cookies are set and visitors are not identified across days. |
| MongoDB Atlas | Database for accounts, catalog, orders, community, and support records. |
| Cashfree | Payment processing, seller payout accounts and split settlement, and payment webhooks. Cashfree receives the details needed to process a payment and to onboard sellers. |
| Cloudinary | Storage of images and installer files. |
| Brevo | Sending account, purchase, product, event, and digest emails. |
| Sign in with Google, only if you choose it. | |
| OpenAI | Optional AI search. Listing text is turned into embeddings for matching, and AI-assisted search can send the text of your search to interpret it. |
| LiveKit | Live webinar rooms. Your user ID, display name, and role in the room are shared when you join. |
| ClamAV | Malware scanner that checks uploaded installers. |
Optional providers are used only when they are switched on for the platform. Each provider handles data under its own terms.
5. What other people can see
- Public: your maker profile and listings, reviews and posts you publish, your display name on them.
- Not public: your email address, payment details, support cases, reports you file, saved items, and library.
- A hosted-purchase review shows a "Verified buyer" label, not your order details.
6. Email
We send verification, password reset, password-change, and sign-in alert emails when those actions happen. Purchase receipts and seller sale notices are sent when a payment completes. Product and event updates and the weekly digest are sent only if you have opted in.
7. How long we keep data
- Sign-in sessions expire after 30 days. Verification and reset tokens, rate-limit records, and Google sign-in state expire automatically.
- Recently viewed items are kept for 90 days. Outbound click records are deleted after 90 days. Product view records are deleted after 400 days.
- Orders, payments, and other financial records are preserved. Corrections are added as new entries; original charges are not edited, so the record can be reconciled with the payment provider.
- When you delete a post or reply it is marked deleted and removed from public pages. Moderation actions are kept in an audit log.
- For other records, no automatic deletion period is set at present.
8. Your choices
- Edit your maker profile and preferences in your account, delete your own posts and replies, and sign out to end a session.
- Download a copy of your data as a JSON file, or delete your account, in Account settings. The download covers your account details, community profile, posts and replies, reviews, orders, library and license keys, saved items, follows, email preferences, and support cases.
- Deleting your account anonymizes it (your name, email, password, and Google sign-in are removed), signs you out everywhere, deletes your community profile, and removes your posts and replies from public pages. Your reviews are no longer shown publicly, though their star ratings still count toward product averages. Orders, entitlements, license and download records, reviews, and audit and financial records are kept for legal and accounting reasons. Accounts that are suspended, have staff access, have listings that are live or in review, or have payouts pending can't be deleted this way.
- To ask for a correction or for anything else to be removed, open an Account case in support.
- You can clear the
agora_visitorcookie in your browser at any time. Product views will then be counted as a new visitor.
9. Security
Passwords are hashed, session and visitor cookies are not readable by page scripts and are marked secure in production, license keys are encrypted, uploaded installers are quarantined and malware scanned before release, and administrative changes are logged. No system is perfectly secure, so please use a strong, unique password.
10. Contact
Open a case at /support (sign-in required) under the Account topic for privacy questions and requests.
