Terms of Service

1. Agreement to these Terms

By creating an account, accessing app.projark.com, or using any part of the Service, you agree to these Terms.

If you are accepting on behalf of a company, agency, or other organization, you confirm that you have the authority to bind that organization, and "you" means both you personally and that organization. If you don't have that authority, don't accept these Terms.

You must be legally capable of entering into a contract. Projark is a business product and is not intended for personal or household use.

2. Definitions

• Service — the Projark application at app.projark.com, the marketing site at projark.com, and any related features, APIs, and support we provide.
• Workspace — the top-level container in Projark. A Workspace holds Clients, which hold Projects. Every Workspace has one owner.
• Customer Content — everything you or your users put into, connect to, or generate through the Service: workspaces, client records, projects, topics, tasks, comments, notes, milestones, chat messages, links, uploaded files, keyword and strategy data, tracked AI-search prompts, competitor registries, rank-tracking history, website context profiles, per-user activity records such as project visits and stars, and data retrieved from third-party services you connect.
• User — any individual who signs in to the Service, whether they're a workspace member or a person invited into a single project.

3. Accounts

3.1 Accurate information

You must provide accurate account information — a real email address and display name — and keep it current. We use your email for sign-in, invitations, password resets, and service notices sent from noreply@projark.com.

3.2 Credential security

Authentication is handled by Supabase Auth using email and password or Google OAuth. You are responsible for keeping your password and any connected Google account secure. Tell us at momin@missionseo.com immediately if you believe an account has been compromised.

3.3 Responsibility for account activity

You are responsible for all activity that occurs under your account. Activity performed with your credentials is treated as yours, whether or not you authorised it. Sharing your credentials does not transfer that responsibility, and is prohibited under Section 3.4 — use workspace or project invitations instead.

3.4 One person, one account

Accounts are for individuals. Don't create shared "team" logins — use workspace invitations instead, so that access can be granted and revoked properly.

4. Workspaces, roles and invitations

4.1 The owner controls the workspace

Each Workspace has an owner. The owner controls who has access, what those people can see and do, and whether the Workspace continues to exist. The owner can delete the Workspace. Deletion cascades to workspace memberships, clients, projects, topics, tasks, comments and the associated file storage (Section 11.3). Invoices and usage/cost ledger events are retained afterwards for accounting (Section 11.4), and deleting a Workspace does not delete any individual user account — see Section 11.3 for how account deletion works.

4.2 Two kinds of access

• Workspace access — a person invited into a Workspace can see and act on data across that Workspace, according to the role and capabilities they've been granted.
• Project-scoped access — a person invited into a single Project sees only that Project. This is how client reviewers and external specialists are typically added.

Capability checks are re-validated on our servers on every privileged action, and there is an invite privilege ceiling: you cannot grant someone a role or capability higher than your own.

4.3 You are responsible for who you let in

When you invite someone, you are deciding that they may see the Customer Content that their access level exposes — including client company information, connected analytics and CRM data, and anything anyone has written into the project. That decision is yours, not ours. You are responsible for:

• Having permission from your own clients to put their data into Projark and to show it to the people you invite.
• Removing users promptly when they should no longer have access.
• The actions of everyone you invite.

4.4 Connected credentials are project-level, not personal

This is important and easy to get wrong. When someone connects a third-party integration (Google, Bing, HubSpot, Salesforce) to a Project, the resulting credential is stored at the project level and can be used by the server on behalf of any member of that Project — and also on its own, from scheduled background jobs that refresh data such as rank-tracking history while nobody is signed in. It is not scoped to the individual who connected it.

If the person who connected an integration is later removed from the Project, their stored credential remains and stays usable until someone explicitly disconnects that integration. If that matters to you, disconnect the integration as part of your offboarding process.

5. Plans, billing and taxes

5.1 Plans

• Free — $0/month
• Pro — $299/month
• Max — $499/month

Plus metered AI-usage overage credits, charged for AI and API operations beyond any usage allowance included in your plan. Allowances and overage rates are the ones shown at checkout and in your billing settings at the time you subscribe. We record a usage and cost ledger of these operations per workspace.

5.2 Plans are per person, not per workspace

A plan attaches to a person, and applies to every Workspace that person owns.

If you work inside someone else's Workspace, that Workspace runs on its owner's plan, not yours. You do not need your own paid plan to be a member of someone else's paid Workspace, and your own plan does not upgrade a Workspace you don't own.

5.3 Payment

Payments are processed by Stripe through Stripe Checkout and the Stripe Customer Portal. Card details are handled entirely by Stripe and are never stored on Projark servers. We store a Stripe customer id, your subscription status, invoices, and your credit ledger. Your use of Stripe is subject to Stripe's own terms.

5.4 Renewal and cancellation

Paid plans renew automatically each month until cancelled. You can cancel at any time through the Stripe Customer Portal. Cancellation takes effect at the end of the current billing period — you keep access until then.

5.5 No partial refunds

Fees are non-refundable, including for partial billing periods and for periods where you didn't use the Service, except where a refund is required by law.

5.6 Failed payments

If a payment fails, we may suspend access to paid features until the balance is settled. Metered overage charges already incurred remain payable.

5.7 Price changes

We may change prices. We'll give you notice before a change takes effect for you, and the new price applies from your next billing period after that notice. If you don't accept the new price, cancel before it takes effect.

5.8 Taxes

Prices are exclusive of taxes. You are responsible for any sales, use, VAT, GST, or similar taxes arising from your purchase, other than taxes on our income.

6. Customer Content

6.1 You own your content

You keep whatever rights you hold in your Customer Content, and we don't claim ownership of it. Two clarifications: data retrieved from third-party services you connect remains subject to those providers' terms (Section 7.3), and AI outputs are produced by third-party models — your rights in them are determined by those providers' terms, and we make no representation that they are original or exclusive to you (Section 8).

6.2 The licence you give us

You grant Mission SEO a non-exclusive, worldwide, royalty-free licence to host, store, copy, transmit, display, and process your Customer Content solely to operate and provide the Service to you — including transmitting it to the subprocessors listed in Section 7.4 where that is needed to deliver a feature you're using.

This licence exists to run the product. It ends when the content is deleted from the Service, except that (a) the invoice and usage/cost ledger records described in Section 11.4 are retained, and (b) copies held outside the Service that we do not control and cannot delete on your behalf — including content already transmitted to AI or data providers, email delivered through our transactional email provider or held in our support inbox, and provider-side backups — cannot be recalled by us. Their retention and deletion is governed by that provider's own terms.

6.3 You must have the rights

You represent that you have the rights and permissions necessary for:

• All Customer Content you upload, write, or generate in the Service.
• Any website you ask Projark to crawl. Projark fetches pages from the website you designate in order to build its context profile, and reads public SERP data. You must own that website or have authorization from its owner.
• Any third-party account you connect (Section 7).
• Any client data you place in the Service, including data about identifiable people that arrives through a connected CRM.

6.4 Crawling behaviour

When Projark crawls a site you've designated, it sends a Chrome user-agent and, optionally, a per-project verification header that you can allowlist in your own Cloudflare configuration. You are responsible for ensuring the crawl is authorized on the target site.

6.5 Feedback submissions

The feedback form in the application at app.projark.com — available there whether or not you're signed in to an account — collects your comment, up to five optional images (PNG/JPG, 5MB each, validated by file signature), and automatically collected context about the page and session the submission came from. Submissions are stored in a private bucket and emailed to momin@missionseo.com; that email copy sits in a Mission SEO mailbox, is not removed when a workspace or project is deleted, and is retained until we delete it on request. It's protected by Cloudflare Turnstile. Don't put credentials or sensitive personal data into feedback.

If you send us product suggestions, we may use them to improve the Service without obligation to you.

7. Third-party services and subprocessors

7.1 Connections are your choice

Projark can connect, per project, to Google Search Console, Google Analytics 4, Google Ads, Google Docs, Bing Webmaster Tools, HubSpot, and Salesforce. Every connection is initiated by you.

When connected, Projark retrieves and displays data such as search queries, impressions and clicks; sessions, conversions and landing pages; ad campaign performance; CRM contacts, deals, leads, opportunities and revenue; and the text of a Google Doc explicitly linked to a task.

7.2 You must have authority to connect

You confirm that you're authorized to connect each account and to allow Projark to access the data in it — including where the account belongs to your client rather than to you.

7.3 We don't control them

These providers set their own terms, pricing, rate limits, API versions, and access policies. Your use of them is governed by their terms, not ours. We are not responsible for their availability, accuracy, changes, deprecations, or decisions to restrict access — any of which may break or degrade a Projark feature without notice.

7.4 Subprocessors

We use the following providers to deliver the Service:

• Supabase — database, authentication, file storage, realtime.
• Sevalla — application and website hosting.
• Resend — transactional email (invites, password resets, notifications, and delivery of feedback-form submissions), sent from noreply@projark.com.
• Cloudflare — Turnstile CAPTCHA.
• Trigger.dev — background job workers.
• Anthropic — AI processing.
• OpenAI — AI processing.
• DataForSEO — SERP and keyword data.
• Stripe — payment processing.
• Google, Microsoft Bing, HubSpot, Salesforce — only when you connect them.

7.5 How we protect connected credentials

OAuth refresh and access tokens and API keys are encrypted with AES-256-GCM using a key held separately from the database credentials, and the credential columns are locked at the database level so browser-tier clients cannot read them. OAuth connection flows are protected against CSRF using a short-lived httpOnly state cookie and nonce verification.

8. AI features

Read this section carefully. It describes a real limitation of the product, not a formality.

8.1 What we send to AI providers

Parts of your Customer Content are sent to third-party AI providers — Anthropic (Claude) and OpenAI (GPT) — to generate results. What we send includes: keywords, tracked AI-search prompts, text scraped from the website you designated, competitor names and domains, SERP result titles and URLs, task and topic titles and briefs, and the text of a Google Doc linked to a task. Some AI calls use the providers' built-in web-search tools, which issue live web searches.

By using AI features, you're instructing us to send that content to those providers. What those providers retain, and whether they use inputs to improve their own models, is governed by their terms — we do not control that and make no commitment on their behalf. See our Privacy Policy, Section 5.

8.2 Outputs are non-deterministic

AI outputs are generated by third-party models and are non-deterministic. The same input can produce different answers on different runs. AI-search and AEO ranking results in Projark are directional, not position-exact.

8.3 Outputs may be wrong

AI outputs may be inaccurate, incomplete, outdated, or fabricated. We do not verify them. You must have a human review any AI output before you rely on it, act on it, send it to a client, or publish it.

8.4 Not professional advice

AI outputs — and Projark's analyses, recommendations, and reports generally — are not legal, financial, medical, or other professional advice.

8.5 No outcome is guaranteed

We do not warrant, promise, or guarantee any search ranking, AI-search visibility, traffic level, conversion rate, revenue, or any other SEO or marketing outcome. Nothing in the Service, our marketing site, or our support communications should be read as such a guarantee.

8.6 Third-party data accuracy

Data retrieved from DataForSEO, from connected providers, and from live web searches is provided as those sources supply it. We don't independently verify it.

9. Acceptable use

You may not, and may not permit anyone else to:

• Use the Service for anything illegal, or in violation of any applicable law or regulation.
• Upload, store, or process content that infringes someone else's intellectual property, privacy, or other rights.
• Direct Projark to crawl or analyse a website you don't own and aren't authorized to crawl, or connect an account you aren't authorized to connect.
• Attack the Service — including denial-of-service attempts, probing or scanning for vulnerabilities without our written permission, or attempting to access data belonging to another workspace or user.
• Reverse-engineer, decompile, or attempt to derive the source code or underlying models of the Service, except where that restriction is unenforceable by law.
• Circumvent rate limits, usage metering, plan limits, or billing — including by creating multiple accounts to avoid paid limits.
• Upload malware, or files designed to exploit or damage any system.
• Use the Service, or any data or output from it, to build or train a competing product or service.
• Resell, sublicense, or provide the Service to third parties as your own product. (Using Projark to deliver services to your own clients, including inviting them into projects, is expressly allowed and is the point of the product.)
• Submit other people's personal data through the feedback form, or use it to send abusive content.

We may investigate suspected violations and take action under Section 11.

10. Service availability and changes

10.1 No uptime guarantee

We do not offer a service level agreement or an uptime guarantee. The Service may be unavailable due to maintenance, provider outages, third-party API failures, or other causes.

10.2 Maintenance

We may perform maintenance at any time, with or without notice. We'll try to minimise disruption where a change is planned and significant.

10.3 Features change

We may add, modify, or remove features, including features you use, and including changes forced on us by a third-party provider changing or removing its API. We are not obliged to maintain any particular feature. If we remove something material to a paid plan, your remedy is to cancel under Section 5.4.

10.4 Limits

We may apply reasonable technical limits — rate limits, storage caps, upload size caps (currently 5MB per feedback image, PNG/JPG, validated by content inspection), and AI usage metering.

11. Suspension and termination

11.1 We may suspend or terminate

We may suspend or terminate your access, or a workspace's access, if:

• Payment fails or an account is past due.
• You breach these Terms, including Section 9.
• Your use creates a security, legal, or operational risk to us, to other customers, or to a third-party provider.

Where it's reasonable to do so, we'll contact you first and give you a chance to fix the problem. Where the risk is immediate, we may act first and explain afterwards.

Note that a staff-initiated deletion of an individual user account is blocked if that user owns a workspace or has authored content such as comments, topics, or tasks. In that case the account is suspended rather than deleted.

11.2 You may cancel

You can cancel a paid plan at any time through the Stripe Customer Portal (Section 5.4). You can stop using the Service at any time.

11.3 Deleting your data

• Workspace deletion — a workspace owner can delete their own workspace self-serve, with type-to-confirm. This cascades: workspace memberships, clients, projects, topics, tasks, comments, and the associated file storage are deleted. User accounts themselves are not deleted by this action.
• Project deletion — a project can be deleted, cascading its data and file storage.
• Individual account deletion — there is no self-serve "delete my account and all my data" flow yet. To have an individual account deleted, email momin@missionseo.com and we'll handle it manually. As described in 11.1, an account that owns a workspace or has authored content can't be deleted outright; the workspace or content has to be dealt with first, and otherwise the account is suspended.

Records attached to a deleted project — notes, milestones, chat messages, links, keyword research, content strategy analyses, AI-search prompts, competitor registries, rank-tracking history, website context profiles, and per-user visit and star records — go with the project they belong to. We do not operate automated data-retention schedules or an automated erasure pipeline. Deletion outside the self-serve paths above is a manual process handled on request.

11.4 What survives deletion

The following are deliberately kept after a workspace is deleted:

• Invoices — retained, with the workspace reference removed, for accounting.
• Usage and cost ledger events — retained for accounting.
• User accounts — deleting a workspace does not delete anyone's individual account or their account data.
• Audit log entries recording privileged staff actions, and feedback submissions, which are held outside workspace storage.
• Copies already transmitted to third-party providers, which we cannot recall.

11.5 Effect of termination

On termination, your right to use the Service ends immediately. Fees already incurred remain payable. Sections that by their nature should survive — including Sections 6.1, 11.4, 12, 13, 14, 15, and 17 — survive termination.

Projark does not currently provide a bulk data export. Copy out anything you need before you delete a workspace or project — deletion cascades and we cannot recover it for you. If you need a copy of workspace data, email us before deleting and we'll tell you what we can produce manually.

12. Confidentiality

Each of us may learn non-public information about the other through this relationship. Each party agrees to protect the other's confidential information with reasonable care, use it only to perform under these Terms, and not disclose it to anyone other than employees, contractors, and the subprocessors listed in Section 7.4 who need it to deliver the Service. We engage those subprocessors under their standard published terms and rely on the confidentiality and security commitments in those terms; we do not represent that each subprocessor is bound by obligations identical to these.

This doesn't apply to information that is public through no fault of the receiving party, was already known without a duty of confidence, is independently developed, or must be disclosed by law — in which case the disclosing party gets notice where legally permitted.

Your Customer Content is your confidential information. We access it only as needed to operate the Service, provide support, investigate abuse, or comply with law. Privileged staff actions are recorded in an append-only audit log. That log covers privileged administrative actions; it is not a complete record of every occasion on which a staff member views Customer Content while providing support or debugging.

13. Disclaimers

The Service is provided "as is" and "as available", to the maximum extent permitted by law.

We disclaim all warranties, express or implied, including implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement.

We specifically do not warrant that:

• The Service will be uninterrupted, timely, secure, or error-free.
• AI outputs, SERP data, keyword data, rank-tracking history, or data from connected providers will be accurate, complete, current, or reproducible.
• The Service will produce any particular ranking, traffic, revenue, or marketing result.
• Third-party providers will remain available or continue to offer the APIs Projark relies on.

We hold no certifications under SOC 2, ISO 27001, HIPAA, or any similar framework, and make no claim to any. The security measures we do implement are described in Sections 4.2, 7.5, 10.4 and 12 of these Terms and, in full, in Section 10 of our Privacy Policy; they reduce risk but do not eliminate it, and no system is completely secure.

Nothing here excludes a warranty that cannot be excluded by law.

14. Limitation of liability

To the maximum extent permitted by law:

• No indirect damages. Neither party is liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, lost data, loss of goodwill, or business interruption — even if advised such damages were possible.
• Cap. Each party's total aggregate liability arising out of or relating to these Terms or the Service is limited to the amount you actually paid Mission SEO for the Service in the twelve (12) months immediately preceding the event giving rise to the claim.
• Where you have paid nothing. If you have not paid Mission SEO any fees in the twelve (12) months preceding the event giving rise to the claim — including because you are on the Free plan, or because you are a member of a Workspace billed to its owner under Section 5.2 — our total aggregate liability to you is limited to USD $100.

These limits apply regardless of the legal theory — contract, tort, negligence, strict liability, or otherwise — and apply to any claim relating to AI outputs, third-party provider behaviour, data loss, or deletion.

They do not apply to your payment obligations, your indemnity under Section 15, or to liability that cannot be limited by law. We allocate risk this way because the fees for the Service reflect it.

15. Indemnity

You will defend, indemnify, and hold harmless Mission SEO and its personnel from any third-party claim, loss, liability, damage, or expense (including reasonable legal fees) arising from:

• Your Customer Content, including any claim that it infringes or misappropriates someone's rights.
• Your use of the Service, including anything done under your account or by users you invited.
• Your instruction to crawl a website, or your connection of a third-party account, where you lacked the necessary rights or authority.
• Your handling of your clients' data or the personal data of individuals in it.
• Your breach of these Terms or of applicable law.
• Any decision made or content published based on AI output without adequate human review.

We'll notify you of the claim, let you control the defence (subject to our approval of any settlement that admits fault or imposes obligations on us), and cooperate reasonably at your expense.

16. Changes to these Terms

We may update these Terms. When we do, we'll change the "Last updated" date at the top and, for material changes, give notice by email or in the app before the change takes effect.

Continuing to use the Service after a change takes effect means you accept the updated Terms. If you don't accept them, cancel your plan and stop using the Service.

17. Governing law and disputes

These Terms are governed by the laws of the Province of Ontario and the federal laws of Canada applicable in that province, without regard to conflict-of-laws rules. The courts of the Province of Ontario have exclusive jurisdiction over any dispute arising out of or relating to these Terms or the Service, and both parties consent to that jurisdiction and venue.

This is the single governing-law provision for both these Terms and our Privacy Policy.

Before filing anything, contact us at momin@missionseo.com and give us 30 days to resolve the issue informally. Most disputes get sorted this way.

18. General

• Entire agreement. These Terms, together with our Privacy Policy, are the whole agreement between us about the Service, and replace any earlier understandings. Terms on your purchase order or vendor form do not apply unless we sign them.
• Assignment. You may not assign these Terms without our written consent. We may assign them to a successor in connection with a merger, acquisition, or sale of assets.
• Severability. If a provision is unenforceable, the rest stays in force and the unenforceable part is narrowed to the minimum extent needed.
• No waiver. Not enforcing a term once doesn't waive it.
• No third-party beneficiaries. These Terms don't create rights for anyone other than you and us.
• Force majeure. Neither party is liable for delays or failures caused by events beyond its reasonable control, including provider outages and network failures.
• Independent parties. Nothing here creates a partnership, joint venture, employment, or agency relationship.

19. Contact

Projark is operated by Mission SEO.

• Email — momin@missionseo.com
• Marketing site — projark.com
• Application — app.projark.com

For billing questions, account deletion requests, security reports, or anything about these Terms, email momin@missionseo.com.