Privacy Policy

Account information. If you create an account, we store your email address and authentication details through our authentication provider. You may sign in with a password or with Google Sign-In.

Files you upload. Contact exports (for example LinkedIn connections, contact lists, or event guest lists) are parsed in your browser. Raw uploaded rows are never transmitted to or stored on our servers. Only the people matched to your goal and short summary counts are kept, and they are kept in your browser's local storage on your device.

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. Nuraga requests exactly one scope, https://www.googleapis.com/auth/calendar.readonly, and no other Google scope. Nuraga never requests access to Gmail, Drive, contacts, or your Google profile.

What Nuraga reads. From your primary calendar, for the previous twelve months only, Nuraga requests a restricted set of fields: event id, status, start and end times, organizer, attendees, and recurrence information.

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

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 Nuraga can suggest which relationships may open a path to a target account. The resulting relationship evidence is stored in your browser's local storage, not on our servers.

How your tokens are stored. 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.

How to remove it. Selecting Disconnect on the “Your context” page deletes both encrypted tokens, deletes the connection record, clears the calendar-derived evidence from your browser, and asks Google to revoke the grant. You can also revoke access at any time from your Google account permissions.

Nuraga's use and transfer of information received from Google APIs to any other app 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 train generalized artificial intelligence models. No human reads your Google user data except with your explicit permission, for security purposes, or where required by law.

When public intelligence is enabled, Nuraga 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 Nuraga 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.

Information received from Google Workspace APIs, including your Google Calendar data and anything derived from it, is never sent to Anthropic or to any other third-party artificial intelligence provider. 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.

Nuraga 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.

Most of what Nuraga produces for you — your recommendation, matched people, and relationship evidence — is stored in your browser's local storage on your own device. Clearing your browser storage removes it. Account records, connector tokens, usage analytics, and short-lived caches of public research results are stored in our managed cloud infrastructure.

We use a small number of service providers to operate Nuraga: Supabase and Lovable for our managed application, database, and transactional email; Anthropic for the public web research described above; and Google, when you choose to connect Google Calendar. Anthropic is the only artificial intelligence provider in this list, and it never receives Google Workspace data. We do not sell your personal information.

You can disconnect Google Calendar at any time, clear locally stored data from your browser, and request deletion of your account and associated server-side records by emailing us. We will respond to verified requests within a reasonable period.

Access to connector tokens is limited to the server components that need it, tokens are encrypted at rest, and database access is restricted per user so that one account cannot read another account's records. No system is perfectly secure, and we encourage you to report any concern to the contact below.

Nuraga is a business product and is not directed to children under 16.

We may update this policy as the product changes. Material changes will be reflected in the “Last updated” date above.

Nathan Pettyjohn, Founder & CEO
Nuraga, Inc.
nathan@theimmersegroup.com