Privacy Policy
o-early is a browser extension that adds an overlay of user-configured metrics to supported trading platform pages. We process data necessary for sign-in, access management, payment verification, invitation rewards, and extension features. We do not sell personal information or use page data for advertising.
Page data read by the extension
When you enable the feature on a supported trading platform page, the extension reads public trading metrics already loaded by the page to calculate your configured strategy and show color progress on the corresponding cards. Market metric values are calculated locally and are not uploaded to our servers; uploads of technical failure counts are described separately below. The extension does not read passwords, form contents, cookies, private messages, or wallet private keys. Turning off the overlay stops its display; adapters may continue processing supported metrics locally while the page remains open. Page memory is released when you leave the page.
The extension observes the page's real-time data channels in the page's main execution context to obtain metrics the page already displays. It does not send trading requests, click trading buttons for you, or change your account state.
Data we process
Google sign-in provides your account identifier, email address, display name, and profile picture to create an account, complete device sign-in, and sync access. The server stores session tokens, device authorizations, access status, orders, and transaction identifiers needed for payment verification. Website wallet payments also store the payer address and unsigned and signed transaction contents for prechecks, submission recovery, and duplicate-payment prevention, retained with order financial records. These do not contain wallet private keys. The extension does not receive Google access tokens, refresh tokens, or ID tokens.
The extension locally stores short-lived sign-in session tokens, pending device sign-in information, cached access status, language preferences, and strategy settings. Strategy settings are saved through Chrome Storage; page trading metrics are not stored on the server. The payment website keeps signed transactions in the current tab's session storage to resume the same submission after a refresh; closing the tab clears this storage.
Free-access whitelist
Approved free access matches a verified sign-in email against an administrator-managed whitelist. An administrator may enter an email you provide and an access note before registration. The service stores the normalized email, note, creation time and operator, plus audit records of access additions and removals, to grant access and review changes. The extension receives access status, not the full list or administrator notes. The whitelist is not disclosed to trading platforms or other users.
The whitelist is separate from sign-in accounts and is retained until an administrator removes the entry. Deleting an account does not automatically remove free-access eligibility; registering again with the same verified email may restore it. Administrator removal deletes the current entry. Change audit records containing the email, note, operator and time are not automatically deleted with the account or entry and currently have no automatic expiry. Contact the email below for requests to inspect, remove or delete whitelist and audit data.
Automatic rendering failure diagnostics
When an enabled overlay on a visible supported listing page detects missing cards or parsing failures, the extension sends the platform, failure reason, extension version, card count, parsed count, rendered count, cache item count, listing page type, random event identifier and occurrence time to o-early.com over HTTPS to identify compatibility problems. Reports do not include page URLs, token addresses, market metric values, strategies, wallets, session tokens or Google account details. Requests create normal network connection information; the endpoint hashes the source IP for short-term rate limiting.
The server aggregates diagnostics by platform, failure reason, version and UTC date, storing event totals, technical counts and server-side first and latest receipt times. The diagnostic table does not store random event identifiers or client occurrence times. IP hashes used for rate limiting have a 120-second KV expiry. If operations alerts are configured, the platform, reason, version, technical counts, aggregate fingerprint and date are sent through Resend to an operations mailbox. Aggregate diagnostics and alerts currently have no automatic deletion period and are used only for compatibility troubleshooting. Contact the email below for related data requests.
Invitation and reward data
When you generate an invitation code, we store its account association, fixed code, Solana payout wallet, and creation time to restore your sharing link and settle rewards. The payout wallet cannot be changed through self-service after generation. Strategy configurations remain local to the extension and are not uploaded through the invitation feature.
Orders created with an invitation code store that order’s code, original price, discount, and payment amount. Eligible payments create commission records containing the order, sharer, payout wallet, amount, and settlement status. We also record review actions, payout batches, and public on-chain signatures for review and Solana settlement. The administration service does not store wallet private keys. Invitation codes do not automatically bind a buyer account or create an expiring referral relationship.
Trial abuse prevention
Google account identifiers are processed with HMAC-SHA-256 using a separate key. After account deletion, an irreversible hash is retained for up to 12 months to prevent repeated trial claims. IP addresses in security events are also stored only as hashes for up to 90 days, with restricted use and access.
Third-party services
Sign-in and account services are provided through Google OAuth, while extension APIs and account data are provided by o-early.com. Payments are completed through a Solana wallet that you actively choose to use. We receive only the public transaction signature and payment status necessary to verify an order, and do not receive wallet private keys. Third-party services process data under their own privacy policies.
Retention periods
Active session tokens are cleared when they expire or you sign out. Account information and usable invitation codes are deleted after an account deletion request is completed. Access, order, and necessary commission financial records are retained for 24 months after the related access ends for payment reconciliation, refund disputes, and financial records. Irreversible trial abuse prevention hashes are retained for up to 12 months, and hashed security events for up to 90 days, then deleted.
Data deletion
You can delete your account on the account page after reauthenticating and confirming again. Deletion revokes all website and extension sessions, terminates unexpired access, and removes account information, device authorizations, usable invitation codes, and trial security events linked to you. Necessary order, payment, and commission financial records are unlinked from the internal account and retained for the periods above; they may include a historical invitation code, payout wallet, and public chain transaction identifiers. Trial abuse prevention hashes are retained as stated above.
Account deletion does not clear the independent whitelist eligibility, access-change audits or aggregate diagnostics. Their retention and request handling are described in the sections above.
Contact
For privacy and account deletion matters, contact feedback@o-early.com.