Privacy Policy

1. Who we are

LimesWorth is operated by Ilija Anteski, an individual sole trader, under the LimesWorth brand. Privacy and data-related requests: hello@limesworth.com.

2. Account information

• Name
• Email address
• Password hash (passwords are not stored in readable form)
• Email verification status and related verification records
• Plan (for example Free, Solo, or Pro)
• Billing interval and subscription status, when a paid subscription exists
• Account creation date

Some older accounts may still have a historical project-credits balance from a previous one-time credit model. Project credits are not the current public pricing model and do not control current plan limits.

3. Business and profile information

• Business or professional name
• Contact person
• Email, phone, website, address, city, and country you choose to provide
• Company number and VAT / tax number if you enter them
• Currency preference
• Optional document note

4. Project information

• Project name, client name, description, status, pricing, hourly rate, and deadline
• Client profile details you enter for a project
• Scope baselines, scope items, effective-scope records, and related version history
• Client requests, classifications, commercial options, questions, counteroffers, and related review data
• Change Orders, versioned Change Orders, small-change records, and delivery or payment-condition records you use in the product
• Evidence events and Evidence Pack snapshots generated from stored project records

5. Uploads, contracts, and attachments

• Uploaded agreements or contracts, including filename, content type, and version metadata
• Inbox and intake attachments stored on disk when received
• Connected-account file attachments where a connected source supports them (for example Slack files, subject to granted permissions)

6. Client requests and change control

When you use request and change-control features, LimesWorth stores the request text, status, scope assessment, analysis and suggestion records, commercial terms you enter or review, client questions and answers, counteroffers, and Change Order content needed to run that workflow. AI suggestions are stored for your review. Human review remains required.

7. Evidence Packs

Evidence Packs are workflow records generated from stored project, request, Change Order, and evidence data. Downloading an Evidence Pack requires account login and project ownership. A public Evidence Pack share link, if you create one, uses a token URL.

8. Inbound email

LimesWorth can receive email sent to account or project intake addresses on the in.limesworth.com domain. Stored records may include sender, subject, body, received time, processing status, and attachments. Inbound delivery uses email routing into the application.

9. Connected accounts (Gmail, Outlook, Slack)

If you connect a supported third-party account, LimesWorth stores the connection information and credentials required to maintain that connection and perform the actions you authorize. Connection credentials are stored encrypted. Depending on the provider and permissions you grant, LimesWorth may retrieve message metadata, sender and recipient information, subject lines, message or channel content, timestamps, attachments, and files where supported.

Retrieved content is used to identify and review potential client requests or project evidence. Retrieving content does not by itself create a project or client request. You remain in control of reviewing and assigning imported items.

Connected-account data remains logically separated by workspace scope. The same Gmail mailbox may be connected independently in Personal and Agency scopes, with separate synchronization state and access controls for each connection. Outlook currently cannot be active in both Personal and Agency scopes for the same LimesWorth user or account context; simultaneous use requires separate LimesWorth user or account contexts and separate Outlook connections. This describes current LimesWorth behavior, not a restriction imposed by Microsoft or Outlook.

You may disconnect connected accounts from LimesWorth. You may also manage or revoke provider access through the relevant provider where available.

Gmail is connected through Composio. Forwarded-email intake on in.limesworth.com is a separate ingestion path and is not the Gmail connected-account path.

Google Workspace / Gmail Data

If you connect Gmail, LimesWorth uses Composio as the primary Gmail connection. Composio’s Gmail integration uses Google mailbox read access. LimesWorth does not request Gmail send, modify, or full-mailbox mail.google.com scopes. Direct Google OAuth using https://www.googleapis.com/auth/gmail.readonly remains in the product as a fallback connector and is not the current Connect Gmail control.

For the Composio Gmail path, new messages are delivered to LimesWorth through a signed Composio webhook. That is separate from forwarded-email intake.

For a connected Gmail account, LimesWorth may store:

• mailbox email address
• Composio connected-account identifier
• message sender, recipients, subject, and timestamps
• plain-text message body derived from the Gmail message
• allowed attachment files, filenames, content type, size, and checksums
• selected Gmail label identifier and name, and encrypted Google OAuth tokens, only if a leftover direct-Google connection is still present

Importing Gmail content does not by itself create a project or client request. You review imported items before assigning them.

If you disconnect Gmail, LimesWorth deletes locally stored Gmail OAuth credentials when they exist and attempts Google token revocation for those leftover credentials. Previously imported Gmail messages, bodies, and attachments are not automatically deleted. You may request deletion at hello@limesworth.com. You may also revoke access in your Google Account and through Composio where available.

Sharing and Disclosure of Google User Data

This section states with whom Google user data stored by LimesWorth may be shared, transferred, or disclosed.

LimesWorth does not sell Google user data.

LimesWorth does not use Google Workspace or Gmail user data for advertising.

Google user data that LimesWorth has imported may be transferred or disclosed as follows:

• OpenAI — Gmail-derived subject, body, attachment text, or related review context may be submitted to OpenAI only when you use an AI-assisted LimesWorth feature on content you have already imported (for example inbox request review, extraction from email, or scope analysis). The purpose is to return suggestions for that user-requested action. Connecting Gmail or importing Gmail messages does not by itself send mailbox content to OpenAI.
• Hosting / VPS provider — imported Gmail records, leftover direct-Google encrypted tokens when present, and stored attachment files reside on the application server used to host LimesWorth, because that is where the service stores account data.
• People you choose in the product — if you assign imported Gmail content into a project and later create a client request, Change Order, Evidence Pack, or public client link from that workflow, the resulting text may be shown to recipients of those records.

Protection of Sensitive Google User Data

LimesWorth uses the following application controls for Gmail connection data and imported Gmail content:

• Leftover direct-Google OAuth access and refresh tokens, when present, are encrypted at rest with Fernet authenticated encryption before they are stored. Tokens are not stored in plaintext. The Composio Gmail path does not store Google OAuth tokens in LimesWorth.
• The public LimesWorth website is served over HTTPS.
• Gmail connect, disconnect, and review of imported Gmail content require a signed-in LimesWorth account.
• Gmail connect and disconnect use CSRF protection on those authenticated POST requests.
• Imported Gmail records are stored against the owning LimesWorth account and are not a shared workspace.
• Composio Gmail webhooks are accepted only after signature verification. Direct Google OAuth fallback uses the gmail.readonly scope when that path is used.
• Session cookies are HttpOnly, HMAC-signed, SameSite=Lax, and Secure in production.
• On Gmail disconnect, LimesWorth deletes locally stored Gmail OAuth credentials when they exist and attempts Google token revocation for those leftover credentials.

This list describes application-level controls. It is not a SOC 2, ISO 27001, or penetration-test claim, and it does not describe database disk encryption or a named key-management service.

AI Processing of Google Workspace Data

LimesWorth does not use Google Workspace API user data to develop, improve, or train generalized or non-personalized AI or machine-learning models.

Submitting Gmail-derived content to OpenAI for a user-requested AI feature is processing for that feature. It is not LimesWorth using Google user data to train generalized AI models.

OpenAI’s published documentation for its API states that API inputs and outputs are not used to train OpenAI models by default unless the API customer opts in. That is OpenAI’s published API default, not a LimesWorth guarantee of a specific retention period, zero-retention configuration, or data-residency region.

10. Payments

Paid Solo and Pro subscriptions are processed by Paddle, which currently acts as the Merchant of Record. LimesWorth does not store complete payment-card details. Payment-related records may include plan, billing interval, subscription status, subscription end time, Paddle customer, subscription, and price identifiers, order, event, or transaction identifiers, customer email, product or price identifiers, and payment or processing status.

Historical one-time credit purchases, where they still exist, may have related order and credit-processing records. Those records are legacy.

11. Sessions and cookies

LimesWorth uses an essential HMAC-signed session cookie to keep you signed in. Session cookies are HttpOnly, HMAC-signed, SameSite=Lax, and Secure in production.

12. Logs and analytics

Server and application logs may contain operational events, errors, or email and extraction warnings. LimesWorth uses self-hosted Umami for page-view analytics on parts of the public website.

13. AI features and data sent to OpenAI

LimesWorth uses OpenAI for AI-assisted features when you use them, including scope analysis, extraction from email or requests, document/image/PDF vision extraction, and optional wording or classification suggestions.

Depending on the feature, project baseline text, client request text, email subject and body, attachment text, uploaded contract or document content, and related review context may be sent to OpenAI. AI output is stored as suggestions and review data in your account. Human review remains required: AI suggests, you decide.

OpenAI’s published documentation for its API states that API inputs and outputs are not used to train OpenAI models by default unless the API customer opts in. That is OpenAI’s published API default, not a LimesWorth guarantee of a specific retention period, zero-retention configuration, or data-residency region.

14. How we use information

We use information to provide the service, authenticate accounts, verify email addresses, keep project records separated by account, process requests and Change Orders, maintain evidence timelines, sync connected accounts you authorize, handle subscriptions and payments, send notifications, provide support, and operate the product safely.

We do not sell personal data.

15. Third-party service providers

Providers that may process data for LimesWorth:

• OpenAI — AI analysis and extraction when you use AI features
• Paddle — payment processing and Merchant of Record for current paid subscriptions
• Composio — Gmail connection and message delivery if you connect Gmail
• Google — Gmail mailbox read access through Composio if you connect Gmail, and leftover direct Google OAuth if that fallback path is used
• Microsoft — Outlook / Microsoft 365 OAuth and mailbox read access if you connect Outlook
• Slack — Slack OAuth and selected channel/message/file read access if you connect Slack
• Self-hosted Umami — website page-view analytics
• SpaceMail — mailbox and SMTP for some outbound messages from hello@limesworth.com
• Resend — transactional email for email verification and covered client messages, plus delivery-status events
• Cloudflare — inbound email routing to LimesWorth intake addresses
• Hosting / VPS provider — application hosting and file storage

We do not publish a data residency or hosting-region guarantee on this page.

16. Public client links

Public client links may allow a recipient to view and, where supported, respond to selected LimesWorth workflow records without creating an account.

17. Data retention

We keep account and project records while your account and projects are active, unless deletion is requested and we are legally or operationally required to retain some records. Backup copies may remain for a limited period after deletion. Payment, security, fraud-prevention, and similar records may need to be kept longer. We do not publish a fixed retention schedule on this page.

18. Your choices

You may update account and business-profile details in the service, and you may connect or disconnect supported third-party accounts. You may request access, export, correction, or deletion by contacting hello@limesworth.com. Some records may need to be retained for payment, security, fraud-prevention, or legal purposes.

19. Changes to this policy

This policy may be updated as LimesWorth develops. The latest version and its effective date will be published on this page.

20. Contact

Privacy and data-related requests: hello@limesworth.com