Tomwiser
Get started

Tomwiser

Privacy Policy

Last updated: 18 September 2026

1. Introduction

Tomwiser LLC ("we," "our," or "us") operates a service that answers questions, asked in plain language, about what a team has been working on. An answer comes from the work the team has connected (the "Service"). This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our Service. By using our Service, you agree to the collection and use of information in accordance with this policy.

2. Information We Collect

2.1 Personal Information

We collect information you provide directly to us, such as:

  • Account information (name, email address, company name)
  • Communication preferences and support requests

2.2 Activity

To answer questions about what a team has been working on, we collect:

  • GitHub activity data (commits, pull requests, reviews, issues, comments and discussions: titles, timestamps, repository names, who wrote them, and the text that comes with a commit, a pull request, an issue, a comment or a discussion)
  • Google Calendar event data (meeting times, titles, descriptions, and how many people were invited)
  • Error tracker data, where you connect one. From Sentry we read an incident when an error is first seen, a regression when a fixed one returns, a resolution when it stops, and the release an error was first and last seen in, which Sentry names on the error itself. From Bugsnag we read an incident, a resolution, a release when a version ships, and never a regression, because Bugsnag puts no date on one. What we keep of either is the title, the culprit or error class, the message, the level, the project, the release stage, and how often it happened and how many people it reached
  • Integration connection status and configuration preferences

Important: We store the activity events we read - commits, pull requests, reviews, issues, comments, discussions, calendar entries, incidents, regressions, resolutions and releases, with their titles and the names the source recorded - because an account of the work is derived from them and has to remain checkable against them. We also store the text that comes with them: the body of a commit message, the description on a pull request, the whole post of an issue, a comment or a discussion, and the description on a calendar entry. Tomwiser does not read the contents of your files.

From an error tracker we store what broke and what was fixed, and nothing that attributes it to a person. Sentry records who an error was assigned to and which changes it blames; we read neither. We also never store a stack trace, because it would say what is inside your files.

Activity older than our full-fidelity window is compacted into a rollup: a single stored summary standing for a period of work, kept so that a claim made about an old week remains checkable after the individual events behind it have gone. An event that an account of the work cites is never compacted.

2.3 Usage Information

We automatically collect certain information about your use of the Service:

  • Log data (IP address, browser type, access times, pages viewed)
  • Service usage patterns and feature utilization

3. How We Use Your Information

We use the collected information to:

  • Provide, maintain, and improve the Service
  • Read activity from GitHub and Google Calendar to generate an account of what a team built
  • Store those activity events, and the accounts generated from them, so a claim can be traced to the activity behind it
  • Deliver an account of a team's work by email, to Slack, and onto a Notion page
  • Communicate with you about service updates, security alerts, and support
  • Analyze usage patterns to improve our AI engine and service features
  • Ensure compliance with our Terms of Service and applicable laws

4. Information Sharing and Disclosure

We do not sell, trade, or rent your personal information to third parties. We may share your information in the following circumstances:

  • Service Providers: With the providers who host the Service and run the model that generates an account of the work
  • Legal Requirements: When required by law, court order, or to protect our rights and safety
  • Business Transfers: In connection with a merger, acquisition, or sale of assets
  • Consent: With your explicit consent for specific purposes

5. Data Security

We implement appropriate technical and organizational security measures to protect your information:

  • Encryption of data in transit
  • Regular security assessments and updates
  • Access controls and authentication mechanisms
  • Hosting on managed infrastructure that holds its own physical and access controls
  • Employee training on data protection and privacy practices

While we strive to protect your information, no method of transmission over the internet or electronic storage is 100% secure.

6. Data Retention

We retain your information for as long as necessary to provide our Service and fulfill the purposes outlined in this Privacy Policy:

  • Account information: Retained while your account is active, and deleted when you delete your account
  • Activity events: Stored while there is somebody in your workspace, because an account of the work is derived from them and has to remain checkable against them. When the last person deletes their account there is nobody left with a claim on them and they are deleted too
  • Generated accounts of work: Kept while there is somebody in your workspace, so a past week can still be read and its claims traced to the activity behind them. The workspace is deleted when its last member deletes their account, and everything in it goes with it
  • Questions you ask: Kept so you can read your own history, and deleted when you delete your account. Your workspace administrator can also set a shorter window. After it, the text of the question is removed and the row is kept: we still hold that a question was asked, when, and what it cost to answer, because that is what stops anybody exceeding their limit by waiting
  • Legal requirements: Some data may be retained longer to comply with legal obligations

7. Your Rights and Choices

Depending on your location, you may have certain rights regarding your personal information:

  • Access: Request access to your personal information we hold
  • Correction: Request correction of inaccurate or incomplete information
  • Deletion: Delete your account at any time from your profile settings. See "What deleting your account does" below
  • Portability: Ask us for a copy of your account and the activity your workspace holds. There is no self-service export yet, so this is a request we answer by hand
  • Opt-out: Unsubscribe from marketing communications
  • Objection: Object to processing, or ask your workspace administrator to disconnect a source

To exercise these rights, please contact us at support@tomwiser.com.

7a. Who controls your data

Two different things are held under this Service and they are controlled by different people.

  • Your account - your name, your email address, your job title, and the questions you ask. We control this, and you can delete it yourself at any time.
  • Your workspace's activity - the commits, pull requests, reviews, issues, comments, discussions and calendar events read from the tools your team connected, and the accounts of work generated from them. Your employer or whoever administers your workspace controls this. We process it on their instructions.

Where we are a processor rather than a controller, a request to erase or export that activity is one we pass to the workspace administrator, who decides. This is the same division used by the other tools your workspace connects.

7b. What deleting your account does

Deleting your account is immediate and cannot be undone. Specifically:

  • Your account record is deleted, with your name, email address and job title.
  • Every question you have asked is deleted. Nobody else has a claim to it.
  • Any connections you authorised are removed, so we stop reading through them.
  • Activity events are not deleted, and your name and email address are removed from them.

We do not delete the activity itself because a commit is two things at once. It is personal data about you, and it is your workspace's record of what was built - which other people rely on, and which the accounts of work already generated cite. Removing it would delete your employer's record and would silently change what every past account of that period says. Removing your name from it means the record of the work remains and the record of who did it does not.

If you would rather the activity itself were deleted, that is a decision for the workspace administrator who controls it, and we will act on their instruction.

Anything you connected - a repository, a calendar - passes to whoever is left in your workspace, because the team still reads it. If you are the last person in your workspace, there is nobody left with a claim on what it gathered, so it is deleted with you.

8. Third-Party Integrations

Our Service reads activity from third-party platforms and delivers an account of that work:

  • GitHub: We read commits, pull requests, reviews, issues, comments and discussions, including the text that comes with a commit, a pull request, an issue, a comment or a discussion
  • Google Calendar: We read calendar events, including their descriptions
  • Sentry: We read incidents, regressions, resolutions and the releases named on them, from the projects you connect. We never read a stack trace, the person an error is assigned to, or the changes Sentry blames for it
  • Bugsnag: We read incidents, resolutions and releases from the projects you connect, through a personal auth token you supply, and no regression because Bugsnag does not date one. We never read a stack trace or the person an error is assigned to
  • Delivery: We deliver an account of a team's work by email, to Slack, and onto a Notion page
  • Notion: Where you choose a Notion page, we write each account of your team's work onto it, with the newest first and earlier ones kept below it. We read only the names of the pages you share with the integration, so that we can offer them to you. We ask Notion for no information about you or anyone else
  • Google Analytics: We measure visits to the public website. It is not connected to your workspace or to any activity we read.
  • Web3Forms: The contact form on this site posts your name, email, company and phone to Web3Forms, which forwards it to us as email. Only what you type in that form.

These integrations are subject to the privacy policies of the respective third-party services. We recommend reviewing their privacy policies to understand how they handle your data.

9. International Data Transfers

Tomwiser LLC is based in the United States. If you are located outside the United States, please note that your information may be transferred to, stored, and processed in the United States. We ensure appropriate safeguards are in place for international data transfers in accordance with applicable data protection laws.

10. Children's Privacy

Our Service is not intended for children under 13 years of age. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe your child has provided us with personal information, please contact us immediately.

11. California Privacy Rights

If you are a California resident, you may have additional rights under the California Consumer Privacy Act (CCPA), including:

  • The right to know what personal information we collect and how we use it
  • The right to delete personal information we have collected, or to have it deidentified where deletion is not available
  • The right to opt-out of the sale of personal information (we do not sell personal information)
  • The right to non-discrimination for exercising your privacy rights

12. European Union (GDPR) Compliance

If you are located in the European Union, you have additional rights under the General Data Protection Regulation (GDPR):

  • Right to be informed about data processing
  • Right of access to your personal data
  • Right to rectification of inaccurate data
  • Right to erasure ("right to be forgotten"), which we honour by deleting your account and removing your name from activity your workspace controls
  • Right to restrict processing
  • Right to data portability
  • Right to object to processing
  • Rights related to automated decision-making

Our lawful basis for processing your data includes contract performance, legitimate interests, and consent where applicable.

13. Cookies and Tracking Technologies

We use cookies and similar tracking technologies to enhance your experience:

  • Essential Cookies: Required for basic service functionality
  • Analytics Cookies: We use Google Analytics to count visits and see which pages are read. Google acts as a processor for this and its own privacy terms apply. We do not use it to identify you.
  • Preference Cookies: Remember your settings and preferences

You can control cookie settings through your browser preferences. Note that disabling certain cookies may affect Service functionality.

14. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We will notify you of any material changes by:

  • Posting the updated policy on our website

Your continued use of the Service after changes become effective constitutes acceptance of the updated Privacy Policy.

15. Contact Information

If you have questions about this Privacy Policy or our data practices, please contact us:

  • Email: info@tomwiser.com
  • General Support: support@tomwiser.com
  • Registered address: Tomwiser LLC, c/o Entity Protect Registered Agent Services LLC, 417 Main St. Suite 111N, Little Rock, AR 72201-3801, United States. This address identifies us. It is our registered agent and receives service of process only, so a letter sent there about your data will not reach us. Write to support@tomwiser.com instead.