Privacy Policy

How Plom handles your information

Last updated: 10 June 2026

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

This policy is written for the current private beta. Plom may update it as the app, hosting, diagnostics, AI processing, subscriptions, or support operations change.

How Plom collects information

Plom usually collects information directly from you when you join the beta 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, such as request metadata, error details, product analytics events, and diagnostic events.

How Plom uses information

Plom uses information to provide and operate the app, manage private beta access, organise academic workflows, generate plans and next steps, respond to support requests, investigate bugs, protect accounts and the service, improve reliability, understand which beta workflows need attention, and comply with legal, security, or operational obligations.

Beta waitlist and email notifications

If you join the beta list, Plom stores the details submitted in the form, including your name, email address, university or institution, student type, study area, device type, consent choices, source page, and optional notes about what you want help with. Plom may send a confirmation email to the address you submit and a notification email about new beta signups to the public support mailbox so the beta list can be managed. You can ask to be removed from the beta list by emailing support.

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, or PDF for analysis, Plom sends the selected material to the backend for that feature. In the current beta, uploaded images and files are used to extract or interpret academic content. Plom may store resulting 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, or photo library unless you choose the relevant upload or capture action and grant the operating-system permission.

AI handling

Plom uses AI-backed features to help 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.

Diagnostics, analytics, and Sentry

Plom collects limited product analytics and operational telemetry during beta. This may include events such as onboarding completion, feature use, route names, tool modes, API errors, slow API responses, crash/error-boundary events, request IDs, status codes, and technical metadata. Plom uses this information to understand beta usage, find reliability issues, and improve the product.

Plom may use Sentry for crash and error diagnostics in the mobile app and backend. Sentry events are configured not to send default personal information, and Plom filters common sensitive fields such as passwords, tokens, prompts, responses, notes, rubrics, essays, feedback, and request bodies before diagnostic events are sent where the current code paths support that filtering. 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 and does not use third-party advertising identifiers for cross-app or cross-site advertising. Plom's beta analytics are for Plom product operation and reliability, not ad targeting.

Security

Plom uses standard HTTPS/TLS for network traffic. Authentication, session handling, rate limits, audit events, telemetry, and hosted persistence checks are part of the beta backend. No public website, beta app, or hosted service can make absolute security guarantees, but Plom is designed to protect information against misuse, interference, loss, and unauthorised access using reasonable technical and operational controls for the current beta stage.

Third-party services and overseas processing

Plom may use third-party services to host the website and backend, store beta data, deliver app builds, provide TestFlight distribution, process 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, 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. Beta waitlist records are kept while beta access, invitations, support, and launch planning are being managed, unless you ask to be removed earlier. Support messages and feedback reports are kept for as long as needed to respond, investigate issues, improve beta reliability, or maintain operational records.

Current beta audit, telemetry, feedback, and waitlist records may be stored in the database and/or operational log files. Hosted beta logs are size-pruned by operational scripts, but a final public retention schedule is not yet implemented. Before a wider public launch, Plom should publish firmer retention periods for telemetry, audit events, feedback reports, uploaded material, backups, and any subscription or payment records.

Account deletion and removal requests

In the app, account deletion 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. You can email support to request access, correction, beta waitlist removal, or deletion help.

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, 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 beta changes. The "Last updated" date will show when the current version was published. Material changes should be reflected before wider public launch or App Store metadata updates.

Contact

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