Privacy Policy

• Your account. Your name, email address and profile photo. If you sign in with Google, Google gives us those three things and nothing else. We don’t ask for your contacts, your calendar or your files.
• Your campaigns. Everything you and your teammates enter: the setup questions, audiences, behaviors, interview notes, edits, comments and feedback. Also any research documents you upload and any spreadsheets you import into Pulse.
• Your organization. Which organization you belong to, your role in it, and the invitations you send, including the email address of each person you invite.
• Field workers in Coach. If your organization invites field workers to Coach, each one gives us their first name, phone number, role and language when they set up the app. As they use it, we also store the questions they ask and the answers Coach gives, what they write in reply to a lesson, which lessons they open and finish, and how long they spend in the app. Each question goes to Anthropic’s Claude model, with the field worker’s role and language and facts about the campaign, and the model writes the answer. The Coach app’s error reports don’t include the field worker’s name or phone number. Your organization should tell each person what Coach collects before inviting them.
• Requests for access. If you ask for an invitation, we keep the name, work email, organization, role, country and campaign description you send us, and what you tell us about how you heard of the Toolkit.
• How you use the Toolkit. We record events such as signing in, creating a campaign, generating or editing a draft, sharing and exporting, with the time and the campaign each one belongs to. These records stay in the Toolkit’s own database. We don’t use an outside analytics service.
• Technical details. When something goes wrong, our error-monitoring service receives the error, your browser and device type, your IP address and the page you were on.

Please don’t enter personal information about individual patients, clients or community members. Planning a campaign doesn’t need it. If a research document includes interviews, take out names and other identifying details before you upload it.

• Run the Toolkit: sign you in, save your work, show it to your teammates and send the emails you’ve asked for.
• Write your drafts. When you generate or regenerate a plan, brief, script, playbook, checklist or measurement section, or ask for a translation, we send the campaign content it needs to Anthropic’s Claude model, which writes the draft. Two smaller AI services help: Voyage AI finds the examples most like your campaign, and Recraft draws the line illustrations in scripts and storyboards.
• Help you when you ask, and find and fix problems.
• Improve the Toolkit, as the next section describes.
• Keep the Toolkit secure and stop misuse.

We don’t sell personal information, share it with advertisers or use it to show you ads.

The Toolkit improves because Upswell staff read what it writes and what people change. Here is how that works.

• Upswell staff can open any campaign in the Toolkit. They do it to help you, to check the quality of the drafts, and to learn from them.
• We keep a copy of every draft the Toolkit writes. When someone edits a draft, staff can compare the edit with the original. An AI model helps them judge whether the change is a general lesson or something that only fits that one campaign.
• Staff can turn a general lesson into a rule or an example that guides future drafts for every organization using the Toolkit, not only yours. A staff member reviews each one before it’s used, and we remove names, organizations and other identifying details from anything that becomes an example.
• Feedback you leave on a draft, such as marking a section as one you loved or one that needs work, can become an example the same way.
• Research documents you upload are handled more strictly. They enter our shared training material only if you tick the box agreeing to it. Even then we keep only general lessons drawn from them, each with the short passage it came from so a reviewer can check it, never the whole document.

None of this trains Anthropic’s models. Under Anthropic’s commercial terms, it doesn’t use content sent through its API to train them.

We use these companies to run the Toolkit. Each receives what its job needs.

• Anthropic provides the AI model that writes drafts and translations and answers field workers’ questions in Coach. It receives the campaign content in each request, and for Coach, the question with the field worker’s role and language.
• Voyage AI helps the Toolkit find examples like your campaign. It receives parts of your campaign, such as your audience description, objective, topic and country, along with the examples and drafts we store.
• Recraft draws the illustrations in scripts and storyboards. It receives a short description of each scene, which our AI model writes from your script, not the script itself.
• Supabase provides our database, file storage and sign-in. It holds everything described above.
• Vercel hosts the Toolkit and runs its scheduled jobs.
• Resend sends our email. It receives each recipient’s address and the message.
• Sentry monitors errors. When something fails, and for a sample of AI requests, it receives technical details, which can include the text sent to the AI model and what came back. Sentry also records a sample of browser sessions (about one in ten, plus every session that hits an error) as replays of clicks and page changes, with the text and images on screen hidden.
• EddyDesk runs the feedback button. When you sign in, the Toolkit registers you with EddyDesk, sending your user ID and email address, so the button knows who is using it. When you send feedback or report a problem, EddyDesk also receives your message, your name, any screenshot you attach, and technical details of the page: recent browser console messages, recent network requests and the pages you visited.
• Google handles Google sign-in. Upswell staff can also import a Google Doc they choose into the Toolkit’s reference library. That access covers only the file they pick, and we don’t keep it after the import. The Toolkit’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
• Ad platforms such as Meta and Google Ads supply Pulse’s campaign figures (impressions, reach, spend and similar totals) for ad accounts Upswell has been given access to. These are totals. They contain nothing about the individual people who saw the ads.

Upswell and these companies are based in the United States. Your information may be processed there or in other countries where they operate.

We may also disclose information when the law requires it, or to protect the safety of the people who use the Toolkit or the public. If Upswell’s work on the Toolkit moves to another organization, your information may move with it, still covered by this policy.

• When you create a share link, anyone who has it can read what it shares, without signing in, until the link expires or you turn it off.
• People who open a share link can leave a note. We keep the note and any name they choose to give.
• Pulse share links record when they’re opened.

We use cookies only to keep you signed in. There are no advertising or cross-site tracking cookies. Your browser also stores a few small preferences, such as whether you’ve seen an introduction, and Sentry and EddyDesk store data in your browser so they can work.

We send email about your work: invitations, comments and mentions, finished drafts and campaign reminders. You can turn off notification email in Settings or with the unsubscribe link in any of them. Sign-in links and invitations always send. We don’t send marketing email from the Toolkit.

• We keep your account and your campaigns for as long as they exist in the Toolkit.
• Campaigns belong to your organization. An organization admin can delete one, and it disappears from the Toolkit straight away. Research files uploaded to it aren’t yet removed automatically, so email info@teamupswell.com and we’ll delete them.
• When an account is deleted, we keep the usage records described above but remove the link to the person.
• Rules and examples drawn from your work, and lessons from research you agreed to share (with their quoted passages), stay in the Toolkit after your account or campaign is deleted.
• We keep requests for access so we can follow up. Ask us and we’ll delete yours.
• Backups, and the records our providers keep, expire on those providers’ own schedules.

Email info@teamupswell.com to see the personal information we hold about you, to correct it, to get a copy of your campaigns, or to have your account deleted. We’ll answer within 30 days, and we’ll delete an account within 30 days of being asked. Deleting your account doesn’t delete your organization’s campaigns, which stay with the organization.

Depending on where you live, your local law may give you further rights, such as the right to object to how we use your information or to complain to a data protection authority. We’ll honor them.

The Toolkit is a work tool for adults. It isn’t meant for anyone under 18, and we don’t knowingly collect information from children.

Connections to the Toolkit are encrypted, and database access rules keep each organization’s campaigns visible only to its members and to Upswell staff. No system is perfectly secure. If we learn of a breach that affects your information, we’ll tell you.

When we change this policy, we’ll update the date at the top. If a change affects how we use information you’ve already given us, we’ll tell you by email or in the Toolkit before it takes effect. Our Terms of Service cover the rest of the agreement between us.