Privacy Policy

How Plom handles your information

Last updated: 24 June 2026

Plom is a university companion for Australian students. This policy explains how Plom handles information from app users, launch-list signups, support contacts, waitlist signups, and visitors to this website.

Plom may update this policy as the app, hosting, diagnostics, AI processing, subscriptions, support operations, or App Store release process changes.

How Plom collects information

Plom usually collects information directly from you when you join the launch list, create an account, complete onboarding, add assignments, use chat, upload or paste academic material, submit feedback, contact support, or use app features. Plom also collects limited technical information automatically when the website, app, or backend is used.

How Plom uses information

Plom uses information to provide and operate the app, authenticate accounts, organise academic workflows, generate plans and next steps, respond to support requests, investigate bugs, protect accounts and the service, manage subscription entitlements when billing is live, improve reliability, understand product usage, and comply with legal, security, or operational obligations.

Academic material and uploads

Academic material can include assignment briefs, rubrics, feedback, drafts, notes, references, email drafts, due dates, and related study context. You should only upload or paste material you are allowed to share and should avoid adding unnecessary personal, health, financial, or highly sensitive information.

When you choose a photo, image, PDF, or other document for analysis, Plom sends the selected material to the backend for that feature. Plom may store extracted text, summaries, rubric criteria, feedback summaries, saved outputs, source type, and related metadata needed to provide the feature. Plom does not access your camera, camera roll, photo library, or files unless you choose the relevant action and grant the operating-system permission.

AI handling

Plom uses AI-backed features to explain academic material, decode rubrics and feedback, generate plans, support chat, and suggest useful next steps. The backend currently uses Anthropic for AI processing. When you use an AI-backed feature, Plom may send the prompt, conversation context, selected academic material, profile context, assignment context, previous saved memory, progress context, and related metadata needed for that request to the AI provider.

Plom is designed for understanding, planning, and academic support, not ghostwriting or submitting work for you. AI outputs can be wrong or incomplete. You are responsible for checking outputs, following your university's academic integrity rules, and deciding what to use.

Subscriptions and purchases

Plom Pro billing is not live in current beta builds. If App Store subscriptions are enabled in a future production build, purchases will be processed by Apple through your Apple ID. Plom does not receive your full payment card details from Apple.

Plom may use RevenueCat to manage subscription entitlements. In that case, Plom and RevenueCat may process your Plom user ID, RevenueCat customer ID, product ID, entitlement status, purchase status, expiry date, renewal or cancellation status, and related billing lifecycle events so Plom can unlock Pro features, restore purchases, prevent abuse, provide support, and reconcile backend access.

Diagnostics, analytics, and crash reporting

Plom collects limited product analytics and operational telemetry. This may include events such as onboarding completion, feature use, paywall views, route names, tool modes, API errors, slow API responses, crash/error-boundary events, request IDs, status codes, device/runtime context, and technical metadata.

Plom may use Sentry for crash and error diagnostics in the mobile app and backend. Diagnostic systems are configured to avoid sending academic content where current code paths support filtering, including common sensitive fields such as passwords, tokens, prompts, responses, notes, rubrics, essays, feedback, and request bodies. No diagnostic filter is perfect, so avoid entering unnecessary sensitive information into the app.

Tracking and advertising

Plom does not track users across other companies' apps or websites for targeted advertising and does not use third-party advertising identifiers for cross-app or cross-site advertising. Plom's analytics are for product operation, reliability, safety, support, and product improvement.

Third-party services and overseas processing

Plom may use third-party services to host the website and backend, store app data, deliver app builds, process App Store subscriptions, manage entitlements, provide diagnostics, send support or beta notification emails, and provide AI processing. These services may include hosting providers, database providers, Apple TestFlight/App Store Connect, Expo/EAS, RevenueCat, Sentry, Anthropic, and email delivery providers.

Some providers may process or store information outside Australia, including in the United States, the European Union/European Economic Area, or other regions where their infrastructure or subprocessors operate. Plom does not sell personal information.

Retention

Plom keeps account and academic workflow information while your account is active or while needed to provide the app. Support messages and feedback reports are kept for as long as needed to respond, investigate issues, improve reliability, maintain operational records, or comply with legal obligations.

Security, audit, telemetry, billing lifecycle, and diagnostic records may be kept for longer where needed for account security, fraud prevention, dispute handling, legal compliance, reliability analysis, or backup recovery. Hosted logs may be pruned by operational scripts, while backups and provider-side records may follow the relevant provider retention settings.

Account deletion and removal requests

In the app, account deletion is available from account settings and requires password confirmation. Current backend deletion removes the user account and user-owned relational app data such as profile details, sessions, assignments, work-plan steps, conversations, messages, assessment records, progress snapshots, saved outputs, memory, wins, notification preferences, AI usage counters, login-attempt records for that email, and user-linked feedback reports.

Account deletion may not immediately remove every operational record, such as security/audit logs, telemetry records, waitlist records, backups, provider-side diagnostic records, or records Plom reasonably needs for security, legal, fraud-prevention, dispute, or operational reasons. Deleting your Plom account does not cancel an App Store subscription. If subscriptions are live, you must cancel through your Apple ID subscription settings.

Data access, correction, and deletion

You can ask Plom to help access, correct, or delete account data by contacting support. Some information may need to be retained where required for security, audit, legal, billing, dispute, or operational reasons.

Children and eligibility

Plom is built for university students and is not intended for children under 13. If you believe a child has provided personal information to Plom, contact support so the issue can be reviewed.

Changes to this policy

Plom may update this policy as the product and release process changes. The "Last updated" date shows when the current version was published.

Contact

For privacy questions, access requests, correction requests, beta waitlist removal, account data requests, deletion requests, billing data questions, or complaints, contact support@plom.app. Please include enough detail for Plom to identify the relevant signup or account. For product support, visit Support.