1. Data Controller

Orwell's bad dream is the data controller responsible for your personal data under this policy. You can reach the data controller at martinvfalck@gmail.com.

2. What This App Does

Orwell's bad dream ("the App", "we", "our") is a collaboration tool for small teams. It lets you and your teammates keep a shared record of outreach — who you contacted, through which channel, when, with what comments and contact details — and surfaces that shared record when any of you opens that person's LinkedIn profile or an email thread they are on. You can group people into lists and move them through stages, tag each other in comments, and mark profiles with your team's own labels. Optionally, you can connect your own HubSpot, Luma, Google Sheets, Microsoft Excel or Attio accounts so matching data from those systems appears on the profile as well.

3. Legal Basis for Processing (GDPR Article 6)

The App processes two kinds of personal data under two different legal bases:

3.1 — Your own data, as a user of the App. When you sign up, connect an integration, or use the App's features, processing is carried out to perform the contract between you and us (Article 6(1)(b)) and — for each optional integration — on the basis of your explicit consent granted at the moment you connect it (Article 6(1)(a)). You can withdraw that consent at any time by disconnecting the integration, leaving the team, or deleting your account (see Section 8).

3.2 — Data about people who are not users of the App. The App's core function is to let a team keep a shared record of professional outreach. That record necessarily contains personal data about the people being contacted (public LinkedIn profile identifier, display name, any email a teammate types in or that arrives via a connected integration, any notes teammates write, and a timestamped log of when any team member opened that person's LinkedIn profile page). These data subjects have not signed up themselves and cannot give prior consent. We rely on legitimate interests (Article 6(1)(f)) to process this data — specifically, the legitimate interest of the App's users and their teams in coordinating legitimate professional outreach (recruiting, sales, partnerships, fundraising) and avoiding duplicate or conflicting contact. We have carried out the balancing test required by Article 6(1)(f); the summary is in the Legitimate-Interests Assessment at the end of this policy. People whose data we hold under this basis have the right to object to the processing (Article 21) and the right to erasure (Article 17). See the Notice for people whose data we hold.

3.3 — Feature-specific transparency for users. Because the App's core feature is team-visible outreach and profile-visit tracking, every user must actively accept these terms before the App stores any outreach or profile-visit data. This means: when you use the Chrome extension on a LinkedIn profile page, the App writes a row to your team's shared database recording that you visited that profile, along with the profile's public identifier, its display name, and the time. Your teammates can see these rows for the whole team. This is by design and is the core reason the App exists. If you are not comfortable with this, do not sign up.

4. Information We Collect

Account data. When you sign in via LinkedIn OpenID Connect we receive your name, email address, and LinkedIn profile identifier. When you sign in with email and password, we store that email and a hashed password (via our authentication provider, Supabase). You may optionally upload a profile avatar.

Content you create. Comments you write on profiles, emails and phone numbers you add for a profile, outreach entries (profile identifier, channel, date, note, who logged it), profile markings — your team's own tags — pipeline lists and the stage each person sits in, and teams you create or join. When you tag a teammate by name in a comment or an outreach note, we store that mention: who was tagged, by whom, on which profile, and an excerpt of the text, so it can appear in their notifications.

Integration credentials. Stored encrypted in Supabase Vault and visible to the App only through server-side functions scoped to your team:

• HubSpot — a Private App access token you generate, with read scopes for contacts and deals.
• Luma — an API key and, optionally, an iCal subscription URL.
• Google Sheets — the Google Picker and Sheets APIs with the drive.file scope, which only grants access to the specific file you pick. Enabling background sync grants offline access once and stores a refresh token in Vault; without it, nothing long-lived is kept.
• Microsoft Excel — a refresh token for your Microsoft account, stored in Vault, used to read the workbooks you pick from OneDrive or SharePoint.
• Attio — an access token you generate in your Attio workspace. The App only reads from Attio and never writes to it.

Data synced via integrations. Only information already visible inside the connected account. Specifically: HubSpot contacts and deal-stage labels; Luma events and attendee lists (from the API or from CSV exports you upload); rows from the single Google Sheets tab or Excel worksheet you pick, plus the headers and an optional custom icon you upload for the connector; and people and their details from your Attio workspace. Some of these sources carry phone numbers, which are stored and shown on the profile alongside emails.

Profile photos. When a teammate opens someone's LinkedIn profile with the extension, the App records the photo's URL so the person is recognisable in the App. Those URLs expire, so we copy the image into our own storage on the same EU infrastructure and serve it from there. It is deleted along with the rest of a profile's data when the profile is deleted or the team is removed.

We do not read, store, or access your LinkedIn messages, your connections list, your newsfeed, or any LinkedIn content beyond the public profile identifier of people you manually log.

Diagnostic data. When the App's website or extension throws an unhandled exception in your browser, we capture the error message, JavaScript stack trace, the page URL where it happened, and your browser user-agent string, and store them so we can debug. The capture is tied to your account so we can find it; it is not used for analytics, profiling, or anything other than debugging. You can delete this data at any time along with the rest of your account (Section 8). No diagnostic data is captured before you sign in.

5. How We Use Your Information

Your data is used only to (a) authenticate you and maintain your session, (b) show outreach history, notes, emails, and integration data to you and your teammates on matching LinkedIn profiles and in the team dashboard, and (c) enable you to export, edit, or delete your data. We do not use your data for advertising, profiling, automated decision-making, model training, or any purpose other than the features described.

6. Data Sharing & International Transfers

We do not sell, rent, or share your personal data with third parties. Data is processed on our behalf by Supabase (database, storage, and authentication) on their EU-region infrastructure. Data you bring in via an integration is fetched directly from the third-party service (HubSpot, Luma, Google) to your browser, and then stored in our database on the same EU infrastructure. We disclose data only where strictly required by law.

6.1 — Data stays inside the team that already had it. The whole point of the App is to surface what your team already knows, not to widen that circle. Every record in the App — outreaches, notes, emails, profile visits, and every row synced from a connected HubSpot, Luma, or Google Sheets account — is scoped to a single team and visible only to members of that team. Row-level-security policies in our database enforce this, not just application code. If you connect your company's HubSpot to a team, the contacts from that HubSpot stay inside that team: we do not copy them to any other team, we do not build a cross-team contact graph, and we do not expose a contact's data to any user who was not already a member of the team you brought it into. If you or a teammate joins a second team, the records from the first team do not follow; each team's database is walled off from the others.

6.2 — You only see what the team already has on the person. When the extension lights up on a LinkedIn profile, everything it shows you — the outreach history, the notes, the HubSpot contact card, the Luma check-ins, the Google Sheets row — was already in your team's own records before you opened that profile. The App does not enrich profiles with data bought from brokers, scraped from elsewhere on LinkedIn, or fetched from any other team's database. If there is nothing in your team's records for that person, the extension stays empty.

6.3 — You must accept this scope before the App stores anything about anyone. By creating an account and accepting the consent gate that appears on first sign-in, you agree not to use the App to expose records to anyone who is not already a member of the team those records belong to. You agree not to copy data between unrelated teams, not to invite strangers into a team solely to leak its records to them, and not to use the App to enlarge the circle of people who can see a given data subject's information beyond what was already the case before the App was involved.

6.4 — Reporting misuse; enforcement. If you see someone using Orwell's bad dream to widen the circle beyond the team that already held the data — e.g. moving contacts between unrelated teams, creating a team for the sole purpose of exposing data to outsiders, or otherwise circumventing the team-scoping described above — please report it to martinvfalck@gmail.com with as much detail as you can share. We will investigate every report. Teams found to be misusing the App in this way will have their data deleted and their members banned from the App; individual users who organise such misuse will be banned as well. Enforcement is at our sole discretion and does not create any liability to the banned parties.

7. Data Retention

We retain your data while your account is active. When you disconnect an integration, the stored credentials and synced data for that integration are deleted immediately. When you leave a team or an admin removes you from it, what you logged stays with the team and remains attributed to you — it is the team's record of who it has spoken to, and losing it because someone changed jobs would destroy the thing the App exists to keep. A team admin can delete a member's contributions at any time, either when removing them or afterwards, and will do so on request. Profile view history is collapsed nightly: we keep the most recent view of each person by each teammate and delete the repeat visits behind it. When you delete your account (Account Settings → Delete account), all remaining personal data is permanently erased within 30 days, in every team you belonged to. We do not keep backups of deleted accounts.

8. Your Rights Under GDPR

Under the General Data Protection Regulation, you have the right to:

• Access all personal data we hold about you (Article 15)
• Rectify any inaccurate or incomplete data (Article 16)
• Erase your data and account entirely — "right to be forgotten" (Article 17)
• Restrict processing of your data (Article 18)
• Receive your data in a portable, machine-readable format (Article 20)
• Object to processing at any time (Article 21)
• Withdraw consent at any time, without affecting the lawfulness of processing carried out before withdrawal (Article 7(3))

Send requests to martinvfalck@gmail.com; we will respond within 30 days. If you believe your data-protection rights have been violated, you can lodge a complaint with your local supervisory authority. In Denmark, this is Datatilsynet (datatilsynet.dk).

9. Cookies & Tracking

The App uses only strictly necessary cookies and browser storage for authentication and session management. We do not use tracking, analytics, or advertising cookies.

10. Third-Party Services

Authentication. You can sign in with LinkedIn OpenID Connect or with email and password. LinkedIn processes your data under its own privacy policy (linkedin.com/legal/privacy-policy). Both methods are handled via Supabase Auth.

Infrastructure. Supabase (supabase.com) hosts our database, storage, and secrets vault in the EU. See Supabase's Data Processing Agreement for details.

Email summarisation. Anthropic (anthropic.com) processes the text of an email at the moment you press “Track”, to produce the three-bullet summary offered as your note. The text is sent for that single request and is not retained by us or used by Anthropic to train models. If you never press Track, no email text is ever sent. This is the only sub-processor that sees message content, and it sees only messages you explicitly choose to track.

Optional integrations. Only active if you connect them:

• HubSpot (hubspot.com) — connected via a Private App token you generate. We read contacts and deal-stage data your HubSpot account has access to.
• Luma (lu.ma) — connected via an API key you generate, plus an optional iCal subscription URL for co-hosted events. We read events and attendee lists visible to that Luma account.
• Google (google.com) — for the Google Sheets connector, the Picker and Sheets APIs are used with the drive.file scope. Google sees only the file you explicitly pick. A refresh token is stored only if you enable background syncing.
• Microsoft (microsoft.com) — for the Excel connector. We read the workbooks you pick from OneDrive or SharePoint and nothing else in your account.
• Attio (attio.com) — connected via an access token you generate. We read people and their details from your workspace, and never write to it.

Payments. Paid teams are billed through Stripe (stripe.com), which handles the payment itself: card details go to Stripe and never reach us. We store the identifiers Stripe gives us for your team's customer and subscription, the plan status, and how many seats the team is using.

AI assistants. The App exposes an optional read-only MCP server, so you can ask an assistant such as Claude questions about your own team's records. It runs every query as you, under the same row-level-security rules as the App, so it can never read a team you are not in. It is only reachable if you connect a client to it, and it cannot write anything.

The Chrome extension runs on linkedin.com/in/* profile pages and, for email tracking, on Gmail and Outlook Web. On LinkedIn it reads the profile identifier in the URL, plus the displayed name and profile photo, so it can look up and show your team's records for that person. It does not read your LinkedIn messages, your connections, or your newsfeed.

Email tracking. In Gmail and Outlook the extension adds a “Track” button next to Send. Until you press it, the extension reads nothing from your mailbox and sends nothing anywhere. When you do press it, and only for that one message, the extension reads the recipient address, the subject and the body of the email you are writing, and sends them to our server, which passes them to Anthropic’s Claude API to produce a three-bullet summary suggested as your outreach note. The email body is never stored — not by us and not by Anthropic for training; it is summarised in transit and discarded. Only the three bullets are saved, and only if you send the email. The extension never reads your inbox, other messages, drafts you have not tracked, or any email you receive.

11. Security

We use encrypted transport (TLS), encrypted storage at rest, Supabase Vault for integration secrets, and row-level-security policies so each team's data is only accessible to that team's members. Access is limited to the minimum necessary. While no system is completely secure, we take reasonable technical and organisational measures to safeguard your personal data in accordance with GDPR Article 32.

12. Children

The App is not directed at anyone under the age of 16. We do not knowingly collect personal data from children. If we become aware that a child's data has been collected, we will delete it immediately.

13. Changes to This Policy

We may update this Privacy Policy from time to time. If we make material changes, we will notify you through the App before they take effect. The "Effective Date" at the top will always reflect the latest revision. Continued use after changes take effect constitutes acceptance of the revised policy.

Appendix A — Legitimate-Interests Assessment

Summary balancing test for processing third-party personal data under Article 6(1)(f). Fuller documentation is held on record and is available on request.

Purpose test — is the interest legitimate?

The App exists so that a small team doing legitimate professional outreach (recruitment, sales, partnerships, fundraising, investor relations) can coordinate: see who on the team has already contacted a given person, what was said, which events or deals the person came from, and avoid the embarrassment or harm of duplicate or contradictory contact. Cross-referencing the team's own records against the LinkedIn profile the user is looking at is the single feature users rely on daily. Teams use the App instead of (or alongside) a full CRM precisely because a CRM does not surface "has anyone on my team already talked to this person?" at the exact moment a user is on the profile. That interest is lawful, specific, and articulated.

Necessity test — is processing necessary for that interest?

The processing is limited to what the feature needs: a public LinkedIn identifier, a display name, a timestamp for profile visits, and whatever a teammate chooses to type (outreach notes, emails pasted from conversations, linkages to attendees or contacts the team already holds). We do not read the profile page's content, messages, or connections list, and we do not enrich the profile with data bought from third parties. A less data-hungry alternative (e.g. manually keeping a spreadsheet) is possible but does not deliver the same coordination benefit and, notably, stores comparable data in a less secure environment. Removing the shared record would remove the App's core utility.

Balancing test — do the data subject's rights override the interest?

Factors weighing in favour of processing:

• The categories processed are non-sensitive business-contact data. No special-category data under Article 9; no criminal-convictions data under Article 10.
• The LinkedIn identifier and display name are, by the data subject's own choice, public on LinkedIn; the data subject made them visible in a professional context specifically to be contacted for professional purposes.
• Access is strictly limited — each row is visible only to the members of one team, enforced at the database layer via row-level security, not merely application-level checks.
• No automated decision-making, profiling, scoring, advertising, or model training is performed against the data.
• Data is hosted in the EU on infrastructure subject to GDPR; credentials for integrations are held in an encrypted vault.

Factors weighing against processing:

• The data subject has not been told directly that we hold their data, so there is an information asymmetry mitigated by (i) the public Article 14 notice at orwellsbaddream.com/privacy/profile-data, (ii) a documented and accessible objection and erasure workflow, and (iii) a contact address they can reach directly.
• Profile-visit logging in particular can feel surveillance-like. We limit this by capping it at one view per profile per user per 24 hours, keeping visits visible only inside the one team, and letting the team member delete their own view record at any time.
• If a data subject works in a field where LinkedIn activity is sensitive (e.g. job-seeking in confidence), the logging of visits could prejudice them if the data were leaked. We consider this risk real but low-probability given EU hosting, RLS, and the absence of third-party sharing.

Conclusion. On balance, the legitimate interest of teams in coordinating legitimate professional outreach, combined with the limited scope, non-sensitive categories, EU hosting, strict access controls, and the availability of an unconditional right to object and erase, outweighs the interference with the data subject's rights. Processing is therefore lawful under Article 6(1)(f). A data subject who disagrees with that balance on their own facts can exercise their Article 21 right to object, which we honour without precondition.

Last reviewed: April 22, 2026. This assessment will be re-reviewed whenever a materially new processing activity is introduced.

1. Who holds your data

Orwell's bad dream is the data controller. Contact: martinvfalck@gmail.com. The controller is established in Denmark; the supervisory authority is Datatilsynet (datatilsynet.dk), where you can lodge a complaint at any time.

2. What data may exist

A team using the App may hold some or all of the following about you. We say "may" because the App is team-driven — what is stored depends entirely on what a given team has entered or synced:

• Your public LinkedIn identifier (the slug from linkedin.com/in/<slug>) and your display name as shown on LinkedIn.
• A log of when members of that team opened your LinkedIn profile. At most one row per team member per day, with a timestamp and the team member's name.
• Outreach entries and notes a team member typed about a conversation with you (e.g. "Reached out on LinkedIn Apr 3, replied interested in a chat").
• Email addresses and phone numbers linked to your profile by a team member, either typed manually or mirrored from a third-party source (see next point).
• Your profile photo as it appeared on the LinkedIn page a team member opened. LinkedIn's own image links expire, so a copy is kept on the App's storage in the EU and shown next to your name inside that team.
• Labels the team applies to you — its own tags (each team defines its own), a list it has placed you on, and the stage of that list you sit in. These are the team's opinions about its own process rather than facts about you, but they are personal data because they are attached to you.
• Data from a third-party source the team has connected and where your record appears: a Luma event you attended as a guest of that team's host; a HubSpot contact record the team holds; a row in a Google Sheet or an Excel workbook the team maintains; a person record in the team's Attio workspace. Only the fields of that source are stored, and only for the specific object that matched your LinkedIn profile.
• A record that a team member emailed you, if they chose to track that email: your email address, your display name as it appeared in the message header, the date, and a short note — often a three-bullet summary — of what they wrote to you. If we hold no LinkedIn profile for you, your email address itself is the identifier your record is filed under.
• Mentions between team members that name you. If one member tags another in a comment or a note written on your record, we store who was tagged, by whom, which record it was written on, and an excerpt of that text, so it can be shown to them as a notification.

We do not collect or store: your LinkedIn messages, your connections list, your newsfeed, anything you did not publish on your LinkedIn profile, the contents of any mailbox, or any inference / scoring / profiling about you.

On email specifically: we store only a summary of the outbound message a team member sent to you, and only when they chose to track it. We never receive, read or store email you send, your replies, your inbox, or any message a team member did not explicitly track. The full text of a tracked message is used once, in transit, to generate the summary and is then discarded — it is never stored and never used to train any model.

3. Where your data came from

Depending on the team, your data may have come from: (a) the public LinkedIn profile page a team member opened, (b) a Luma attendee list the team's Luma account has access to because you RSVPed to or attended an event, (c) a HubSpot CRM record the team maintains, (d) a row the team pasted or synced from a Google Sheet, (e) something a team member typed manually, or (f) an email a team member sent you from Gmail or Outlook and chose to track, or (g) a person record in the team's Attio workspace.

4. Why we process it — legal basis

Processing is carried out on the basis of legitimate interests (GDPR Article 6(1)(f)) — specifically, the interest of the App's users and their teams in coordinating legitimate professional outreach (recruiting, sales, partnerships, fundraising, investor relations). The documented balancing test is included in our main Privacy Policy appendix. We do not use your data for advertising, profiling, automated decision-making, or AI/ML training.

5. Who can see it

Only the members of the single team that entered or synced the data. Teams in the App are isolated at the database layer by row-level security; there is no "cross-team" index and no public directory. We do not sell, rent, or share your data with third parties. The data is stored by Supabase (a data-processing provider) on EU infrastructure under a Data Processing Agreement.

6. How long it is kept

A team's records about you are kept while that team uses the App. A team's data is deleted in the following cases:

• A team admin removes the member who entered it and chooses to delete their data with them. Removal on its own does not: what a member logged stays with the team.
• A team admin disconnects an integration — the data synced via that integration is deleted.
• A team admin deletes the team — all data within it is deleted.
• You exercise your right to erasure (below).

We do not keep backups of deleted records.

7. Your rights and how to exercise them

Under GDPR you have the right to:

• Access the personal data we hold about you (Article 15).
• Rectify inaccurate data (Article 16).
• Erase your data and ask us not to process it further (Article 17).
• Restrict processing while a request is being resolved (Article 18).
• Object to processing based on legitimate interests — at any time, without justification. When you object, we stop processing unless we can show compelling legitimate grounds that override your rights, which for this App we treat as a high bar (Article 21).

To exercise any of these, email martinvfalck@gmail.com with your LinkedIn profile URL so we can identify your records. We will respond within 30 days. If you are not satisfied with our response you can complain to Datatilsynet (datatilsynet.dk) or the supervisory authority in your EU country of residence.

8. Changes to this notice

If we materially change the way we process third-party data, we will update this notice and log the change. The "Effective Date" above reflects the latest revision.

1. Who These Terms Apply To

These Terms of Use ("Terms") govern your use of the Orwell's bad dream website and Chrome extension (together, "the App"). By creating an account, accepting these Terms in the signup flow, or otherwise using the App, you agree to be bound by them. If you do not agree, do not create an account or use the App.

2. What the App Is For

The App is a lightweight collaboration tool for small teams. It lets you and your teammates keep a shared record of LinkedIn outreach, notes, and contact emails per profile, and surfaces that shared record when any of you visits that profile. You can optionally connect your own HubSpot, Luma, and Google Sheets accounts so matching data from those systems also appears on the profile. The App is intended for legitimate professional outreach (recruiting, sales, partnerships, fundraising) by users who have the right to perform that outreach and to read the data they connect.

3. Limits and What the App Is NOT

The App is intentionally limited in scope. The following are explicitly outside the scope of the App:

• The App does not read, send, scrape, or interact with LinkedIn messages.
• The App does not read or copy your LinkedIn connections list.
• The App does not automate any action on LinkedIn (no auto-connecting, auto-messaging, or similar).
• The App does not bypass LinkedIn rate limits, terms, or technical protections.
• The App does not resell, share, or expose your data to third parties.
• The App does not profile you or run analytics on your behaviour.
• The App does not read your inbox, your received mail, or any draft you have not explicitly chosen to track.
• The App does not send an email for you, or alter one you are writing.
• Your data is not used to train machine-learning models. The one place a model sees your content at all is the optional email summary: when you press “Track”, that single email is sent to Anthropic’s Claude API to draft three bullet points, then discarded. See the Privacy Policy.

Data you log or connect is visible only to you and to the members of teams you join. Nothing is published anywhere else.

4. Your Account and Sign-In

You can create an account by signing in with LinkedIn OpenID Connect, with Google, or with an email and password. Whichever you use, we receive only the identity fields described in the Privacy Policy. You are responsible for keeping your sign-in credentials secure; an attacker who controls your LinkedIn or Google login, or your email inbox, can sign in to the App as you. You may add a password to an account created through a provider; doing so requires a code sent to the address on that account.

5. Acceptable Use

You agree to use the App only for lawful, legitimate professional outreach activities. You agree not to:

• Use the App to harass, stalk, defame, or harm any person.
• Log false outreach data, impersonate someone, or misrepresent who reached out.
• Use the App in violation of LinkedIn's terms of service or applicable law.
• Attempt to access teams, data, or accounts that do not belong to you.
• Reverse-engineer, scrape, or extract data from the App at scale, except for your own data via the in-app export.
• Use an integration to bring in data you are not authorised to access, or whose storage outside of the source system would violate your organisation's policies or the source system's terms.

5b. Billing

A team may be on a free or a paid plan. Paid plans are billed per active member through Stripe, which processes the payment: your card details go to Stripe and never reach us. Adding or removing members changes the seat count, and therefore the amount. If a subscription lapses, the team becomes read-only — nothing is deleted, and it can be written to again once billing is settled.

6. Integrations

The App supports optional, opt-in integrations with HubSpot, Luma, Google Sheets, Microsoft Excel and Attio. When you connect one of these, you confirm that you have the authority to read the data being connected under your organisation's policies and the third party's terms of service. Each integration is connected per team; its data becomes visible to that team's members on matching LinkedIn profiles.

For HubSpot, Luma and Attio, the credentials you paste (Private App token, API key and optional iCal URL, access token) are stored encrypted in Supabase Vault and used only by server-side functions scoped to your team. The same applies to the Microsoft refresh token behind the Excel connector. Every connector reads only: the App writes nothing back into a connected account, Attio included. For Google Sheets, the App uses the Google Picker and Sheets APIs with the drive.file scope, which only grants access to the specific file you pick; no refresh token is stored, and you re-authenticate on each sync.

The App copies the data you pick from each integration into our database so it can be shown on matching LinkedIn profiles. You are responsible for re-syncing when the source data changes. Disconnecting an integration immediately removes the stored credentials and the data synced from that integration.

7. Your Data and GDPR Rights

The App is GDPR-compliant. We process your data only based on the consent you grant when you sign up and when you connect each integration. You may at any time access, correct, export, or permanently delete your data — see Sections 7–8 of the Privacy Policy. The "Delete account" button in Account Settings erases all your personal data and your underlying authentication record.

8. Team Data

When you create or join a team, the outreaches you log, comments you write, contact details you add, markings and lists you create, and integrations you connect become visible to the other members of that team. This is the core function of the App. If you remove yourself from a team, the data you contributed to that team is also deleted. If a team admin removes the team, all member data within it is deleted.

9. Service Availability and Modifications

The App is provided on an "as available" basis. We do not guarantee uninterrupted availability, freedom from bugs, or fitness for a particular purpose. We may modify, suspend, or discontinue parts of the App at any time. If we make material changes that affect your rights, we will notify you in the App before they take effect.

10. Disclaimers and Limitation of Liability

To the maximum extent permitted by law, the App is provided "as is" without warranties of any kind, express or implied. We are not liable for any indirect, incidental, special, or consequential damages arising from your use of the App, including loss of data, loss of business opportunities, or damage caused by reliance on team-logged outreach history or integration data. Our total liability, if any, is limited to the amount you have paid to use the App in the preceding twelve months — which, for the current free tier, is zero.

11. Termination

You may stop using the App at any time and delete your account from Account Settings. We may suspend or terminate your access if you materially violate these Terms or the law, or if your continued use poses a security or integrity risk. On termination for any reason, your data is erased per the Privacy Policy.

12. Governing Law

These Terms are governed by the laws of Denmark, without regard to its conflict-of-law rules. Any dispute will be resolved by the courts of Denmark, except where mandatory consumer-protection rules in your country of residence grant you the right to bring proceedings locally.

13. Contact

For questions about these Terms or to exercise your GDPR rights, contact the data controller at martinvfalck@gmail.com.

14. Changes to These Terms

We may update these Terms from time to time. Material changes will be announced in the App, and the "Effective Date" above will reflect the latest revision. Continued use after changes take effect constitutes acceptance of the revised Terms. If you do not agree, you can delete your account at any time.