Privacy Policy

Who operates TaskUp

TaskUp's named operator is Alex Glavin, based in England. For privacy questions or requests, email support@task-up.org. The service address and agreement arrangements still need confirmation. Until the notice is completed and reviewed, external beta invitations should remain closed.

Data TaskUp handles

Beta requests store the submitted email address and review status. Invite records store the invited address, a hash of the one-use key, its expiry and redemption status. Account sign-in uses an email address and authentication data. Projects include a name, production URL, framework choice and public project key. Monitoring stores endpoint URLs, HTTP status, response time, certificate expiry and incident history. Registered controls, scheduled actions and Modes include their values and an audit trail. Deploy Guard also stores deployment identifiers and observation results. If you send in-app feedback, TaskUp stores your message, account, project, page path and submission time for owner review.

Public signup and Google

The planned public email signup sends a confirmation link before account completion. Supabase provides authentication and password recovery. When Google sign-in is enabled, Google and Supabase authenticate the account and can supply an email address, name, profile image URL and identity identifiers. TaskUp requests basic identity scopes, not Gmail or Drive access. Provider identity data may be retained in Supabase Auth; TaskUp does not automatically copy a Google photo into its account-photo storage. These public signup options remain closed or unavailable until their release checks pass. Current beta signup uses an invitation key.

Age and terms confirmation

Applicants confirm that they are at least 13; TaskUp does not request a birthday or identity document. The current invitation/request forms check this confirmation without saving it. The planned public account flow stores an age-confirmed flag and the accepted terms version in Supabase Auth account metadata. These are self-declarations, not identity or age verification. Eligibility and any additional protections required in the countries where TaskUp operates still need review.

Optional profile photos

You can add a display name and upload a JPG, PNG or WebP photo after signing in. TaskUp resizes and re-encodes accepted photos to a small WebP image, stripping the original image metadata. The image is stored in a private Supabase Storage bucket at a path tied to your account. The app serves it only to that signed-in, eligible account; it is not a public profile photo or shared with other TaskUp customers. You can replace or remove it in Your account. Photo removal deletes the active stored image; provider logs and backups may persist separately. Uploading a photo is optional.

Sign-in cookies

TaskUp uses authentication cookies to keep account holders signed in and to protect project pages. These cookies are needed for the account service. Optional SDK browser storage on a connected website is separate from TaskUp sign-in.

TaskUp account activity

When an account holder opens the protected TaskUp app, TaskUp records their account ID once per UTC day to count active accounts in the private beta admin page. It does not store page paths or a stream of visits for this count. An in-memory marker avoids repeated requests while the page is open, and the database prevents duplicate daily records. This account count does not create a browser identifier in storage.

SDK events

The web SDK can submit runtime error messages, failed request metadata, route, version, up to five file names and line numbers from an error stack, and an optional host-supplied user ID. The server validates and sanitizes those submissions, then groups equivalent errors by fingerprint. TaskUp briefly stores a server-side hash derived from the sending IP address to enforce ingestion limits; the raw address is not stored in its telemetry tables. The SDK does not read cookies, authentication tokens, passwords, form contents, payment details or request bodies. An error message, route or user ID supplied by a website may still contain personal information. Project owners should avoid sending sensitive values and tell their own visitors about this processing.

Optional website usage

When a project enables usage tracking in the SDK, TaskUp counts page views, browser visits, explicit clicks and explicit conversions. For daily active users, the SDK creates a random browser identifier in local storage. A website can instead supply its authenticated user ID for more accurate signed-in counts. The SDK also creates a random session identifier in browser session storage. TaskUp hashes the submitted identifiers on the server and keeps short-lived deduplication records and daily totals. One person using multiple browsers or signing in during a day may be counted twice in the browser estimate. The server classifies a visit as desktop, mobile or other from the browser user agent and stores only the daily category totals. It does not store the raw user agent, click target, raw usage URL, query string or event properties. This tracking is optional and off by default in the SDK. Project owners must provide their own visitor notice and obtain any consent required for browser storage or analytics before enabling it.

How data is used

TaskUp uses account and project data to provide monitoring, incident grouping, deployment observation, registered control reads and changes, scheduling, alerts and account security. Optional integration data appears only when that integration is connected. The precise legal bases for each purpose need review before external beta invitations.

Email choices, mailing lists and delivery records

TaskUp product news and promotions are optional. We send them only when the address belongs to an active, verified TaskUp account and you have separately chosen to receive them in your account's email preferences. We rely on your consent for this marketing. Joining TaskUp, accepting its Terms, appearing in a saved mailing list or receiving a support reply does not opt you in.

You can withdraw your choice in account preferences or use the unsubscribe link in a marketing email without signing in. You can also tell support@task-up.org that you do not want marketing. Withdrawal stops future marketing but does not make earlier lawful processing unlawful. It does not prevent genuinely necessary account, security or service information, or a reply you requested. We do not use a necessary-service label to include promotions you have not agreed to receive.

For email administration, we use addresses supplied through your account or correspondence and addresses entered by the operator for a specific support or necessary-service purpose. The operator may organise addresses into named lists or choose a current account audience. Addresses are sent separately rather than exposed to other recipients. A list is an administrative grouping, not evidence of marketing permission.

We store message sender and reply-to details, subject and body, the reviewed audience, recipient addresses and delivery outcomes, timestamps and provider message identifiers where available. A message review expires after 24 hours; that does not itself erase its history. We retain the campaign/message and recipient-outcome history for 30 days from preparation and remove it through the documented manual cleanup process. This is not automatic scheduled expiry. If cleanup is missed, records may remain longer until the delay is corrected; that does not extend the retention policy. Resend processes messages for delivery and keeps its own copies and logs under the provider schedule, separately from TaskUp's history. Delivery acceptance is not proof you read a message.

Your email preference record uses a hash of your address, your choice, a notice/consent version, relevant account reference and change information. An unsubscribe link contains a limited code that can turn marketing off without displaying your address. Hashes and these codes are not treated as anonymous information.

On account closure, we stop marketing eligibility and remove unnecessary active preferences and list/address records within the existing 30-day closure process. We may retain a minimal do-not-contact record, including the address hash and information needed to honour your opt-out, after the account and campaign history are gone. We use that record only to respect your choice and prevent accidental re-contact, not to send marketing or rebuild your profile. We review its necessity during our monthly retention review and remove it when it is no longer needed for that purpose. We explain a justified exception in response to a deletion request. Keeping a suppression record does not renew your marketing consent.

We keep only necessary evidence of consent or withdrawal for the relevant compliance purpose, with a recorded review or deletion point. Support case correspondence follows the separately stated support schedule; its 90-day period does not automatically extend every campaign record. Saved lists are reviewed monthly and removed when their stated purpose ends. No saved list or marketing preference gives permission to keep unrelated information indefinitely.

We rely on legitimate interests in handling requested correspondence and administering necessary service communications, subject to the existing safeguards and rights. We retain minimal suppression information to comply with your marketing objection and avoid sending unwanted messages. Our Privacy Policy explains your other rights, providers and overseas processing. You can complain to the Information Commissioner's Office.

Optional browser alerts

If you turn on push alerts, TaskUp stores this browser's push endpoint and encryption keys to deliver short incident and Deploy Guard messages. The endpoint is a sensitive delivery address and is kept server-side. Alerts use your browser's push provider; that provider receives the delivery request. You can turn alerts off in Project Settings or revoke notification permission in your browser. TaskUp limits delivery attempts and removes expired subscriptions.

Optional integrations

When connected, TaskUp reads a repository's latest GitHub commit, Vercel deployment identifiers, Stripe charge totals for a selected currency, or Supabase Auth user counts. With additional Checkout read access, TaskUp can store the names and quantities of up to five top products from paid one-time Checkout sessions for the latest complete day. It stores small daily aggregates and connection status. Stripe customer records and Supabase user records are processed in memory for those counts and are not copied into the TaskUp database. Disconnecting removes the saved credential and that provider's daily metric snapshots.

Products, costs and estimated profit

If you use cost settings, TaskUp stores the completed UTC day, currency, product and fulfilment costs, payment fees, operating costs and your review confirmation. An optional breakdown stores product names, unit costs and units sold. TaskUp uses those entries with Stripe revenue for the same day and currency to show estimated profit. It does not fetch your expenses automatically, create checkout products or infer costs from selling prices. Do not enter customer names or personal information in product labels.

Storage and providers

Supabase provides authentication, database storage and Vault storage for optional integration credentials. Vercel hosts the application. Provider credentials are sent to the server for verification, stored in Vault and never returned to the browser. Successful provider snapshots normally refresh daily; setup and retries can contact a provider sooner. The primary Supabase database is configured in the Frankfurt region. That does not establish the locations of every provider, log, backup or support process. Provider contracts and international transfer arrangements still need review.

Retention

Configured cleanup removes detailed HTTP checks and error buckets after seven days, website usage daily counts after about seven days, and usage deduplication keys and beta rate-limit hashes after about two days. TaskUp account activity records are removed after 30 days. Daily integration metrics and push delivery logs are kept for about eight days, and worker health records for seven days. Daily cost totals and optional product breakdowns are retained for 90 days. Control value and definition changes, activity entries and inactive error groups are removed after 90 days. Cleanup depends on operational jobs running; retained data may remain longer after a failure. Incident records, feedback, account and project data, beta requests and invite records do not currently have an automatic deletion period. Backups may persist separately. A deletion process and final retention schedule are required before external beta invitations.

Your choices and rights

Project owners choose whether to enable usage tracking, which registered controls to expose and whether to supply a user ID. Browser push alerts require your permission and can be disabled in Project Settings or in the browser. Remove the SDK from your site to stop new SDK submissions. To request access, correction, deletion or to object, email support@task-up.org from your account address. We will verify your identity before disclosing or removing account data. You may also complain to the UK Information Commissioner's Office. The final request procedure and lawful bases need review before external invitations.