Privacy Policy

Gravity is operated by Jonah Greenberger and Jay Zhang(“we”, “us”). This policy covers the Gravity website and application at https://meetgravity.ai. Questions about this policy may be sent to hello@meetgravity.ai or by post at P.O. Box 1723, Wilson, WY 83014, United States.

Gravity is in early access and available by invitation. This policy describes the current Service and will be updated if our data practices change.

Members of a small trusted group each connect their own Gmail account, read-only. Gravity processes selected conversations in which you participated and derives a private record of your correspondents and their apparent areas of knowledge or work. The Rolodex itself is visible only to you, while derived signals from it participate in the group matching described below. When another member states a goal, Gravitymay identify you as someone who could facilitate a relevant introduction and provide a general description of the potential fit. The other member does not receive the contact’s identity. The named proposal is visible automatically only to the member who owns that relationship. Gravity does not contact that person, and an introduction proceeds only if that member approves it.

Account information. When you sign in with Google we receive your name, email address, and profile image from your Google account, and we store an identifier for your account.

Information you give us. The goals you state within a group, the recipient email addresses and notes you provide when sending group invitations, the context you add about how you know a contact, messages you send in shared group chats or an optional move chat, a LinkedIn profile PDF if you choose to import one, and the name, email address, and description you submit if you request an invitation from our homepage.

Google Gmail data. If you connect Gmail, we request exactly one read-only scope, https://www.googleapis.com/auth/gmail.readonly, and use it as described in section 4.

Technical information. We collect ordinary web request information that reaches our hosting provider, such as an IP address, browser user agent, and timestamp. We also maintain operational logs. Our application logs are restricted to a fixed set of non-identifying values, such as a stage name, error class, or provider status code. We do not write mailbox contents, contact addresses, message identifiers, or model output to application logs.

We request one scope, gmail.readonly, and only that scope. If Google grants anything broader, we refuse the connection until you reconnect. Gravity cannot send, modify, delete, or label anything in your mailbox, and has no ability to email your contacts.

We select conversations you have sent messages in, read their headers to determine who you exchange messages with, and process selected message text to build your private Rolodex, derive short paraphrased relationship and capability notes about people you correspond with, and build your private Gmail-derived profile about your own work. These signals may support matching and introduction proposals within groups you join, subject to the visibility and approval controls in section 6.

We do not retain message bodies, subjects, snippets, attachments, raw headers, Gmail-processing prompts, or raw model responses after processing. We retain the connected Gmail address and connection lifecycle metadata; encrypted OAuth credentials while Gmail remains connected; private contact email mappings and Gmail-observed names; interaction counts and dates; derived relationship, capability, and self-profile summaries and claims; selected private Gmail thread identifiers; processing and coverage metadata; and dependent matching records.

This workflow needs to search sent conversations within a date window, identify the participants, read selected message text, and list the account’s send-as aliases so your own addresses can be excluded. The narrower Gmail metadata scope cannot perform all four operations, while adding a Gmail settings scope would introduce write authority over mailbox settings. The read-only scope above is therefore the narrowest scope that supports the feature.

Gravity’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.

We use a large language model to derive relationship and capability information from selected conversations and to respond to optional move chats. Selected message text, profile text, move context, and move-chat messages are submitted through the API of our current model provider, OpenAI, to produce the features described in this policy. OpenAI is also identified in the service-provider table below.

We do not use your Google user data, and we do not permit our providers to use it, to train, develop, or improve generalized artificial intelligence or machine learning models. We use model-provider APIs only to process the data needed to provide the features described in this policy.

Model output is used to produce your own private results and, once you approve an introduction, the material shown to the people in it. It is never used to build a shared contact database, and it is not sold or licensed to anyone.

The following restrictions govern how Gmail-derived information is made available through the Service.

• No member can browse, search, export, or enumerate another member’s relationships. There is no directory and no contact search.
• The list of people derived from your mailbox is visible only to you, in your own account.
• When another member’s stated goal matches someone you know, that member is shown your name as a possible connector, a general professional description, a general statement of how the person might help, and a coarse indication of how strong the fit looks in each direction. They are not shown the contact’s name, contact details, employer, title, location, inferred needs, the reasoning behind the match, source message text, or mailbox evidence.
• The full proposal, including the contact’s identity and the reasons for the match, becomes visible automatically only to you because the relationship came from your Rolodex. The requester continues to see only the anonymous fit brief.
• A shared group chat is visible only to the goal’s requester and the member whose Rolodex supplied the relevant matches. Both members may browse the same anonymized fit briefs there, while only the relationship owner may follow a private link to the named move. Either member may explicitly ask Gravity a question using only the shared goal and conversation; Gravity does not receive contact identity, private move, relationship, or mailbox context and cannot approve or contact anyone.
• An introduction occurs only when you approve that specific introduction. There is no standing consent and no opt-out default.
• Joining a group requires your affirmative action and can be withdrawn. Signing in alone does not add you to a group. You join only by accepting an invitation.

People identified from your mailbox have not signed up for Gravity and do not have accounts. We maintain a limited record associated with your account that may include an email address, a display name, interaction counts and dates, and short derived summaries. Gravity does not contact or market to these people, create public profiles about them, or provide a way for others to look them up. Any introduction is sent by a member who already knows the person, not by Gravity.

If you are not a member and believe Gravity holds information derived about you, write to hello@meetgravity.ai and we will locate and delete it. Because that data lives inside individual members’ private accounts, we may need the email address you would have corresponded from in order to find it.

We do not sell personal information, we do not share it for cross-context behavioral advertising, and we do not run advertising. We disclose information to the service providers below, who process it on our behalf under contract. We may also disclose information where required by law or when necessary to investigate a security incident or suspected abuse.

If Gravity is ever involved in a merger, acquisition, or sale of assets, we will comply with the Google API Services User Data Policy, which requires your prior consent before Google user data is transferred in such a transaction.

A small number of trusted operators can access production systems for a documented, specific support request, to investigate a security incident or suspected abuse, or to comply with law. That access can expose data derived from a member’s mailbox, but our operator tools do not display raw message bodies. We do not read member data for any other reason.

We keep your account, derived relationship data, and stated goals for as long as your account exists. Gmail message text is not stored and exists only for the duration of the request that processes it. Shared group-chat messages are retained with their thread while the associated goal and both participant accounts exist. Retiring the goal makes the thread read-only and archived while both participants remain active group members; leaving the group makes it unavailable, and deleting the goal, group, or either participant account deletes it. An optional move-chat transcript and its snapshotted developer prompt are retained until you start a new chat or the associated move is declined, replaced, or deleted. When move chat changes a private note, its transcript also retains the before-and-after note receipt needed to show and undo that change and to give later chat responses and memory reflection the private product-state history for the same period; forgetting the note from your Rolodex removes those receipts. Google OAuth credentials are stored encrypted and are erased when you disconnect Gmail. We also ask Google to revoke those credentials.

Disconnecting Gmail stops further access but does not delete previously derived relationship data. If you delete your Gmail data as described in section 10, we remove it from our live systems. Our database provider retains backups on a rolling basis, and deleted records are removed as those backups expire.

• Do not connect Gmail. Gmail is optional. You can join a group, state a goal, and receive matches without connecting it.
• Disconnect Gmail at any time from your account, which erases our stored credentials and stops all further reading, or revoke our access directly at your Google Account permissions page.
• Delete Gmail data. From Profile → Sources, choose Delete Gmail datato permanently remove your Gmail connection, private Rolodex, Gmail-derived profile, retained Gmail identifiers and workflow state, and matches sourced from your private Rolodex. Matches sourced from another member’s Rolodex remain. You can use this control whether Gmail is connected or previously disconnected. We attempt to revoke any remaining Google authorization before deleting the live data.
• Deleting Gmail data does not delete messages or settings inside Gmail, your Google account, or your Gravity account. Your Gravity identity, group memberships, goals, and imported LinkedIn profile remain. It removes only data sourced from your Gmail, not another member’s independently sourced data about the same person. Reconnecting Gmail later starts with a new, empty Gmail-derived state.
• Leave a groupto withdraw your data from that group’s matching.
• Delete your Gravity account. Email hello@meetgravity.ai from the address you sign in with. We use that address to verify the request, complete account-deletion requests within 30 days, and confirm by reply. Full-account deletion removes your account and profile, Gmail-derived data, imported profile, memberships, goals, invitations, matches, and proposals. Account deletion does not affect introductions or communications that occurred outside Gravity, and content independently authored by another member remains theirs.
• Remove information about you as a non-member. If you believe Gravity holds a record derived about you inside a member’s private account, email hello@meetgravity.ai with the address you would have corresponded from so we can locate and delete it.
• Access or correct your data. Write to hello@meetgravity.ai. Depending on where you live you may have rights to access, correct, delete, or obtain a copy of your personal information, and to be free from discrimination for exercising them. We honour these requests regardless of where you live, and we do not charge for them. We will ask you to verify control of the account.

Our security measures include encrypted transport; application-layer authenticated encryption of Google OAuth credentials with a key held outside the database; managed database encryption at rest for stored account and derived data; database queries that scope member-owned Gmail-derived records to the applicable member; and operational logs restricted to values that cannot carry user content.

No system can be guaranteed to be completely secure. If you believe you have found a vulnerability, report it to hello@meetgravity.ai. We will acknowledge your report and we will not pursue good-faith security research.

Gravity is not directed to anyone under 18 and we do not knowingly collect their information. We operate in the United States, and information we hold is processed there; if you use Gravity from elsewhere, you are sending your information to the United States.

We will update this policy as the product changes. When a change is material we will update the effective date above and, for changes that affect how we use Google user data, tell members before the change takes effect.