Privacy Policy
Oinker is a paper-trading simulator for memecoin terminals. It lets you practise trading with simulated funds on token pages you open yourself. This policy explains what stays on your computer, what reaches our server, and what never gets collected at all.
What Oinker never asks for
Oinker does not request, read, store or transmit:
- private keys, seed phrases or recovery codes;
- wallet passwords or any other credentials;
- your name, email address or payment details.
Every trade you make in Oinker exists only as a record in your own simulated account. No blockchain transaction is ever signed or broadcast.
What is stored on your computer
- Your simulated account: starting balance, open positions and trade history.
- Your settings: buy and sell presets, slippage, fees, panel position and appearance.
- Price snapshots for coins you hold, so the counter keeps working when a data source is briefly unavailable.
You can erase all of it at any time: remove the extension, or reset the account on its settings page.
What is sent to our server
Oinker syncs your practice account between your devices through our own backend at oinker.fun. The following is sent there:
- your simulated trades and the resulting positions and PnL;
- the token addresses of coins you open, so prices can be prepared for them;
- your extension settings, so they follow you to another computer;
- a random device identifier generated on first run.
The device identifier is a random string, not an account. We do not ask you to register, and we have no way of connecting it to a person.
Usage statistics
To find bugs and see which features people use, Oinker sends a small usage report to oinker.fun every 10 minutes. It contains:
- the extension version, the browser and operating system name and the interface language;
- which supported platforms (Axiom, GMGN, Padre, FOMO, Photon, Jupiter) and networks you open coins on, as counts;
- counts of actions: simulated buys and sells and their total size, trades cancelled by slippage, refused trades by reason, and features used (for example take-profit and stop-loss, alerts, chat messages sent);
- the token addresses of coins traded and how many trades each had (these are public addresses; the server keeps only a total per coin, not per device);
- error codes with the part of the extension where they happened and a short description. Wallet addresses and links are removed from descriptions before sending.
The report never contains wallet addresses, chat messages, journal notes, the pages you visit or anything you type. It is linked to your random device identifier and, if you set up a friends profile, the server can match it to your chosen nickname. The developer sees these numbers in a private admin view to fix problems and may block a device that abuses the service. Reports are kept for 30 days. Request logs on the server (which endpoint, the result and how long it took, without request contents) are kept for the same period.
You can turn the report off at any time: Settings → “Send usage stats”.
Friends chat
Friends chat lets you message the friends you have added in Oinker: coins (Send CA), text, pictures, GIF files and GIFs from GIPHY.
- Encryption: every message is encrypted on your device before it is sent. Our server stores and forwards encrypted data only.
- What the server keeps: encrypted messages until each recipient's device receives them (at most 7 days); encrypted pictures until they are downloaded (at most 7 days); an encrypted copy of your chat history (the last 30 days, up to 500 messages) so it can be restored after you reinstall the extension; and your chat keys, sealed with our server key. To deliver messages the server also sees which device writes to which, when, and the approximate size.
- Who can read it: the friends you chat with. Because your chat keys are held in escrow on our server, we are technically able to decrypt your chat history. We do so only to restore your chat on a new device after you confirm through Telegram that it is you, or when we are required to by a valid legal request from a competent authority. We do not read messages for any other purpose.
- Trading websites you have open cannot read the chat: it runs in an isolated extension page.
- GIFs from GIPHY: when you search for a GIF, your browser sends your search text directly to GIPHY (
api.giphy.com). A GIF you send travels inside the encrypted message as its GIPHY identifier only; each friend's browser then loads it from GIPHY (media.giphy.com), so GIPHY sees the IP address of everyone who views it. GIPHY's own privacy policy applies to these requests. GIFs you mark as favorites are stored on your device and in your encrypted history copy. - Deleting: you can delete your own messages for everyone. Removing the extension erases the chat from your computer; server copies expire as described above, and a history copy that has not been updated for 180 days is deleted.
What we do not do
- We do not sell your data and never will.
- We do not use it for advertising, or for credit and lending decisions.
- We do not share it with third parties, apart from the data sources listed below, which your browser contacts directly, and lawful requests described in Friends chat.
Third-party data sources
To show prices and token information, your browser requests data from:
lite-api.jup.agandapi.dexscreener.com— token prices and metadata;frontend-api-v3.pump.fun— newly launched tokens;api.mainnet-beta.solana.com— token supply;- Google Translate and MyMemory endpoints — only when you use the optional translation feature, and only for the text you chose to translate.
api.giphy.comandmedia.giphy.com— only when you search for, send or view GIFs from GIPHY in Friends chat (see above).
These services receive the request itself — a token address, or the text to translate. They receive nothing about your account.
The platforms Oinker runs on
Oinker adds its panel to token pages of the trading terminals it supports. On those pages it reads the price and token data the page is already displaying. It does not read your accounts on those platforms, does not touch their trading forms, and is not affiliated with any of them.
Remote code
All code ships inside the extension package. Oinker loads no external scripts and evaluates no remote strings.
Children
Oinker is not directed at children under 13 and does not knowingly collect any data from them.
Changes
If this policy changes, the date at the top changes with it. Material changes are announced on the extension's Chrome Web Store page.
Contact
Questions about this policy: egachmo@gmail.com