In short
- We do not sell personal information.
- We do not use data from your workspace, or data from your Google or Microsoft accounts, for advertising.
- We do not use your data, or data about your visitors and contacts, to train AI models.
- Keys, passwords and sign-in tokens you connect are stored encrypted.
- getem is offered to businesses in the United States, and stores data in the United States.
Who decides how data is used
For information about you as a getem user (your account, your workspace and how you use getem), Aprative LLC decides how it is used.
For information getem handles for your business about other people, such as visitors to your app's website, people who book a meeting with you, people who sign up for your app and the cold email contacts you import, your business decides how it is used and we process it on your behalf. Your own privacy policy applies to those people. If one of them asks us about their data, we will pass the request to you and help you answer it.
This website
This site sets no cookies of its own, runs no advertising tags and does not record your visits. Vercel, which delivers the pages, receives your IP address and browser details with every request, as every web host does, and keeps short-term logs to run and protect the service.
If you email us, we receive what you send, such as your name, email address and message.
Your getem account
When you create an account at app.getem.now and use getem, we collect:
- Account details: your name, email address and, if you choose, a profile picture. Sign-in is run by Clerk; we never see your password. If you sign in with your Google account through Clerk, Clerk receives your name, email address and profile picture from Google for that purpose only.
- Workspace details: the workspace name, its members and their roles, your working hours and time zone (for booking pages), and your business's name and postal address (getem adds the address to marketing and cold email, as the law requires).
- What you put into getem: your apps' product profiles and interview answers, market test plans, research, articles, emails, booking pages, campaigns, tracked links, settings, spending limits and approval rules.
- Activity: who changed or approved what and when (the audit log), tasks, and the messages you type to getem's message bar with what it changed in reply.
- Notifications: if you turn on phone or browser notifications, the address your browser gives us for delivering them.
- Keys and passwords for services you connect: API keys, app passwords and sign-in tokens. They are encrypted with AES-256-GCM before they are stored and decrypted only when getem calls that service. Your app's secret key is shown to you once and stored only as a one-way hash.
Clerk sets cookies on app.getem.now to keep you signed in. They are needed for the app to work and are not used for advertising.
Data getem handles for your business
Depending on what you set up, getem handles the following for your business:
Visitors to your website and app
When you add getem's tracking to your site or app, getem records a random visitor ID, the pages viewed, the page that sent the visitor, campaign details (utm parameters and campaign code), ad click IDs, browser type and time. It sets the cookies below on your domain. A consent notice asks every visitor before advertising runs, and a Global Privacy Control signal always counts as no. The visitor's IP address is kept with their record only if they accepted advertising cookies, and with signup and purchase events so they can be sent to ad platforms when allowed.
| Cookie | What it holds | Kept for |
|---|---|---|
kit_vid | A random visitor ID, so repeat visits and a later signup can be linked to the first visit. | 400 days |
kit_attr | How the visitor first arrived: campaign details from the link (utm parameters and campaign code), ad click IDs, the first page, the page that sent them, and the time. | 90 days |
kit_click | The most recent ad click ID, if the visitor arrived from an ad. | 90 days |
kit_cid | The campaign code of the link used on this visit. | 12 hours |
kit_consent | The visitor's advertising cookie choice. | 365 days |
People who sign up for your app
Your app tells getem the new user's ID and, if you send it, their email address. getem keeps a one-way (SHA-256) hash of the email with the visitor record. It keeps the email address itself only while your app has onboarding emails running, to send them.
People who use your booking pages
Name, email address, phone number if your page asks for it, answers to your questions, the time chosen and their time zone, and the ad, link or site that brought them. If they tick the box for text reminders, getem stores the exact wording they agreed to and sends reminders through your Twilio account; replying STOP ends them.
Cold email contacts you import
The name, email address, company and other fields you import, where each address came from (required), and the contact's US location. getem checks each address with ZeroBounce through your ZeroBounce account before the first email, records the emails sent and the replies received, and stops emailing anyone who replies, bounces or asks to stop. Contacts outside the United States are refused.
Email delivery reports
Your email delivery provider tells getem when an email bounces, is marked as spam or is unsubscribed from. Each of your apps keeps one do-not-email list, and every marketing email carries a one-click unsubscribe link and your business's postal address.
Search and AI answer data
Search figures from Google Search Console and Bing Webmaster Tools for your domain, and the answers AI assistants give to the buyer questions you set. getem also reads public pages of your website when you run a site check.
How we use information
- To provide getem: run the features you set up, show you counts and reports, and send what you approve.
- To send you service messages, such as sign-in emails, notifications you turn on and notices about your account.
- To keep getem working and secure: getem records each call to an outside service (the result, the error and the address called) with keys, tokens and email addresses removed, to find and fix failures.
- To meet legal obligations and enforce our terms.
We do not sell personal information. We do not use the data in your workspace to advertise getem or anything else, and we do not combine it with data from other workspaces. Each workspace and each app inside it is kept separate in the database.
Ad platforms and conversion events
When your business connects an ad account, getem tells that platform when a visitor who came from an ad becomes a lead, signs up, starts using the app, books a meeting or buys. Platforms getem can send these events to today: Meta (Conversions API), TikTok (Events API), Snap (Conversions API) and Google Analytics 4 (Measurement Protocol).
An event is sent only for a visitor who accepted advertising cookies. It contains an event ID, the ad click ID, a one-way (SHA-256) hash of the email address and phone number if known, and the visitor's IP address and browser type, which the platforms use to match the event to an ad. Without that consent, nothing about the visitor is sent to any ad platform. The events go to your business's own ad accounts, and the platform's own privacy policy covers what it does with them.
Google Ads and LinkedIn are not connected through getem yet. When they are, they will follow the same consent rule, and this policy will describe what getem accesses before that connection is available.
Google user data
getem asks you to sign in with Google only to connect a Google service to your workspace. Each purpose asks only for its own access, at the moment you connect it:
| What getem can access | What getem does with it |
|---|---|
| Your Google account's email address (openid, email) | Shows which Google account is connected and to which person or app in getem it belongs. |
| Free/busy times on your calendar (calendar.freebusy) | Reads when you are busy, without event titles or details, so your booking pages offer only times you are free. |
| Calendar events (calendar.events) | Creates a meeting on your primary calendar when someone books on one of your getem booking pages (with a Google Meet link when the page offers one), and updates or cancels it when they move or cancel. getem does not list or read your other events. |
| Google Search Console (webmasters) | Adds your app's domain as a property, submits its sitemap and reads back the result, and imports search performance for that property each day (search terms, pages, clicks, impressions, average position, country and device). getem shows these figures on the app's Articles tab and uses the search terms to suggest article topics. |
| Site Verification (siteverification) | Gets the DNS record Google asks for to prove you own your domain, and asks Google to check it. |
Gmail
getem does not ask for access to Gmail through Google sign-in. A Google Workspace mailbox you use for cold email connects with an app password you create in your Google account. getem then sends your approved emails through Google's mail server and reads new messages in that mailbox to find replies to them; messages that do not answer one of getem's emails are left alone.
Google Ads
getem does not access Google Ads accounts today. When that connection is added, getem will ask for Google Ads access separately, only to read your campaigns' results and to make the campaign changes you approve in your own Google Ads account, and this section will be updated before that.
How Google user data is stored and shared
- Access tokens and refresh tokens are encrypted (AES-256-GCM) before they are stored, and are used only by the part of getem that calls Google for the purpose you connected.
- We use Google user data only to provide the features listed above to you, in your workspace.
- We do not sell Google user data, and we do not use it or transfer it for advertising, including retargeting or interest-based ads.
- We do not use Google user data to develop, improve or train AI or machine learning models. Search terms from Search Console may be sent to the Claude model through Vercel AI Gateway to suggest article topics for your app; this is a feature you see and control, and the providers do not use the data to train models.
- We transfer Google user data only to the service providers listed below that host and process it for getem, when the law requires it, or as part of a merger or sale of the business with notice to you.
- People at Aprative LLC do not read your Google user data unless you ask us to for support, it is needed to investigate security or abuse, or the law requires it.
How to stop getem's access
Remove getem at myaccount.google.com/connections. getem then marks the connection as needing attention and stops using it. To have the stored tokens and the data getem imported from Google deleted, email tyler@aprative.com from the email address on your getem account; we delete them within 30 days.
getem's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Microsoft accounts
Microsoft sign-in connects a calendar or a cold email mailbox. getem asks for:
- Your account's email and lasting access (openid, email, User.Read, offline_access): to show which account is connected and to keep the connection working without signing in again.
- Calendars.ReadWrite: reads your busy times so booking pages offer only free times, and creates, updates and cancels meetings booked through your getem booking pages, with a Teams link when the page offers one.
- Mail.Send and Mail.ReadWrite, only for mailboxes on your app's separate cold email domains: sends the cold emails and replies you approve, confirms each one is in Sent Items, and reads new inbox messages to find replies, bounces and requests to stop.
The storage, sharing and AI rules in the Google section apply in the same way. Remove getem in your Microsoft account's app permissions (for work or school accounts, at myapps.microsoft.com), or email tyler@aprative.com.
AI processing
getem uses Claude models from Anthropic, reached through Vercel AI Gateway, to draft and check content (product profiles, plans, articles, emails, booking pages, campaign emails and listing copy), to sort replies to cold emails and draft answers, to point out claims during a site check, to compare providers' published API changes with getem's code, and to answer and act on what you type in getem's message bar.
What is sent is the text needed for that task, such as your product profile, the draft, a reply to one of your cold emails or public pages of your site. Keys, passwords and tokens are never sent. Replies that do not answer one of your cold emails are never sent to the AI.
We do not use your data, or data about your visitors and contacts, to train AI models, and the AI providers do not use it to train theirs. The AI never calculates the numbers getem shows you: counts and results come from database queries.
Service providers
These companies process data for getem, only to provide their service to us:
| Provider | What it does for getem |
|---|---|
| Vercel | Hosts the getem app and this website, runs scheduled jobs, and routes AI requests (Vercel AI Gateway). |
| Neon | Postgres database where getem stores workspace data, including encrypted keys and tokens. |
| Clerk | Sign-in, workspaces and members, and the emails Clerk sends to sign you in. |
| Anthropic | Claude models, reached through Vercel AI Gateway, which draft, sort and explain content (see AI processing). |
| OpenAI, Google and Perplexity | Receive only the buyer questions you set for AI answer checks, through Vercel AI Gateway, so getem can record whether their answers name your app. |
| Browser push services (Google, Apple, Mozilla) | Deliver the phone and browser notifications you turn on. They receive the notification text. |
Services you connect
getem also sends data to services your business connects with its own account. Your agreement with each of them covers what they do with it: your email delivery provider (Postmark, Resend, SendGrid, Mailgun, Amazon SES, Brevo, Mailchimp Transactional, SparkPost or an SMTP server), Twilio for text messages, ZeroBounce for address checks, your DNS provider (Vercel, Cloudflare, GoDaddy, Porkbun, Dynadot or DigitalOcean), Vercel for domain purchases and site projects, Google and Microsoft, Bing Webmaster Tools, IndexNow, and the ad platforms in "Ad platforms and conversion events".
How long we keep it
- Your account details: while your account is open.
- Workspace data, including data getem handles for your business: while your workspace is open. When a workspace is closed, or its owner asks, we delete its data within 30 days, except records the law requires us to keep. Database backups that contain it are overwritten on the backup provider's normal schedule.
- Keys and tokens for a connected service: until you disconnect it, or the workspace is closed.
- Emails you send us: as long as needed to answer you and keep a record of the conversation.
Your choices and requests
- To see, correct, export or delete your information, or to close your account and workspace, email tyler@aprative.com from the email address on your account. We confirm the request by email and act on it within 30 days.
- To stop getem's access to a Google or Microsoft account, follow the steps in those sections.
- If you are a visitor, a person who booked a meeting, or a contact of a business that uses getem, ask that business first. You can also email us and we will pass your request to them.
- Every marketing and cold email from getem carries a way to unsubscribe; replying STOP ends text messages.
- A Global Privacy Control signal from your browser turns advertising off on sites that use getem's tracking.
Security
getem encrypts connected keys and tokens, stores secret keys only as hashes, uses HTTPS for every connection, signs unsubscribe, booking and connection links so they cannot be forged, and checks in every database query that data belongs to the workspace and app asking for it. Members see only what their role allows. No system is perfectly secure; if we learn of a breach that affects your data, we will tell you as the law requires.
Where getem operates
getem is offered to businesses in the United States. Data is stored and processed in the United States. Cold email contacts must be in the United States. getem is not offered in the European Union, the European Economic Area, the United Kingdom or Switzerland at this time.
Children
getem is a business tool for people 18 and older. It is not for children under 13, and getem does not support apps directed at children under 13. If you believe a child has given us information, email tyler@aprative.com and we will delete it.
California residents
In the last 12 months we collected, about getem users: identifiers (name, email address, account ID, IP address), commercial information (the apps and settings in your workspace), internet activity (actions in getem), and professional information (your business and role). We collect them for the purposes in "How we use information", from you and from the services you connect.
We do not sell or share personal information for cross-context behavioral advertising, and we do not use or disclose sensitive personal information for any purpose that would give you the right to limit it. For data getem handles for a business, we act as that business's service provider.
You have the right to know what we collected about you, to have it deleted or corrected, and not to be treated differently for using these rights. Email tyler@aprative.com. We will confirm your identity by email before acting. An authorized agent may make a request for you with your signed permission.
Changes
When we change this policy we update the effective date above. If a change affects how we use data you already gave us, we tell account holders by email before it takes effect.
Contact
Aprative LLC, 1674 N 840 W, Salem, UT 84653, US. tyler@aprative.com