Privacy Policy

Who is responsible

WorkSchool 365, registered in Ontario, Canada, operates these services. Contact support@getpaidx.com for privacy questions, access, correction, export, deletion or consent-withdrawal requests. Include the account email and affected service or workspace, but never send passwords, API keys or one-time codes.

The two branded plugins use the same GetPaidX backend. Their OAuth permissions and browser sessions are tied to their respective origin. OpenAI and other services you choose also process information under their own terms and privacy policies.

Information we collect

Account and access

Email, name, username, profile photo, professional description, external links, sign-in provider identifiers, session and OAuth grant records, granted scopes, roles, and delegation details. Sign-in credentials are handled through the website or provider authorization flow, rather than requested in plugin conversations. Anonymous visits can create a pseudonymous account/session before sign-in.

Posts and discovery

Post titles and bodies, tags, audience and purchase settings, covers and QR targets, replies, follows, memberships, referral/UTM attribution, and private Pass/Saved/Interested decisions. A confirmed interest reply becomes a normal moderated reply sent to the author.

Workspaces and AI

Files you upload, select, read, or create; repository URLs and checked-out source; prompts, instructions and supplied conversation context; program parameters; source revisions and snapshots; generated documents, images and sites; execution status, output, errors and cancellation records; automation rules and channel messages. Workspace browser sessions can also retain their own browsing profile, cookies and downloads.

Connected provider data

When you connect a provider, its account identifiers, granted scopes and the data used by your authorized workflow. Supported Google Workspace permissions can include Gmail messages and attachments, calendar events, Drive file metadata and contacts. Supported workspace/API operations can also receive connection configuration or secret values and return credential metadata or newly issued access credentials when authorized. These operations are distinct from ordinary browser sign-in.

Collaboration and communications

Collaborator and organization membership/role details, conference submissions, assignments, reviews and decisions, invitation recipients, email subjects/bodies/attachments, reply routing, delivery status, notification preferences, push subscription endpoints, live-session participants, moderation events and persistent chat. Optional live audio, video and screen sharing are handled when you join through the website.

Payments and usage

Plan and subscription status, purchases, amounts, currency, Stripe customer/connected-account and transaction references, invoices, revenue shares, eligible organization billing accounts, AI token/credit consumption, workspace runtime usage and quota records. Stripe collects payment-card and payout-verification details in its own payment/onboarding surfaces; do not put them in tool inputs.

Location and technical records

Places and check-ins you choose, city or coordinates supplied for nearby discovery, IP address, browser/device information, user agent, request/error and security records, timestamps, cookies, and website analytics events where enabled. Plugin requests carry the connection’s network metadata; website/browser visits can produce separate device records.

We receive information directly from you, from your authorized AI client, sign-in/payment/connected providers, collaborators and correspondents, and from use of the service. An authorized professional outreach campaign can create an unverified profile and public featured workspace using a recipient email and professional information before that person signs in. Existing profiles are not overwritten by that process. Contact us to correct, remove or stop this use; verification of account control is separate from profile creation.

ChatGPT, Codex, MCP and Site tools

When you invoke a tool, your AI client sends its selected tool name and arguments to our server under your authorized connection. Depending on the task, arguments can contain search/location filters, post or participant identifiers, email recipients, text, selected file paths and contents, prompts, repository addresses, program parameters, publication choices and billing selections. Connecting alone does not give us your entire ChatGPT/Codex history or unrestricted access to local files. Files or context that you or the client include in a request, upload or workspace operation are processed by the service.

Tool results return to the invoking client and may become part of the AI conversation. They can include public profile/display information and Discover cards; your authorized posts; workspace, conference, participant and billing-option details; selected source files, diffs, execution output, generated artifacts and links; and action receipts, object identifiers, revisions, scheduling times and status needed to continue the requested work. Other people’s information is returned only through the applicable access and conference-blindness rules. User-selected files and output can themselves contain personal information.

Professional discovery and contact are service functions. Author/contact records made available by the app can include names, usernames, profile images, author/account identifiers, email addresses, contact and external website links, and associated author information. Tools preserve these fields under the same access rules as the underlying product route. An email included in an accessible author record can be returned even if it is not separately written in the post body. Public records can make these details visible to the public; private-content and conference-blindness rules still apply.

Immediate Codex tasks and AI-assisted automations send the instruction and relevant workspace context to the configured AI provider. Declared program runs execute selected source and parameters without a model turn, but that program may contact external services. Authorized workspace code and agents can read or change files and use connections available to that workspace. Choose the workspace and task scope carefully.

Normal plugin sign-in uses the browser/provider OAuth flow and does not require you to paste a password, one-time code or API key into the conversation. Advanced authorized API/workspace operations can manage workspace secrets, OAuth client configuration, access tokens, webhooks or configuration files. Their inputs can contain credential values, and their results can include newly issued credentials, authenticated access links or tokenized reply routes. We process that information for the requested operation under its permissions. If sent through an AI client, those inputs and results may also remain in its conversation/history. Use website/provider settings when you want to keep credential setup out of an AI conversation, and avoid putting sensitive values in public posts, logs or shared files.

Disconnecting a plugin stops that connection’s future authorized access when its grant is revoked. It does not erase earlier tool results from your AI conversation, delete saved GetPaidX content, or stop already-created scheduled automations. Manage each separately. Signed-in browser Site tools use the same service through a browser session and the same data practices.

How we use information

We use information to create and authenticate accounts; apply permissions and peer-review blindness; provide discovery and remember your decisions; run, save and reopen workspaces; generate and publish requested work; deliver messages, invitations, reminders and notifications; process purchases, payouts and revenue sharing; allocate organization billing and meter AI/runtime usage; provide support; detect abuse and protect the service; investigate failures; measure website use and referrals; and meet legal, accounting and dispute obligations.

We do not sell personal information. We do not use private workspace content or plugin inputs/outputs to train our own general-purpose AI models. Sending content for requested model inference is a separate use. AI clients and providers have their own data controls; our policy does not override their retention or training terms. We do not claim that the whole service has zero data retention.

Where consent is required, we rely on the relevant permission or consent and allow withdrawal for future optional processing. Other processing is needed to provide the requested service, operate and secure it, or meet applicable legal obligations. Withdrawal can limit the feature that requires the information.

Who receives information

• Hosting and operations: Microsoft Azure hosts application/database, object and workspace storage, runtime and logging infrastructure. Amazon Web Services currently hosts the LiveKit media relay. Authorized operators and support personnel can access relevant information for operation, security, support and privacy requests.
• AI services: OpenAI receives content involved in ChatGPT/Codex conversations, requested model/image generation and workspace-agent tasks. Google receives prompts or media when you use a Gemini-backed feature. Gooey.AI processes QR targets/payloads, prompts and optional reference-image content or image links when you choose the ControlNet QR option. Generated artwork and scan results are saved when needed for the requested asset or cover. We send the context required by the selected workflow rather than promising that no content leaves the workspace.
• Payments: Stripe processes checkout, subscriptions, Connect onboarding, payouts and related billing records. GetPaidX receives payment state and transaction/account references, rather than complete card numbers. Payment-card and identity-verification collection belongs in Stripe’s surfaces.
• Email, messaging and notifications: Azure Communication Services, SendGrid and Google Workspace/Gmail process the addresses, message content, attachments, routing and delivery information needed for enabled email flows. Connected messaging services such as Telegram or WhatsApp process participant identifiers and messages/media for the channel you choose. Browser/OS push services process subscription and notification payloads when you subscribe. A reply to a workspace email or connected channel can be saved and passed to its agent.
• Optional integrations: Google Maps/Places processes map/place queries and relevant network or location information. Fallback maps request OpenFreeMap/OpenStreetMap-derived map assets through our relay; requested map tiles can indicate the area viewed. Google Analytics receives website analytics where enabled. Embedded media such as YouTube can receive connection/cookie data when loaded. Public GitHub cloning contacts GitHub; social-sharing destinations and connected Google or other user-selected services receive the requests/content needed by the authorized workflow.
• Your chosen audience: Other users, collaborators, reviewers, event participants, email recipients, webhook endpoints and the public receive content that you ask us to send or share, subject to product access rules. Organization administrators can see relevant membership, billing and usage information; membership alone does not grant workspace-content or conference access.
• Legal and business recipients: We may disclose necessary records to professional advisers, authorities or a successor business where required by law or needed for a lawful transaction, rights enforcement or protection against abuse, with applicable safeguards.

Providers’ own practices are described in their policies: OpenAI, Microsoft, Google, Gooey.AI, Stripe, Amazon Web Services, Twilio/SendGrid and GitHub.

Publishing and other people’s information

Publishing a post, profile, QR card, artifact site, proceedings or shared file makes the selected content available to its configured audience; public or unlisted links can be forwarded. Public material can be indexed, cached or downloaded. A draft or private workspace requires the applicable access rights. Paid access does not prevent a recipient from keeping a copy. Changing visibility or removing the original does not recall copies already received.

Author/contact details exposed by the app, including email addresses where present in an accessible author or participant record, are intended to support professional contact and collaboration and can also be included in tool results. Review your profile and contact details and contact support to correct or remove information you no longer want available.

Choose recipients and review file contents before sending or publishing. Invitation addresses, collaborator emails, review submissions and meeting messages can concern other people. Supply them only for an authorized purpose and avoid unnecessary sensitive information. Conference blindness and admission rules still apply when using tools.

The current hosted Live Sessions configuration does not enable recording or AI participants. Live media goes through the enabled media provider to participants; MCP control-plane tools handle session state and chat, rather than returning raw audio/video or media credentials. Participants can independently capture what they receive.

Retention and deletion

Retention depends on the type of record and the action taken. Credential validity, content visibility, database deletion, runtime shutdown and backup expiry are separate events.

Account, posts and collaboration records

Kept while the account/content is maintained, until removed through an available product control or a verified request is processed. These records have no general automatic age-based deletion. Shared posts, reviews, transactions and other people’s contributions can require separate handling.

Workspace files, snapshots, AI and execution records

Persist so projects can reopen and results can be inspected or reused. Closing a workspace, cancelling a task, or disconnecting the plugin does not delete saved files, snapshots, prompts, output or published artifacts. There is no general automatic expiry for this saved content; request removal of the specific project and retained copies.

Sign-in and OAuth

Browser sessions can remain valid for up to 365 days; email sign-in codes are valid for 10 minutes. MCP authorization codes are valid for 5 minutes, access tokens for 1 hour, and refresh tokens for 30 days unless revoked earlier. Expiry or revocation stops use of the credential; related account, grant and security records are not necessarily deleted at that time.

Messages and notifications

Place-chat messages are normally visible for 24 hours, then become eligible for the scheduled expired-message purge. Live-session chat, workspace/channel/email conversations, delivery receipts, notifications and Discover decisions are durable records with no general automatic expiry. They are handled through available controls or verified requests.

Billing, safety and support

Transaction, tax, credit/usage, abuse-prevention, dispute and support records remain for the applicable accounting, legal, security or dispute purpose, including after account closure when necessary. Retention depends on the record and applicable obligation; there is no single automatic deletion period for these categories. We explain exceptions when responding to a request.

Infrastructure logs and backups

Our current Azure Log Analytics workspace default retention is 30 days and managed PostgreSQL point-in-time backup retention is 7 days. These settings do not cover every operator export, workspace snapshot, object-storage copy or provider record. Backups are not selectively edited for each request; restored data must be reconciled with completed deletion requests. Other retained copies require separate review and removal.

Recipients and external providers

Copies in ChatGPT/Codex, connected services, recipients’ inboxes, downloaded files and public caches follow those recipients’ policies and controls. Google Analytics retention follows the configured property and Google’s policy; it is separate from application logs. Removing a GetPaidX record does not remove those independent copies.

A deletion request is handled through support after verifying control of the account. We identify the affected records and storage, remove or de-identify information where applicable, and explain any records retained for legal, financial, security or other justified reasons. We do not promise instant erasure, a universal fixed purge deadline, or deletion of independent recipients’ copies.

Your choices and requests

• Edit profile details and external links in Profile settings, and review each post’s audience and publishing controls before sharing.
• Revoke a GetPaidX MCP OAuth connection or a personal access token in API settings. Disconnecting/removing the plugin in your AI client is a separate client control. Revoke each branded origin’s connection as applicable.
• Manage connected provider access in Workspace connections and, when needed, revoke authorization at the provider. Review post/workspace automation rules and disable scheduled or event-triggered work you no longer want.
• Manage optional email categories and device push in Notification settings, use email unsubscribe links, and remove browser/OS notification permission. Necessary sign-in, receipt, security or legal communications can still be required.
• Review Delegation and Organization settings to manage granted access; use billing settings for subscriptions. Cancelling payment or removing access does not itself delete records.
• Request access, a copy/export, correction, deletion, restriction, objection or withdrawal of optional consent by emailing support@getpaidx.com. Availability and exceptions depend on applicable law. We verify identity without asking for your password, explain the outcome and any limits, and respond within applicable legal timelines. There is no general self-service account-erasure or complete account-export button today.

You may also contact your local privacy regulator, including the Office of the Privacy Commissioner of Canada where applicable. Use ChatGPT/Codex and other recipients’ own controls for copies stored there.

Cookies, analytics and location

Essential cookies and browser storage support sign-in, anonymous-session continuity, referrals, app preferences and security. Clearing them or blocking them can sign you out or interrupt these features; it does not delete server-side records. Browser sessions can last up to one year. Browser/workspace profiles and service-worker caches have separate storage lifecycles.

On configured production hosts, Google Analytics measures page visits, referrals and interactions using cookies and technical data. The current site does not offer a dedicated analytics-consent toggle. You can block analytics with browser controls/extensions or Google’s opt-out tools and contact us about an objection or deletion request. Disconnecting the plugin does not disable analytics on a website you separately visit.

Location search uses the city, place or coordinates you enter or allow your browser to provide. Decline browser geolocation and use text/place selection instead. Check-ins, chosen places and published schedule/location details can be visible to the selected audience. A check-in is not a guarantee of someone’s physical presence.

Security and international processing

We use access controls, scoped authorization, transport encryption and protected credential storage to reduce unauthorized access. Authorized operators can access information needed to operate the service; no system can guarantee complete security. Report suspected unauthorized access to our support address and revoke affected connections.

WorkSchool 365 is in Canada, while hosting and providers can process information in the United States and other countries where they operate. We do not promise that all data remains in your country. Cross-border processing is subject to the applicable provider arrangements, safeguards and laws, including lawful access by authorities.

Children and policy changes

The service is intended for professional use and is not directed to children under 13 or a higher minimum age required by local law. Contact us if a child has supplied personal information. We update this policy as practices change, display the new date, and provide additional notice or seek consent when required for a material change.

Privacy contact: support@getpaidx.com. See also our Terms of Service.