Privacy
Effective date: September 6, 2026.
Who operates Tasq
pxlabz operates Tasq. For privacy questions, access requests, or account and data deletion requests, email paulcedrick.artigo@gmail.com.
Information Tasq processes
When you sign in with Google, Tasq receives your email address, name, profile-picture URL, and the information needed to verify your identity. Tasq stores your email address and profile details for your account. It does not store Google access or refresh tokens for later access to your Google account.
When you sign in by email, Tasq processes your email address and sends a one-time sign-in code and link. It stores hashed verification values and session tokens. Tasq also processes request information, including IP addresses, to operate the service and limit abusive sign-in attempts. The application stores an IP hash for sign-in rate limiting; the gateway can record IP addresses and request paths in operational logs.
Tasq stores the information you and your collaborators add to the service, including workspaces, team memberships, projects, tasks, descriptions, comments, assignments, invitations, and activity history. Workspace permissions determine which collaborators can access that information.
How the information is used
Tasq uses this information to authenticate users, maintain accounts and sessions, provide project-management features, deliver sign-in and invitation emails, support users, and maintain the service. Google account information is used for sign-in and account profile display.
Providers and sharing
Google handles Google sign-in. Resend delivers transactional email and receives the recipient address and message content, which can include a sign-in code or link, a workspace name, and the inviter's identity. Hosting and infrastructure providers process information needed to run Tasq and its database. Information you add to a shared workspace is available to collaborators according to their access permissions.
Tasq's use and transfer of information received from Google APIs must follow the Google API Services User Data Policy, including its Limited Use requirements.
Retention and deletion
Tasq does not currently apply a fixed automatic deletion period to account and workspace content. Expiration of a sign-in code or session ends its validity; it does not necessarily delete the stored record. Task archiving is not permanent deletion, and activity or cycle history can retain information about earlier work.
Contact pxlabz to request access to or deletion of your account or personal information. We may need to verify that the request comes from you. Shared-workspace content, operational records, and backup copies need to be considered when handling a request.
Security and updates
Tasq uses HTTPS for production access, access controls for shared work, and protected session cookies. No service can guarantee absolute security. We will update this page when the practices described here change.