How Plom handles your information

Last updated: 2 November 2026

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

Plom handles personal information in line with the Australian Privacy Principles in the Privacy Act 1988 (Cth). In short: Plom stores your data in the United States, uses AI only after you allow it, does not sell your information or use it for advertising, and lets you delete your account at any time.

Account and profile data

Plom may collect your name, email address, password credentials, university or institution, study area, student type, communication preferences, device type, app account details, profile details, and support messages.

Study workflow content

Plom may collect assignments, due dates, work-plan steps, study notes, chat messages, rubric text, feedback, uploaded academic material, generated summaries, saved outputs, progress snapshots, wins, and notification preferences you choose to create.

Uploads, camera, and photos

Camera, photo, document, and file picker access is used only when you choose to capture or select academic material, such as a rubric, assignment brief, feedback, draft, email text, or notes.

Diagnostics, analytics, and billing

Plom collects product analytics to understand which parts of the app students use and where they get stuck: for example, that an assignment was added, a plan step was completed or the paywall was shown. These records use your Plom user ID, codes and counts, never what you write: no assignment names, briefs, rubrics, notes, file names, messages or AI replies, and no name or email address. Plom also collects API error telemetry, crash diagnostics, request IDs, route names, technical metadata, subscription identifiers, entitlement status, product IDs and Plom Pro billing events.

Sign-in and device details

When you sign in or use the app, Plom’s server records your IP address and your device’s browser or app identifier (user agent) to keep your account secure, spot unusual sign-ins and fix problems. Failed sign-in attempts record the email address that was tried, with the IP address and device details.

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, such as your IP address and device details, 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 Plom Pro subscriptions, 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 asks before it first sends your content to Anthropic, and nothing is sent until you tap Allow. You can turn AI features off at any time in Me → Settings → AI features. Plom’s server then refuses AI requests for your account, so nothing more is sent to Anthropic until you turn AI features back on. Turning them off does not recall what was already sent: Anthropic keeps it only for a limited time under its commercial terms and does not use it to train its models. Plans, replies and other results already saved in Plom stay in your account; turning AI features off does not delete them.

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 is bought through the App Store. Apple processes the payment through your Apple Account under Apple’s own privacy policy, and Plom never receives your card details. If Plom Pro is bought through Google Play in the Android app, Google processes the payment in the same way under Google’s privacy policy.

Plom uses RevenueCat to manage subscriptions. Plom and RevenueCat 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 uses 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.

On this website, limited first-party events help us understand whether visitors view the product, start the launch-list form or complete it. These events use fixed page and action labels, without form contents, email addresses, cookies or persistent visitor identifiers. Website measurement is disabled when your browser signals Do Not Track or Global Privacy Control. The server may still process technical request information needed to operate and protect the service.

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.

Plom’s analytics provider does not use advertising identifiers and does not combine Plom’s data with other companies’ data. Plom does not record your screen or your taps.

Where your data is stored, and who processes it

Your Plom data is stored in the United States. Plom’s server, database and file storage run on Railway in the United States (US East, Virginia), because Railway has no Australian region. AI processing, subscription records, product analytics and crash reports also go through providers in the United States. Plom’s emails are sent from Resend’s Tokyo, Japan region.

Plom shares personal information only with the service providers below, only so they can do their part in running Plom, and only with providers that give it the same or equal protection to this policy. Plom does not sell personal information.

Railway (United States) hosts Plom’s server, database and file storage, so it holds your account and study data.
Anthropic (United States) runs the Claude AI model for AI features. It receives what you share with those features, with your first name, university, degree, year and semester, the names of files you upload, and your saved study progress, only after you allow AI.
RevenueCat (United States) manages Plom Pro subscriptions. It receives your Plom user ID and your purchase and subscription status.
Sentry (United States) receives crash and error reports with technical and device details. Plom filters academic content and common sensitive fields out of these reports.
PostHog (United States, US East, Virginia) receives Plom’s product analytics: your Plom user ID, which screens you open, which features you use, your year of study and university (when you chose it from Plom’s list), the app version, your phone’s model, operating system, language and time zone, and, on Android, which Plom campaign link you installed from. It does not receive your name, email address or anything you write in Plom. RevenueCat also tells PostHog when a free trial or subscription starts, renews or ends, so Plom can see which features paying students use. When you delete your account, Plom asks PostHog to delete your analytics records too.
Resend (a United States company; Plom’s emails are sent from its Tokyo, Japan region) sends Plom’s emails, such as password-reset and launch-list emails. It receives your email address, your name where the email uses it, and the email’s content.
Google Workspace (Google’s data centres worldwide) hosts Plom’s support mailbox, so it holds the emails you send to support@plom.app.
Microsoft (Microsoft’s data centres worldwide): Plom reads the support mailbox in Outlook, which may keep a synced copy of support emails on Microsoft’s servers.
Cloudflare (global network) hosts and delivers this website. It receives your IP address and technical details of each request.
Google (United States): to check whether your phone is online, the iPhone app may contact a Google web address, which receives your device’s IP address but no account or study information.

Apple, and Google if Plom Pro is bought through Google Play, handle app downloads, TestFlight and store purchases as independent businesses under their own privacy policies.

Retention

Plom keeps your account and study data while you use Plom. If an account goes 2 years without a sign-in, Plom deletes it and its data. Plom emails you 30 days before, so you can sign in to keep the account, and never deletes an account this way while it has an active Plom Pro subscription.

Launch-list entries are removed 12 months after Plom’s public launch, or sooner if you ask. Support emails are kept for as long as needed to respond and investigate. In-app feedback reports are also emailed to Plom’s support mailbox, where they are kept like other support emails.

Every day, and each time it starts, Plom’s server removes audit, diagnostic and in-app feedback log entries older than 30 days, including the IP addresses recorded in them. The IP address and device details saved with each sign-in session are deleted 90 days after the session ends. Failed sign-in records, which hold the email address that was tried with the IP address and device details, are deleted 30 days after the last attempt, but not while a pause on sign-ins after repeated failed attempts is still running. Both are removed sooner if the account is deleted. Failed sign-in records for an account are also cleared when its password is reset, and a successful sign-in clears those from the same network. Plom’s stored copies of finished assignment and plan requests are removed after 30 days. Records of AI usage, which hold no study content, are kept for 24 months, and purchase records for 7 years for tax and refunds. Backups and records held by service providers follow those providers’ 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. Plom also asks PostHog to delete your product analytics; PostHog removes those records in its next deletion run.

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. A copy of in-app feedback you sent may remain in Plom’s support mailbox; ask us and we’ll delete it. Deleting your Plom account does not cancel a Plom Pro subscription: cancel it in your Apple Account subscription settings, or in Google Play if you bought it there.

After an account is deleted, Plom asks RevenueCat to delete its purchase record for that account. Plom keeps its own purchase history for refunds and tax, with no name, email address or account number.

To delete your account without the app, see Delete your Plom account.

Data access, correction, and deletion

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

Changing your choices

AI features: turn them on or off in Me → Settings → AI features.
Camera, photos and notifications: change Plom’s permissions in your phone’s Settings app.
Launch-list emails: email support to stop them or to leave the launch list.
Your account: delete it in Me → Settings → Delete account.

Children and eligibility

Plom is built for university students. You must be at least 16 to use Plom, as the Terms of Use explain. If you believe someone under 16 has given Plom personal information, contact support so Plom can review it and delete the account.

Complaints

If you have a privacy complaint, email support@plom.app with the details. Plom will reply in writing within 30 days. If you are not satisfied with the reply, you can complain to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au.

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

Plom is operated by Constantine Dean Karouzos, a sole trader based in Sydney, New South Wales (ABN 45 387 763 319), who is responsible for the personal information described in this policy.

For privacy questions, access requests, correction requests, launch-list 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.