Privacy

Stored on your device

Without an account you can read the public pages and free guides and try the homepage examples; guests have no saved progress. The theme remains a device preference. Older private browser records stay intact and are not automatically copied into an account.

When you sign in, account progress loads from the server and changes sync to your account. An account-specific recovery draft stays on the device for interrupted saves. Settings Data contains manual file import and export. Named whiteboards and HLD prompt drawings save to your account, with separate account-specific recovery drafts. Drawings made while signed out stay in the open tab; older device board drafts remain available for explicit import.

Anyone who can use the same browser profile may be able to read locally stored records. Clearing site data removes local records and pending drafts, but it does not delete progress already saved to an account.

Network requests

• Handle sync: when you request it, the app sends the public username to the relevant judge or a read-only Arise proxy. The proxy asks LeetCode for public profile counts and recent accepted submissions. Codeforces requests go to its public API. AtCoder sync sends the handle to the independent AtCoder Problems service at kenkoooo.com, which indexes public submissions.
• Exercises: Python exercises run in your browser, which downloads the Python runtime from the jsDelivr CDN the first time. Running C++ sends your source code to an isolated Vercel Sandbox machine with no network access, which is discarded after the run. Arise keeps daily counts and durations of compiler runs, not the code.
• Site content: your browser requests pages, artwork and video files. The serving infrastructure can receive request information such as an IP address, browser details, requested URL and time.
• External links: a judge, employer reference or source link opens that provider's site, governed by its own privacy policy.

The current application does not include advertising trackers or a marketing analytics SDK, and it does not require a judge password, session cookie or private submission history. Judge services may rate-limit or reject requests.

Server logs record errors with the route, a random error ID and the kind of error, without your email address, progress or what you typed. Your browser may also report blocked page resources, with the page path and the blocked address. To limit abuse, Arise counts bug reports per network, and C++ runs and LeetCode syncs per account, using keyed hashes. Counters older than two days are scheduled for batch cleanup; delayed or backlogged runs can retain them longer.

AI hints and resume reviews

When you ask for a hint, Arise sends the exercise context, your code, test results, question and relevant earlier hints to its AI provider. For resume review, Arise sends the text you paste or extracts text from your PDF and sends that text. These requests include personal information you put in the submission. Remove information you do not want processed before submitting.

Depending on the server configuration, these features send data to OpenAI or Anthropic. The Anthropic connection may use Vercel AI Gateway. Provider processing and retention rules apply. OpenAI requests set application-state storage off; this setting does not establish zero retention of provider security logs.

Arise processes resume PDFs and extracted text in memory. It saves the generated report, a submission hash and usage metadata in your account, without saving a separate original resume file or full extracted-text record. Reports can quote or infer personal information from your resume. Deleting a report clears its content and submission hash; a minimal usage record remains to enforce the rolling review limit.

Hint records store your question, generated hint, a hash of submitted code, feedback and usage metadata with your account. The submitted source code is not saved in that hint record. An active hint thread displays earlier hints for six hours; this display window does not delete stored records.

Completed resume reports and hint records currently have no automatic age-based deletion. Account deletion removes these account-linked records. You can delete a resume report from its page. Deleted-report usage rows older than 24 hours are cleared when a later review request reserves capacity; that cleanup has no guaranteed completion time. Account-data requests use the contact channel below.

Optional usage measurement

If you allow optional measurement, Arise records page and sample events, a random browser token, broad learning goal and source category. The server records receipt times, links signed-in events to your account and adds your saved pricing region. It stores a keyed hash of the browser token. It collects no code, resume text, raw campaign names or advertising identifiers.

The default is off. Your choice lasts 90 days on this browser. You can stop collection and request deletion below; a failed deletion can be retried while collection stays off. Events are scheduled for deletion after 90 days. Unused browser and revocation hashes are scheduled after 91 days. Daily deletion runs in batches, so a backlog can take further runs. Account deletion removes signed-in optional events. Financial records and essential service logs follow their separate policies.

Cards and exports

Exporting progress creates a file on your device. Treat it as private: it can contain your practice history and linked handles.

A player-card link contains a small self-reported snapshot in its URL path, including appearance choices and summary counts. Arise's server and social preview services can read that snapshot to render the shared page or a link preview. You can choose whether to include your name and college. The link uses library artwork. Personal uploads, connected judge handles and full solve history are not automatically copied from your account.

Profile links you enter, such as GitHub, LinkedIn, X, Clist and a personal website, are stored with account progress and start private. A shared card includes only links you mark public, and only when identity sharing is on. Shared links become part of the card snapshot. Changing a saved profile link does not remove it from cards already shared.

Anyone who receives the link or image can view, save and forward it. A recipient's copy cannot be recalled by deleting your local record. PNG export is generated in your browser. Native sharing passes the image to the app you select, under that app's policies.

Your choices

• Change player-card details and appearance in Profile settings.
• Export, import or reset progress in Settings Data. You can remove local records using your browser's site-data controls.
• Remove a linked handle in Connections to stop future sync requests for it. This does not change the judge's public record.
• Turn off name and college before sharing a card. Send only information you intend recipients to keep.

Accounts and payments

Accounts store your name, email address, sign-in methods, session records and progress in a PostgreSQL database hosted by Neon. Email/password accounts store password hashes. Google sign-in can store encrypted provider tokens. Better Auth handles authentication and session cookies. Session records can include an IP address and browser details.

Pricing stores the account's first trusted server country, price region and assignment time. This pricing record stores no IP address. Later browser preferences cannot change the assigned currency.

Email/password signup does not verify email ownership. Google can confirm the email returned by its provider. If you ask for a password reset, Arise sends a single-use link to the account email through Resend, an email delivery service; the link expires after 30 minutes. Signing out ends that session; it does not delete the account. Expired session records are scheduled for daily cleanup in batches. To ask for account deletion or a copy of your account data, follow Questions below and include the account email so the record can be identified.

All-time and weekly leaderboards are public, including to visitors who are not signed in. Joining is optional and saves your chosen board name with your progress. Public entries show that name, your built-in avatar and cosmetics, level, assessment grade, solve count and XP. They do not include your private account email, linked handles, college or uploaded photo. Leaving removes your entry; copies others have already saved cannot be recalled.

Private classes store the class name, membership, your chosen display name, sharing preference, check-ins, invitations and challenges. Members can see one another's display names and check-in activity even with progress sharing off. Your solve count is visible to members only when you opt in. A valid invitation can be used by someone who receives its link; owners can replace or revoke it. Leaving removes your membership and check-ins. Deleting a class removes its class records.

If you enable reminders, Arise stores your schedule, time zone, channel preferences and delivery history. Browser notifications also store a device label, push endpoint and subscription keys. Arise uses account progress to select reminders, sends email through Resend and encrypted push messages through your browser's push service. Disabling email or reminders stops future scheduled sends for that choice; it does not erase saved settings or history. You can remove a registered browser from reminder settings.

Referral features store invitation codes, the accounts linked by a referral, qualification and reward status, and relevant payment references. A referral link shows the inviter's first name and built-in avatar to its visitors. The inviter can see a referred friend's first name and last initial, built-in avatar, joining date and reward status. Email addresses and payment details are not shown to the other participant. Reward status can reveal that a qualifying purchase or refund occurred.

Class records and reminder settings have no automatic age-based deletion. Account deletion removes account-linked class membership, owned classes, reminder settings and push subscriptions. Reminder delivery logs older than 60 days are scheduled for cleanup when the reminder job runs. Referral and access-grant audit records, including internal account identifiers and payment references, remain after account deletion for reward administration and disputes; they have no automatic age-based deletion.

Bug reports store the description, reproduction steps and page path you submit, plus a report identifier and review history, in a separate private database. Reports include any personal information you type. Reports are available to authorized administrators and are not published as a public list. Reports and review history older than 180 days are scheduled for deletion in batches; a backlog can require further runs. Account deletion does not automatically delete these separate reports.

Stripe processes payments. Card, UPI and bank details are entered on Stripe's page and are not sent to Arise. Arise stores, for your account, the Stripe checkout and payment references, the pass bought, the amount, currency and price region, and payment, refund and dispute status, so the pass can be granted or ended. These payment records are kept after an account is deleted, as financial records for accounting, tax and dispute purposes. Stripe's own privacy policy covers the data it collects.

Policy changes and data requests

We will post material privacy-policy changes with a revised date and provide further notice or obtain consent where required. Depending on where you live, you may have rights to access, correct or delete personal information or object to certain processing. Use the contact channel below; we may ask for information needed to verify your request. We may retain records for legal obligations or to establish or defend legal claims.

Questions

Find account recovery, data export and other support options

The support email for account, refund, privacy and deletion requests is being set up and will be listed here. When you write, include the email on your Arise account and, for a payment, your Stripe receipt. Do not send passwords, card numbers or UPI PINs.

Report site issues using Report a bug in the footer. For account requests or refunds, use the support contact above.