Privacy Policy

Account information. If you create an account, we store your email address and authentication details through our authentication provider. You sign in with a Google or Microsoft work account.

Files you upload. Where an upload goes depends on where you add it.

Tools that stay in your browser. On the scan tool and the older lead and intro tools, contact exports (for example LinkedIn connections, contact lists, or event guest lists) are parsed in your browser. These tools never transmit raw uploaded rows to our servers or store them there. Only the people matched to your goal and short summary counts are kept, in your browser’s local storage on your device. When the strategy feature is on, the names, companies, and titles of the people the scan tool matched, plus what you typed, are sent to our servers for that request; raw rows still never leave your browser. One exception: choosing Share private scan on the intro tool or the starter dashboard stores that brief (the names, context, and path it contains) on our servers so that anyone with the link can read it. Older scan pages still reachable by direct link (/founder-scan and /scan/<id>) store a summary of a saved scan, including the matched people, in our database under your account, along with any email address you enter to save it.

Imports into your team workspace. When you are signed in and import an attendee list or a LinkedIn connections export on the Connect page, or ask your own Claude to import people through the Ask Nathan connector, the rows are sent to our servers so Ask Nathan can find your team’s warm paths. For each person, Ask Nathan keeps their name, job title, and company; the company’s domain; the domain of their email address and a hash of the address (used to recognize the same person across sources), not the address itself; the date you connected on LinkedIn, where the export includes it; and, when a row has no email address, the handle from their LinkedIn profile address. The uploaded file itself is not kept; its name and a fingerprint of its contents are recorded on the import record, together with the event name and date you enter for an attendee list. Imported people are stored with your workspace. Other members see the company names. In the app, a person you imported is shown to other members where that person is part of a warm path; a member can also find any imported person by name, title, or company through the ask bar and the Ask Nathan Claude connector. The person who made an import, or a workspace admin, can remove it with Remove this import on the Connect page, which deletes that import’s evidence and any person or company only that import brought in, unless someone on your team has since acted on them (for example, marked them as met, requested an intro, or attached a deal).

Documents you add. On the Connect page you can add product and sales material: PDF, PowerPoint, and Word files, text files, or pasted text. Your team’s owners and admins can also add documents for the whole team and a short “What we sell, and to whom”. Ask Nathan reads the text in your browser and stores the file and its text with your workspace, in our database and file storage. Contact details found in a document (email addresses, phone numbers and personal profile links) are removed from the stored text, and nothing in a document is ever added to your team’s graph as a person or used as evidence about a relationship. A document you add for yourself is used only in your own answers: no teammate or admin can see it. Team documents are used in every member’s answers unless a member turns off “Use team documents”. When you use the Ask Nathan connector in your own Claude, it can return relevant passages from these documents to your Claude, with the names of people in your workspace replaced. When you ask for a line drafted from your documents (for an intro request or “Why this account, why now”), the relevant passages, with contact details and the names of people in your workspace removed, and the account’s name, industry and size when Ask Nathan may share them, can be sent to Anthropic to write the draft; you see and can edit or delete every draft before anything is sent. Ask Nathan never shows this material to another workspace, never uses it to answer anyone else’s questions, and never uses it to train artificial intelligence models. Removing a document stops its use straight away and deletes the file and its text within 24 hours; replacing one deletes the earlier version the same way. If you leave a workspace, the documents you added for yourself there are deleted, and if your workspace closes, everything is deleted 30 days later with the rest of its data. Please don’t add material containing personal information you don’t need, such as customer contact lists.

Events, target lists, and the Network page. Attendee and target lists you add to an event are stored with your workspace, including each person’s name, company, and title (and, when marked, who met them and when), and are visible to your workspace’s members. Company names you save as your team’s target list are stored with your workspace and visible to its members, together with the tier and owner set for each. An ask one member sends another about an account on the list is stored too and shown only to those two members. Company names you check on the target list page without saving them are still sent to our servers to check coverage, and the last list you checked is remembered in your browser. Sharing a list with a partner is not available yet; if your team later shares a list with a partner, that partner will see only the company names on it and nothing else from your workspace. Contact files uploaded on the Network page are stored in your account on our servers, up to 500 rows, including name, email address, company, title, and LinkedIn profile address.

What you type. The goal, target, and any notes you enter are used to produce your recommendation and are stored in your browser's local storage.

Connecting Google Calendar is optional and off until you choose it. For Google Calendar, Ask Nathan requests exactly one scope, https://www.googleapis.com/auth/calendar.readonly, and no other Google scope. Beyond the name, email address, and profile picture that Google sign-in provides, and the Google Sheets access described below if you choose to connect a Google Sheet, Ask Nathan never requests access to Gmail, Drive, or contacts.

What Ask Nathan reads. From your primary calendar, Ask Nathan requests a restricted set of fields: event id, status, start and end times, organizer, attendees, and recurrence information. When your team connects a calendar to a shared workspace, Ask Nathan reads up to 36 months of meeting metadata: the most recent twelve months first, then the older months in stages, a portion with each sync, until all of them are read. After that, each sync refreshes only the most recent twelve months. The direct connection from the Connect page, which keeps its evidence in your browser, reads the previous twelve months only.

What Ask Nathan never reads. Event titles, descriptions, attachments, and conferencing links are excluded by the request itself, so Google never returns them to Ask Nathan.

How it is used. This metadata is used only to show you who you meet with, how often, whether meetings are one-to-one or group, and how recently they occurred, so Ask Nathan can suggest which relationships may open a path to a target account. When you connect Google Calendar directly from the Connect page (the connection this section describes), the resulting relationship evidence is stored in your browser’s local storage, not on our servers. When your team connects a calendar to a shared workspace, the same kind of metadata (who met and when, never titles, descriptions, or contents) is stored on our servers as relationship evidence for that workspace.

Suggesting a colleague. When your own meetings or your company’s CRM show that a colleague attended a meeting with you, or owns a deal, at a company you ask about, Ask Nathan may suggest inviting that colleague. It tells you only that fact, never anything from the colleague’s own sources, and a colleague can ask not to be suggested, through the link in an invite email or by contacting us.

How your tokens are stored. For that direct connection, Google access and refresh tokens are encrypted in a managed secrets vault. They are never written to our database in readable form; the database record holds only references to the encrypted entries and your calendar account email. For a workspace connection, Composio holds the tokens and relays the calendar requests; see “Where your data lives.”

How to remove it. For the direct connection, selecting Disconnect on the Connect page deletes both encrypted tokens, deletes the connection record, clears the calendar-derived evidence from your browser, and asks Google to revoke the grant. For a workspace connection, Disconnect deletes the connection and its tokens at Composio and stops syncing. It also asks Google to revoke Ask Nathan’s access, unless a Google Sheets connection under the same Ask Nathan login is still working or being connected: Google ends all of a Google account’s connections to Ask Nathan when that access is revoked, so Ask Nathan revokes it when you disconnect the last working Google source under your login. Ask Nathan doesn’t know which Google account each connection uses, so two things follow. If your Google sources under one login use different Google accounts, the access of the account you disconnected can stay at Google, with no tokens held by Ask Nathan or Composio. If the same Google account is also connected under another Ask Nathan login, revoking its access can stop that login’s Google source too. If Ask Nathan can’t reach Composio when you disconnect your last Google source, and the connection is replaced or removed before Ask Nathan retries, Ask Nathan deletes it without asking Google to revoke access. You can always remove Ask Nathan in your Google account permissions. If you don’t reconnect Google Calendar within 30 days, Ask Nathan then automatically deletes the meeting evidence that came from your calendar. People and companies that another source, or a teammate’s action such as a verification, an intro request or a logged interaction, also knows stay in your workspace. You can ask for earlier deletion by emailing nathan@asknathan.ai; we act on verified requests within 30 days. Deleted data leaves our backups as they expire on their regular schedule. Revoking access from your Google account permissions also stops syncing, and ends every Ask Nathan connection of that Google account, Google Calendar and Google Sheets alike. On its own it doesn’t always schedule the deletion: if our connection provider then reports the connection as expired, the 30-day rule for broken connections applies (see “How long we keep it”). To be sure the deletion is scheduled, select Disconnect on the Connect page, or email us.

Connecting Google Sheets is optional and off until you choose it. Ask Nathan requests two scopes: https://www.googleapis.com/auth/spreadsheets.readonly, a read-only scope that lets it read spreadsheets your Google account can open (Ask Nathan uses it only for the spreadsheets you connect, as described below), and https://www.googleapis.com/auth/userinfo.email, your Google account’s email address, used only to show which Google account is connected.

What Ask Nathan reads. Ask Nathan reads only the spreadsheets you connect. When you paste a spreadsheet’s address, and again whenever a member reviews its tabs, Ask Nathan reads that spreadsheet’s name, the names of its tabs, and the values in a limited range of each tab (currently the first 50 columns of the first 20 tabs), so it can propose what each tab holds: a pipeline, a list of people, or a list of target accounts. It works this out from the tab’s column headers and the kind of value in each column (for example, whether a column holds email addresses, amounts or dates), by fixed rules, not with an artificial intelligence model. When it can tell, it starts reading the tab and shows you what it chose; when it can’t, it asks you. You can change or skip any tab at any time. A tab added to the spreadsheet later is read only after you ask Ask Nathan to look at it. After that, each time your workspace syncs, including when a member asks for an immediate sync, Ask Nathan reads the spreadsheet’s list of tabs and the values in the same limited range of only the tabs it is reading for you. It reads no spreadsheet or file other than the ones whose address you paste, and it never writes to your sheet. You can connect more than one spreadsheet, with or without a CRM.

What is kept. Ask Nathan keeps only what the mapped columns hold, for the tabs it is reading for you. From a pipeline tab, each row becomes a deal in your workspace: the deal’s name, its ID from your sheet when you map that column, stage, amount and currency, whether it is closed and when, and its owner when the owner’s email address matches a member of your workspace (the address itself is not stored). From a list of people, each row becomes a person in your workspace: their name, title and company and, when you map them, a hash of their email address and the address’s domain (the address itself is not stored) and their LinkedIn profile, used to recognize them. From a list of target accounts, and for each deal, the row’s company is matched to a company in your workspace or added as one, with its website’s domain; a person’s company is matched or added by its name or by the domain of their email address. Ask Nathan records which list each person or company is on, the list’s name and, if you choose one, its purpose (such as fundraising). If you mark a list as people you know, Ask Nathan also records that you know each person on it at that moment, as it does for a LinkedIn export; people added to the list later count as people to reach until you confirm the list again. Otherwise it records no relationship. Ask Nathan also keeps the spreadsheet’s and tabs’ names, the headers and positions of the columns you mapped, and a record of each sync’s counts. The rows themselves and every column you did not map are not stored. While the member who connected the spreadsheet chooses its tabs, the first rows of each tab are shown to them in their browser and are not stored; other members see the column headers only.

How it is used. Deals from your sheets are used, as deals from a CRM are, to show which of your team’s relationships may open a path into the companies you are selling to, and they are visible to the members of your workspace. If your workspace also connects a CRM, deals from both are shown side by side, and Ask Nathan doesn’t merge them. People and companies from your lists are used to show who on your team may know them. A row removed from a pipeline tab closes its deal at the next sync; a person or company removed from a list stays in your workspace and is no longer updated from the sheet. Ask Nathan does not send anything read from Google Sheets, or derived from it, to Anthropic or to any other artificial intelligence provider. If you connect your own Claude to Ask Nathan, your Claude reads Ask Nathan’s answers, which can include your sheets’ deals, people and companies, under your own agreement with Anthropic.

How to remove it. Selecting Disconnect next to a spreadsheet on the Connect page stops syncing it and deletes the connection and its tokens at Composio, unless the same Google connection still reads another spreadsheet in one of your workspaces. Ask Nathan also asks Google to revoke its access, unless a Google Calendar connection under the same Ask Nathan login as the spreadsheet’s connection is still working or being connected: Google ends all of a Google account’s connections to Ask Nathan when that access is revoked, so Ask Nathan revokes it when the last working Google source under that login is disconnected. Ask Nathan doesn’t know which Google account each connection uses, so two things follow. If the Google sources under one login use different Google accounts, the access of the account disconnected can stay at Google, with no tokens held by Ask Nathan or Composio. If the same Google account is also connected under another Ask Nathan login, revoking its access can stop that login’s Google source too. If Ask Nathan can’t reach Composio when the last Google source is disconnected, and the connection is replaced or removed before Ask Nathan retries, Ask Nathan deletes it without asking Google to revoke access. You can always remove Ask Nathan in your Google account permissions. If you don’t connect that spreadsheet again within 30 days, with its pipeline tabs still set to Pipeline, Ask Nathan automatically deletes the deals that came from its pipeline tabs at the end of those 30 days. For a sheet disconnected before this change, the earlier rule applies: connecting another pipeline sheet or uploading a pipeline within those 30 days also keeps its deals. People and companies added from your sheets stay in your workspace’s people and company lists after you disconnect. You can ask for their deletion, for earlier deletion, or for deletion of your whole workspace, by emailing nathan@asknathan.ai; we act on verified requests within 30 days. Deleted data leaves our backups as they expire on their regular schedule. You can also revoke access at any time from your Google account permissions, which ends every Ask Nathan connection of that Google account, Google Calendar and Google Sheets alike.

The Google API Services Limited Use disclosure on this page applies to Google Sheets data.

Connecting Microsoft 365 is optional and off until you choose it. Calendar and email are separate choices: connecting one doesn’t connect the other. For the calendar, Ask Nathan requests the Microsoft Graph permission Calendars.Read; for email, Mail.ReadBasic; with each, offline_access and User.Read, used to keep the connection working and to show which account is connected. Ask Nathan never requests Mail.Read, Mail.Send, or access to shared mailboxes or other people’s mailboxes.

What Ask Nathan reads from email. Mail.ReadBasic would let an app read message headers, including subjects, but not message text or attachments. From each message, Ask Nathan asks Microsoft only for the message’s id, the sender, the To and Cc addresses, the sent and received times, the conversation it belongs to, its folder and whether it is a draft. It never asks for the subject. It reads the last 36 months (12 on Free) when you connect, the most recent mail first and the older months in stages over about a day, then new messages every few hours (weekly on Free), and skips Junk Email, Deleted Items, Drafts and meeting invitations and responses (your calendar already shows those meetings). With User.Read it also reads your own account’s email addresses, so mail to and from your other addresses is never counted as someone else.

What Ask Nathan keeps. For each person at a work email domain with whom you’ve had a back-and-forth by email, or to whom you’ve written directly, Ask Nathan keeps a hash of their email address and its domain (the address itself is not stored), the name shown on their messages, and, for each conversation, how many messages each of you sent, how many times the conversation went back and forth, who started it, its first and last dates, how many people were on it, and Microsoft’s internal identifier for the conversation (never its subject). It keeps nothing about people at personal email domains, automated senders, people at your own company’s domain, people who wrote to you without a reply, or people who were only copied. Members of your workspace see the resulting warm paths and how often and how recently you were in touch, never your messages. Ask Nathan sends nothing derived from your email to Anthropic or any other AI provider. If you or a teammate connect your own Claude to Ask Nathan, that Claude can read how often and how recently you were in touch with someone by email, under your own agreement with Anthropic, never your messages.

How to remove it. Turn email off on the Connect page. Ask Nathan stops reading your mail, deletes the connection and its tokens at Composio, and deletes the email evidence 30 days later unless you reconnect. Your Microsoft 365 calendar keeps working. The permission you granted stays listed for the Ask Nathan app in your Microsoft account until you or your administrator remove it there; removing it ends both the calendar and the email connection. If your administrator approved Ask Nathan for your organization, Microsoft may not show you a permission screen; Ask Nathan’s own screen still asks you first.

Ask Nathan’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, Google user data is used only to provide and improve the features you requested, is never sold, is never transferred to third parties except as necessary to provide those features or as required by law, is never used for advertising, and is never used to develop, improve, or train generalized or non-personalized artificial intelligence or machine-learning models. No human reads your Google user data except with your explicit permission, for security purposes, or where required by law.

Public research is currently switched off: nothing is sent to Anthropic for it.

When public intelligence is enabled, Ask Nathan may search publicly available web sources for context about the people and companies in your recommendation. This feature is powered by Anthropic, accessed through Anthropic's commercial API, which is the only third-party artificial intelligence provider Ask Nathan uses. Only public-safe fields are sent: a person's name, company, and job title, the target account, a public event name, and a topic.

Ask Nathan does not send information received from Google Workspace APIs, including your Google Calendar and Google Sheets data and anything derived from them, to Anthropic or to any other third-party artificial intelligence provider. If you connect your own Claude to Ask Nathan, your Claude reads Ask Nathan’s answers, which can include facts derived from your calendar or your Google Sheets, under your own agreement with Anthropic. More generally, private information is never included in a web search: no calendar metadata, no meeting participants, no uploaded contact rows, no notes, no opportunity names or values, and no message content. This restriction is enforced both in your browser and again on our server, and requests containing unrecognized fields are rejected before any processing.

Ask Nathan records product usage events — for example that a page was viewed or a feature was used — together with a randomly generated session identifier stored in your browser. These events are used to understand how the product is used. They do not contain your uploaded data, calendar metadata, or message content. After you sign in, these events (including use of the Ask Nathan Claude connector) are tied to an opaque account identifier and your work email domain, never your email address or name.

If you type a question in the chat during one of our webinars, it may be answered by the Ask Nathan assistant. The assistant is an AI, not a person, and its first reply in each conversation says so. It answers only from public information about Ask Nathan and our published research, and it cannot see any customer’s data, any workspace, or anyone’s relationships.

Our webinars and their chat are hosted by eWebinar, under its own privacy policy. When you type a question, eWebinar passes your message to Ask Nathan’s servers, with the earlier messages in that conversation when it includes them. Before anything is sent on, Ask Nathan removes the email addresses, telephone numbers, links and names it recognizes. It then sends what is left to Anthropic, our artificial intelligence provider, through Anthropic’s commercial API, to write the answer. Ask Nathan does not send Anthropic your registration details; if eWebinar sends your name with a message, Ask Nathan uses it only to keep your name out of what it sends. No automatic removal is perfect, and a name Ask Nathan doesn’t recognize can remain, so please don’t share sensitive personal information in the chat.

Ask Nathan keeps a copy of the questions it receives and the answers it gives, with the same details removed, for 90 days to improve its answers, and then deletes them. They are stored with a one-way code for the conversation, never eWebinar’s own identifier for it. Ask Nathan never adds them to any customer’s workspace or uses them as relationship evidence.

A member of our team may read your conversation in eWebinar and answer you there, or follow up with you by email. When the assistant can’t answer a question, our team may see it, with the same details removed, so they can follow up.

When you buy an Ask Nathan plan online, Stripe processes the payment and the subscription. Ask Nathan never receives or stores your card number. Ask Nathan gives Stripe your email address and the ids of your workspace and your account, so the purchase can be matched to your workspace; Stripe holds your billing name, email, address, tax ID and payment method. Ask Nathan keeps the Stripe customer and subscription ids, your plan, its status and dates, the number of seats and whether a discount applies, so it can apply the plan to your workspace. Stripe also uses payment information for its own fraud prevention, as an independent controller under Stripe’s privacy policy. Ask Nathan keeps billing records as long as the law requires, generally up to seven years.

If you use Ask Nathan’s browser tools without a team workspace, what it produces for you (your recommendation, matched people, and relationship evidence) is stored in your browser’s local storage on your own device, and clearing your browser storage removes it. If you sign in and use a team workspace, your workspace’s data is stored in our managed cloud infrastructure: the people, companies, and relationship evidence that come from the sources your team connects (HubSpot, Google or Microsoft 365 calendars, and Microsoft 365 email metadata) or imports, the warm paths computed from them, the deals synced from HubSpot (name, stage, amount, and owner) or from a pipeline spreadsheet you upload or connect from Google Sheets, the people and companies from the Google Sheets lists you connect, the questions you type in the ask bar, intro requests, events, and the interactions you log, including any short note. Account records, tokens for the direct Google Calendar connection, usage analytics, and short-lived caches are stored there too.

Your company controls the data your team brings into its workspace, whether from a CRM, a calendar, an import or a Google Sheet, and Ask Nathan processes it on your company’s behalf under its agreement with us. If someone contacts us about information about them held in a workspace, we pass the request to that company and help it respond. Ask Nathan isn’t designed for sensitive personal information; please don’t connect or map data that holds it, such as health details, government ID numbers or financial account numbers.

How long we keep it. When a connected source is disconnected (HubSpot, Salesforce, a Google or Microsoft 365 calendar, Microsoft 365 email, or a pipeline sheet), Ask Nathan deletes the data that came from it 30 days later, unless it is reconnected in that time (for a pipeline sheet, unless another sheet is connected or a pipeline is uploaded). For HubSpot or Salesforce that means the deals, contacts and activity it synced, and company details only the CRM provided, such as industry and size; for a calendar, the meeting evidence from that person’s calendar; for email, the email evidence from that person’s mailbox. A connection that our connection provider reports as expired or failed is treated as disconnected from that day: unless it is reconnected, the data that came from it is deleted 30 days later. If many connections break at once, for example during a provider outage, Ask Nathan may pause these deletions for up to 14 days while members reconnect. Switching to a different CRM or calendar provider doesn’t keep the first one’s data. People and companies that another source or a teammate’s action also knows stay. Every member of the workspace sees the scheduled date on the Connect page. Your company can ask us to delete all of its workspace’s data at any time; we act on verified requests within 30 days.

We use a small number of service providers to operate Ask Nathan: Supabase and Lovable for our managed application, database, and transactional email; Composio, which handles the sign-in, holds the access tokens, and relays requests and responses between Ask Nathan and the services your team connects to a workspace (HubSpot, Salesforce, a calendar, Microsoft 365 email or Google Sheets); it processes that data only to provide the connection; HubSpot, Salesforce and Microsoft, when you choose to connect them; PostHog for the usage analytics described above; Deno Deploy, which relays requests from the Ask Nathan Claude connector to our servers without storing them; Anthropic for short explanations of recommendations and drafts of intro requests, built only from data that did not come from Google or Microsoft, with people’s names withheld; to answer questions typed into our webinar chat, after Ask Nathan removes the details described in “Webinar chat” above; to understand a question typed into Ask Nathan’s Ask bar when it can’t fully read it on its own (the whole question is sent, not only the part it couldn’t read), after Ask Nathan removes email addresses, telephone numbers, links and the names of people in your workspace (a name Ask Nathan doesn’t hold can remain); and to suggest a company’s industry, type, size and region, and to check whether a company or a job title fits what you search for, from the company’s name, website and the job titles of people there and the words you search for, after Ask Nathan removes contact details and the names of people in your workspace (a name Ask Nathan doesn’t hold can remain), only for companies that came from a LinkedIn or event export, a CSV, HubSpot or manual entry, never from Google or Microsoft data; eWebinar, which hosts our webinars and their chat; Stripe, for payments (see “Payments”); and Google, when you choose to connect Google Calendar or Google Sheets. Anthropic is the only artificial intelligence provider in this list, and Ask Nathan does not send it Google Workspace data. We do not sell your personal information.

You can disconnect any connected source at any time from the Connect page; what came from it is deleted 30 days later unless it is reconnected (see “How long we keep it”). You can also clear locally stored data from your browser, remove an import you made with Remove this import, and request deletion of your account and associated server-side records by emailing us. We respond to verified requests within 30 days. We keep your account information while your account is active and delete it when you ask us to, except for records the law requires us to keep (such as billing records; see “Payments”).

Depending on where you live, you may have the right to ask what personal information we hold about you, to receive a copy of it, to correct it, to delete it, and to object to or restrict how we use it. To make a request, email nathan@asknathan.ai. We verify the request, usually by confirming it comes from your account’s email address, and respond within 30 days. You may use an authorized agent, and we may ask the agent for proof of authority. We will not treat you differently for exercising these rights.

For data a company brings into its Ask Nathan workspace, that company decides how it is used, and we pass your request to it and help it respond (see “Where your data lives”).

We do not sell or share personal information, as those terms are defined under California law, and we do not use it for targeted advertising. Ask Nathan does not track you across other websites, so it treats a Do Not Track or Global Privacy Control signal the same as no signal: either way, nothing is sold, shared, or used for advertising.

Ask Nathan, Inc. is based in the United States, and Ask Nathan’s data is processed in the United States and wherever our service providers operate. If you are in the European Economic Area, the United Kingdom, or Switzerland, we process your account information to provide the service you signed up for, and workspace data on behalf of your company; transfers out of your region rely on the safeguards our service providers offer, such as the European Commission’s Standard Contractual Clauses. You may also complain to your local data protection authority.

Data is encrypted in transit between your browser, Ask Nathan, and our service providers. Access to connector tokens is limited to the server components that need it, tokens are encrypted at rest, and database access is restricted per workspace so that one workspace cannot read another workspace’s records; within a workspace, members share what this policy describes above. No system is perfectly secure, and we encourage you to report any concern to the contact below. If we learn of a security incident that affects your personal information, we will notify you and the affected companies as the law requires.

Ask Nathan is a business product and is not directed to children under 16. We do not knowingly collect personal information from children under 16; if you believe a child has given us personal information, contact us and we will delete it.

We may update this policy as the product changes, and the “Last updated” date above shows when it last changed. Before a material change takes effect, we will tell account holders by email or in the product. We will not use Google user data in a new way without first updating this policy and asking for your consent.

Nathan Pettyjohn, Founder & CEO
Ask Nathan, Inc.
nathan@asknathan.ai