How can we help?

Open SubTasks on the web or install the app, create your account, and choose whether to make a solo workspace or invite a partner. In a partnered relationship, choose the Tasker and Taskee roles, wait for the invitation to be accepted, then create your first task.

Use SubTasks on the web, on iPhone and iPad through the App Store, or on Android through Google Play. A client can open either a Solo Workspace or an accepted partnered relationship; workspace role and plan conditions still apply.

Yes. Free supports the core tasks, points, rewards, consequences, streaks, achievements, Shop, and Solo workflows. Some advanced features and usage allowances require Pro. Pro status is account-level, while feature access is evaluated for the active workspace: the Solo owner's access controls Solo, and either participant's effective Pro can cover an accepted partnered relationship. Check Pricing or User Settings → Plan & Connections for the current comparison.

Open Partners, select the add button, and choose Invite Partner. Enter their email address or username, choose the role you want in this relationship, and send the invitation. An existing user accepts it in SubTasks; a new user can follow the invitation email.

The Tasker usually creates tasks, sets rewards and consequences, and reviews completions. The Taskee completes tasks, earns points, redeems available Shop items, and may accrue demerits. Roles belong to each relationship, so the same person can have different roles in different relationships.

Yes. New accounts start with a Solo Workspace for tasks, points, streaks, rewards, consequences, and the Shop. If you already have a partnership but no solo workspace, open Partners and use the + menu to create one. If you later connect with a partner, SubTasks lets you keep the solo workspace separate or bring supported solo content into the partnership.

Send or accept an invitation from Partners and wait until it is accepted. The invitation sender then chooses once between Keep it separate and Bring it along; pairing itself does not erase solo data.

Yes. SubTasks supports ordinary partnered use through the web and mobile apps, so partners can use the same accepted relationship from different locations. The Tasker can assign and, when validation is enabled, review; the Taskee completes. Confirm the shared relationship Timezone and Notifications settings so schedules and notices behave as configured.

Use the app menu to switch between Light Mode and Dark Mode. For your avatar, open User Settings → Personalization to choose a character and turn Show Avatar on or off.

From the Tasks area, choose Create Task. Add the title and details, choose the task type and schedule, set points and any completion requirements or consequences, then save. Before saving, you can link an existing Notebook note or create one from the task form. In a partnered relationship the task is assigned to the Taskee; in solo mode it appears in your own workspace.

Habits live in Tasks and track a repeated Wanted or Unwanted practice in a Day, Week, or Month window. Create a habit from Tasks → Create Task → Habit, or edit one from Task Manager, then choose its count and optional points, demerits, review, note, or proof rules. Log occurrences and use History to review them. Use a recurring task when you need an ordinary task that repeats on a schedule.

In the active Solo Workspace or partnered relationship, create or edit a regular task, then use Schedule to control when and how often it returns.

Due Time is a Pro feature for eligible Regular and Challenge schedules. It appears for Daily tasks or Any Time tasks with a Due Date, not Weekly or Monthly schedules. Open Schedule, choose Add due time, and save; the deadline uses the active workspace's configured timezone. After the deadline, normal demerit/overdue processing applies. A Wanted Day habit's Due by is separate pacing guidance and never creates demerits.

Choose Challenge as the task type, use + Add Subtask for each step, and save the parent task's schedule, points, and supported consequence settings. The Tasker or Solo owner can choose Complete in order and Visible steps → Show all or One at a time; One at a time hides future steps from a partnered Taskee and requires order. Checklist rows are zero-point; the parent owns points, validation, completion, and missed-task consequences and auto-completes when every active step for the period is done.

In a partnership, only the Tasker can create a Lightning task; in Solo, the owner acts as Tasker and completes it in the same workspace. The partnered task is assigned to the Taskee. Choose a Time Limit and points; expiry is server-enforced. Missing the deadline records a rejected completion and normally issues the task's demerit amount; an optional failure Punishment is assigned when configured. Availability and usage limits depend on the current plan, so check the Plan screen.

Use Tasks → Manage → Select to change the state of several tasks or habits at once. This does not bulk-edit fields such as titles, points, schedules, or validation settings.

Stats tracks a daily streak of consecutive successful task days in the active Solo Workspace or partnered relationship; by default, every required daily task must be completed, and when Streak requires all tasks is off, a miss breaks the streak only if no task was completed that task day. Skip Day skips automatic missed-task demerits and protects the streak, while Streak Freeze protects the streak but can still allow demerits. For an eligible recorded Regular-task failure, a partnered Tasker with the Task Failure Repair beta can open Repair from Stats → History → Tasks or the task’s History, restore the captured streak, and continue from today; Repair does not complete the old task or award points or rewards.

When validation is required, the Taskee’s completion moves to Pending Review. The Tasker can approve it, reject it for another attempt, or reject it with the available consequence. Points are awarded when the completion is approved. Automatic approval can also be configured in Relationship Settings. Validation availability and limits depend on task type and plan.

A Tasker can enable Require a note while creating or editing an eligible regular task. A habit can also use Require a note; its form says Logger must write a note with each log. In a partnered relationship, the Taskee must enter a nonblank response in the completion sheet or habit log; in a Solo Workspace, the owner must write one before submitting. Challenges do not support this requirement. Free's required-note allowance is separate from validation/review and is currently one per week and one active required-note task or habit; the current Plan screen is authoritative if allowances change.

Photo proof records an image with a task completion or habit log. Requiring proof and requiring Tasker review are separate choices.

A Tasker, including a Solo Workspace owner, can add demerits manually and configure eligible task failures to add them. By default a missed task can use its point value, but the Tasker may override the amount, set it to zero, disable automatic demerit calculation, or use a punishment outcome instead. In a partnered relationship, a Taskee can spend demerits on punishments when redemption is allowed; in Solo, the owner can redeem punishments directly.

The Tasker or Solo owner creates punishments and sets their demerit cost. In an accepted partnership, a Taskee with Manage Punishments can also create or edit them. Redemption is separate: the Taskee can choose Redeem when Redeem Punishments is enabled; otherwise the Tasker uses Assign. In Solo, the owner redeems directly. An eligible task failure can use a configured punishment instead of fixed demerits; punishment-wheel outcomes require Pro.

The Tasker or Solo owner gives tasks a point value and creates rewards with a point price. A normal points-outcome completion awards points immediately; a partnered validation completion awards them after approval. A configured success reward or wheel replaces the point payout. Rewards live under Shop → Rewards and can be one-time or repeatable. Solo owners redeem directly; in a partnered relationship, Taskee redemption depends on Relationship Settings.

An affordable ordinary reward shows Buy in Solo and whenever Taskee redemption is enabled in a partnered relationship. Choosing Buy deducts the reward's point price, records the purchase, creates a reward delivery task, and notifies the Tasker only in a partnered relationship. The purchase later appears under Stats → Rewards → Redeemed.

Power-ups include Skip Day, Grace Period, Streak Freeze, Extension Request, Demerit Forgiveness, and Wheel Spin. Wheel Spin buys a prepaid spin from the configured reward or punishment pool. In a partnership, the Tasker configures the Item Shop and the Taskee purchases enabled items; in Solo, the owner configures and purchases directly. Custom prices and weekly limits require Pro.

A direct wheel turns configured rewards, punishments, or both into one pending result to spin. The usual partnered flow is Tasker to Taskee; a Solo owner can also send a wheel to themselves.

Open Notebook at /notes in the active Solo Workspace or accepted relationship. Notebook separates Notes (Free-form, List, Checklist), Journals, Agreements, and Limits & Desires. Notebook text fields also have fixed caps: a Title is limited to 500 characters, a Free-form body to 5,000, and each List/Checklist item to 2,000. Text beyond a cap is truncated when saved rather than rejected. In a partnership, the Tasker manages notes by default and a Taskee needs Manage Notes for note-level create/edit/delete; Collaborative notes can allow Taskee content/item edits. In Solo, the owner uses the workspace owner controls. Either participant can add journal entries once a journal exists. Limits & Desires are Taskee-authored in partnerships and owner-authored in Solo. Shared content can notify a partner only when a partner exists. Taskers can also link an existing Notebook note, or create one, from a supported task form; in a partnership the Taskee cannot change that link.

Agreements live in Notebook and store a purpose, rules, consequences, and optional Review date as versioned documents. In an accepted partnership, the Tasker manages the Agreement by default; a Taskee needs Manage Notes to create, edit, delete, or revise it, while both participants can acknowledge the current version. A Solo Workspace owner can manage and acknowledge it with one acknowledgement. A partnered version becomes Current signed version after both participants acknowledge it; a Solo version does so after the owner’s acknowledgement. Choose Revise after acknowledgement to create a new draft; the signed version remains in History and the new version must be acknowledged again. Free includes a limited number of Agreements; check the current Plan screen for the allowance.

Task Kits are ordinary templates for tasks, habits, rewards, punishments, and notes. Open Task Kits (/app/kits), preview a Kit, select supported items, and choose Import All or an item count for the active Solo Workspace or partnered relationship. A Solo owner or partnered Tasker can import; a partnered Taskee can import only the selected content types allowed by the relationship’s Taskee manage permissions, otherwise the app offers Send to the Tasker. Quests are a separate flow and must be started from the quest screen. Plan and feature limits can skip notes or optional habit capabilities, clamp flexible recurrence, or report skipped content after import.

A curated public Quest can be opened from the Quest shelf in Task Kits and started by an authenticated user with a Solo Workspace; its stages and tasks then appear in Today. A partnered Quest is different: in an accepted relationship, the Tasker can author a Quest when the quest_authoring rollout and campaign_authoring entitlement (Pro) are enabled, or choose an eligible Quest, preview its offer, and choose Offer quest when the campaign_authoring entitlement is enabled. The Taskee sees a pending offer and must Accept before the run is materialized and its timing begins. A current blocking run can prevent another start, and completed Solo Quests are not replayable yet.

Vacation Mode is relationship-scoped and free for Solo workspaces and accepted partnerships; no Pro subscription or beta opt-in is required. The Tasker controls it in Relationship Settings; in Solo, the owner is both Tasker and Taskee, while a partnered Taskee cannot toggle it. When on, the app pauses demerits, streak pressure, automatic consequences, and reminders while tasks and points stay available. Turning it off ends the active period but keeps the current task day protected; pressure resumes with the next task day. There is no date scheduler or automatic end date.

Pro applies in Solo and partnered workspaces. It can remove configured Free-tier limits for eligible features and unlock advanced controls such as Task Due Times, Flexible Recurrence, Custom App Icon options, and Wheel Outcomes. In Solo, the owner's effective Pro access controls the workspace. In an accepted partnership, either participant's effective Pro access can make that relationship Pro; account Pro and relationship coverage are separate states. Solo does not consume a partner slot, while Pro-linked relationships can cover a Free account. Platform safety caps still apply. Use Pricing or User Settings → Plan & Connections for current limits and feature availability.

Pro pricing is an account-level purchase flow for both Solo and partnered workspaces. Open the Pricing page for the Free/Pro overview or User Settings → Plan & Connections for account status and purchase actions. Review the current localized Monthly, Yearly, and any Lifetime offerings there. Trial or introductory eligibility can differ by platform, store account, product, and prior subscription history; only the offer shown by the store at checkout applies to that purchase.

No. This article applies to an accepted partnered relationship. If either person has effective Pro access—including an active subscription, a trial, or billing-grace access—the relationship receives the applicable Pro features. A canceled subscription remains Pro through its paid-through date. One user's access applies across that user's eligible relationships; the partner does not need to buy a second subscription for the same relationship. A Solo Workspace has no partner whose Pro access can cover it.

Subscription management is available to the person whose paid Pro purchase is manageable through the current store or billing portal.

The statement descriptor depends on whether you purchased through the App Store, Google Play, or web billing and can vary by region or bank. Review the checkout receipt or storefront subscription record for the exact merchant wording. The statement does not establish whether your active workspace is Solo or partnered, or whether a relationship has Pro coverage. SubTasks does not store your payment-card details.

Fresh Start is a partnered-workspace reset available to the Tasker of an accepted relationship. In Relationship Settings → Danger Zone, Reset stats only clears the scoreboard while keeping the board and history; Full fresh start clears the relationship’s operational content and history while keeping the partner connection and settings. The confirmation text is <code>RESET STATS</code> or <code>FULL RESET</code>, and the app asks you to confirm that you talked it through with your partner. A Solo Workspace has no Fresh Start control, so its data is unchanged by this flow; account deletion is the separate account-wide option.

Account deletion is an account-level, permanent action—not a workspace reset. Open User Settings → Help & Safety → Danger Zone → Delete Account, read the warning, and type <code>DELETE</code> to confirm. The account and its associated Solo and partnered relationship data are removed, then the app logs you out and returns to the landing page. In a partnered workspace, the shared relationship is removed and the partner can receive an account-deleted notification; in Solo, the Solo workspace is removed without a partner notification.

The in-app Report User flow is for an accepted-partner interaction. User Settings → Help & Safety is available in Solo and partnered workspaces, but the Support section shows the Report button with a partner's username only when an accepted partner is active. You can also open Partners and choose the flag icon labeled Report User on an accepted partner card. Choose Inappropriate Content, Abusive Behavior, or Spam, describe what happened, and choose Submit Report. Also block and remove this partner is optional; it blocks the partner, permanently deletes the shared relationship history, and prevents new invitations.

SubTasks stores account and connection data (email, username, timezone, notification preferences, display settings, Discord account link, and subscription tier/status), workspace/relationship links and preferences, user-created tasks, rewards, punishments, points, demerits, notes, messages, proof photos, push notification and browser authentication tokens, diagnostics/crash reports, support requests, and limited first-party analytics. Solo Workspace content is your own workspace; partnered relationship content is available to you and your linked partner. Published Task Kits expose their name, description, designer note, tags, and template content to all users alongside your username or anonymous attribution. Discord raid and <code>/brag</code> output are public/community data only when you opt in. Analytics may include username, subscription tier, timezone, platform, attribution, relationship identifier, and behavioral events, but is designed not to include task titles, reward names, note/chat text, proof images or URLs, email addresses, partner identifiers, or other user-generated content. SubTasks does not process or store payment-card details; see the Privacy Policy for the complete current description.

SubTasks uses TLS for data in transit. Supported sensitive and private user-generated fields are stored at rest with application-layer AES-256-GCM; the data-encryption key is wrapped by AWS KMS. Public Task Kit and catalog fields and operational metadata needed for identifiers, filtering, status, timestamps, and numeric values are not all encrypted. The running application must decrypt protected fields to display and process them, so this is server-side encryption at rest, not end-to-end encryption.

Protected user-generated fields are stored as ciphertext, and the developer IAM principal used for routine database work is explicitly denied KMS decryption. The ECS task role can unwrap the application key and decrypt protected fields while the service runs. The AWS account owner retains KMS policy administration and could deliberately change the key policy through a CloudTrail-audited break-glass action for an emergency or legal requirement. Therefore SubTasks cannot promise that no operator with account-level control could access content, and it is not end-to-end encrypted.

If you sign in and the dashboard looks empty, first check the active workspace: a Solo Workspace and an accepted partnership keep separate tasks, progress, history, and partner-covered Pro access. Open Partners, choose the intended card, then check Manage, Pending Review, Stats → History, and Plan & Connections before assuming anything was deleted. If the data is still missing, use Contact Support; do not create another account or use Fresh Start, Leave Relationship, or Delete Account as recovery steps.

Open User Settings → Plan & Connections → Connect Discord and choose Generate connection code. Join the SubTasks Discord, open the tickets channel, click Connect Account (or run <code>/connect</code>), and paste the one-time code before it expires. Choose Regenerate code if it is expired or no longer valid; regenerating invalidates the earlier code. This links the Discord account to your SubTasks account; no partner or Pro subscription is required.

Boss Raids are optional community events for connected accounts. An account with an active Solo Workspace or accepted partnered relationship can join; no partner or Pro subscription is required. Run <code>/raid join</code> and choose Solo, Selected relationship, or All relationships when prompted. Approved completions of accepted task types normally deal 1 damage; Pro Boost normally doubles damage, while current boss abilities or raid-wide boosts can change scoring. Use <code>/raid stats</code> for status and <code>/raid leave</code> to opt out. Leaving stops future scoring and removes the Raider role, but prior public posts and scores remain.

Connecting Discord alone or joining a raid does not publish your SubTasks username, email, tasks, notes, messages, proof, relationship details, rewards, punishments, demerits, or internal IDs. Public raid posts may show your Discord display name, damage, and rank, and a Pro account's Discord Pro role may be visible. <code>/brag</code> is a separate opt-in public share: it can post your Discord display name/avatar, Pro badge, chosen Solo or relationship scope, aggregate points/streak/task/achievement counts, and recent achievement names/descriptions. <code>/raid leave</code> stops future scoring and removes the Raider role but cannot retract prior public posts or scores.

Open User Settings → Help & Safety at /settings/help and choose Contact Support. Choose Help or Feedback, Report a Bug, or Request a Feature; enter a nonblank Description and optionally Screen or context. On supported web browsers, Include a screenshot lets you choose a tab, window, or screen to send; select only a view you have checked for private content. Choose Send to Support. You can also email hello@subtasksapp.com if the form is unavailable.

Open the app menu and choose Give Pro, Get Pro (also shown as Share SubTasks in the share panel). Share your referral code or link. Your friend must enter the code when creating their account, then pair with their own partner; pairing with you does not count. When that third-party pairing is credited, you both receive 14 days of Pro and Word of Mouth unlocks for you.

Yes. The press path is for any journalist, reviewer, creator, or publication; it does not assume a partner or relationship. Email press@subtasksapp.com with your publication or channel, planned coverage or review, timing, and what you need. The About SubTasks page says the team can provide screenshots, app-store links, character art, and other requested materials.