Relivance

Privacy Policy

Effective:

Relivance helps users organise professional relationships, contacts, interactions, goals, tasks, and AI-assisted relationship insights. This Privacy Policy explains how Relivance LLC collects, uses, discloses, retains, and protects information in connection with the Relivance iOS application (the “App”), the relivance.app website (the “Website”), and any related services or APIs (collectively, the “Service”).

This Privacy Policy is intended to support compliance with applicable privacy and platform requirements, including requirements that may apply under the EU and UK GDPR, CCPA/CPRA, COPPA, Apple App Store rules, and other applicable laws. Your specific rights may vary depending on where you live.

1. Who We Are

Relivance is a relationship-intelligence platform operated by Relivance LLC, a Wyoming limited liability company (the “Company,” “we,” “us,” “our”).

Principal office: 30 N Gould St Ste N
Sheridan, WY 82801
USA

Registered agent for service of process in Wyoming: Northwest Registered Agent Service, Inc., 30 N Gould St Ste N, Sheridan, WY 82801, USA.

Privacy and data-rights requests: privacy@relivance.app. General questions and user support: hello@relivance.app.

Relivance LLC is the “controller” of your personal data within the meaning of GDPR and the “business” within the meaning of the CCPA/CPRA.

2. Scope of This Policy

This policy applies to all data we process in connection with the Service. The Service currently consists of two distinct surfaces, each with its own data practices:

By submitting your email on the Website, creating an account in the App, or otherwise using the Service, you confirm you have read and understood this policy. If you do not agree, do not use the Service.

3. Eligibility & Children’s Privacy

The Service is intended exclusively for adults aged 18 or older. We do not knowingly collect personal information from anyone under the age of 18.

If we learn that we have inadvertently collected personal data from a person under 18, we will delete that information promptly. To request deletion of a minor’s information, contact privacy@relivance.app.

Relivance is not directed at children, does not feature child-targeted content, and complies with the U.S. Children’s Online Privacy Protection Act (COPPA) and the GDPR provisions governing children’s data.

4. What We Collect on the Website

When you use the early-access form, we store the email address you choose to submit and the date and time of submission in our dedicated EU-hosted waitlist Supabase database. Separately, Cloudflare Turnstile processes technical request and browser/device data to protect the form from automated abuse. The verification token is checked by our server and is not stored in the waitlist. We do not run advertising trackers, cross-site fingerprinting scripts, or analytics scripts on the Website. We do not use cookies on the Website for tracking.

Standard server logs at our hosting provider may briefly record routine request data (IP address, browser type, referring page) for security and abuse prevention. Web font files for the Roboto typeface are served directly from relivance.app, so visiting the Website does not expose your IP address to a font provider. The early-access form loads Cloudflare’s Turnstile script for security verification, as described in Section 9.

The email address you submit is used only for: (a) sending you early-access updates about Relivance, (b) inviting you to use the App when private access opens, and (c) sending launch and service announcements. We do not sell, rent, or trade early-access email addresses, and we do not use them for unrelated marketing.

5. What We Collect in the App

We collect the following categories of personal information in the App. All of these are processed solely to provide and operate the Service for you, never for third-party advertising or cross-context behavioural advertising.

We do not ask for or seek to collect: precise device location, biometric identifiers, browsing history, advertising identifiers, financial-account numbers, government-issued identifiers, health data, or content from any service you have not explicitly connected. Notes, recaps, messages, and other text you write may nevertheless contain health information or other sensitive details about you or other people, and AI features can process that content when they use it.

6. Sources of Information

7. Legal Bases for Processing (EU / UK / EEA Users)

If you are located in the European Union, the European Economic Area, the United Kingdom, or Switzerland, we process your personal data on the following legal bases under GDPR Article 6:

8. How We Use Your Information

We use the personal information described above strictly for the following purposes:

We do not use your information for: targeted advertising, cross-context behavioural advertising, sale to data brokers, or automated decision-making that produces legal or similarly significant effects concerning you. We do not use your personal data to train AI models ourselves. Whether a provider may use submitted data depends on its terms and our configuration, as described in Sections 9 and 10.

9. Third-Party Sub-Processors

We use the following service providers to operate the Service, and we aim to limit what each receives to what its function requires. Published provider terms do not by themselves show how our own accounts are configured. Sections 10 and 13 explain what remains under verification for AI providers.

Website sub-processors:

App sub-processors:

PostHog Cloud EU (PostHog, Inc., hosted in Frankfurt, Germany) — product analytics and app-usage measurement. PostHog may receive user identifiers, device or distinct identifiers, event names, timestamps, screen or feature interaction data, and limited diagnostic context so we can understand feature usage, improve reliability, debug issues, and measure product performance. We do not use PostHog for third-party advertising, cross-app tracking, retargeting, sale of personal data, or data-broker sharing.

We will update this list at least 30 days before adding any new sub-processor that materially affects your personal data.

10. How AI Processing Works

Several App features rely on third-party AI APIs. The provider depends on the feature, as listed in Section 9. Features send the content they need to perform the task — for example, contact context, goal text, interaction summaries, recaps, notes, and uploaded text where applicable. We aim to limit what is sent, but it can be extensive: a Reach Out draft, for example, can use a contact’s saved notes and history.

Depending on the feature, the information sent may include relevant conversation history and selected information already saved in Relivance, rather than only your latest message. For screenshot interpretation, the submitted image is sent to the AI provider for processing. Some processing begins as part of using a feature, such as opening Reach Out, submitting a recap, or importing a spreadsheet; it does not always require a separate request to generate AI content. Some processing runs in the background: creating a goal, or opening People, can send goal text and professional details about contacts for analysis.

Some pathways replace internal record identifiers with temporary labels and limit the records or fields sent. These measures do not make the content anonymous: names, notes, images, or other details may still identify you or another person.

The AI Output we receive back — including briefs, summaries, scores, suggestions, and drafts — is stored under your account so you can review, edit, share, or delete it. AI Output is retained under the same schedule as the underlying content it relates to and may be deleted using the app’s data controls. See Section 15 (Data Retention) for the full schedule.

Published terms and our own accounts. Section 9 summarises what each provider publishes. Those summaries describe provider terms, not verified settings of our accounts. We have not completed verification of the contracting customer for each provider account, which data-processing agreement applies, or the settings that apply to each workspace and request. We do not claim zero data retention or EU-only AI processing. We do not provide your content to AI providers for advertising.

11. Google User Data — Limited Use

If you connect a Google account to the App, Relivance’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.

12. Third-Party Contact Data

When you use the Service to manage your professional network, you will inevitably upload, import, or enter information about other people who are not Relivance users (your contacts). Relivance processes this third-party information to provide the Service to you — for example, to store contact records, surface relationship-health signals, generate AI briefs, or remind you to follow up.

AI-assisted features may send information about your contacts, including people who do not use Relivance, to an AI provider when that information is needed for the feature. This can include information you record about meetings, relationships, and correspondence, as described in Sections 9 and 10.

You are responsible for ensuring you have any required rights, permissions, or lawful basis to provide third-party contact data to Relivance, in particular where privacy laws such as the GDPR apply.

If you believe your information has been uploaded to Relivance by one of our users and you want to request access, correction, or deletion, contact privacy@relivance.app. We may need to verify your request and balance it against the rights and lawful interests of the user who provided the information.

13. International Data Transfers

Relivance LLC is a U.S. company, and some of our sub-processors remain U.S.-based. Our production app database, authentication, and file storage are hosted in Supabase Central EU / Frankfurt, Germany. Even so, personal data is transferred outside the EU. Examples include U.S.-based providers such as Sentry, Apple, Google (if you connect it), and providers supporting our support and legal operations.

AI processing does not stay in the EU. Anthropic’s published documentation states that, unless U.S.-only processing is selected, requests may be processed in any geography where it operates, and its direct API offers no EU-only option. Our requests do not select a region. Our transcription requests use Deepgram’s US endpoint. OpenAI requests, where configured, use OpenAI’s standard endpoint.

The Website’s dedicated waitlist database is hosted in Frankfurt, Germany. Supabase Edge Functions may execute in regions near the visitor, and Cloudflare processes Turnstile security signals through its infrastructure. EU database hosting does not mean all Website processing takes place in the EU. Applicable provider agreements describe the safeguards for international transfers.

Verification of the agreements and transfer arrangements applicable to each provider remains in progress. Anthropic’s published commercial terms incorporate its data processing addendum, including its transfer terms. Because the customer of record and the account used by our production backend are not yet confirmed, we do not state that those terms cover our production traffic. This policy does not confirm that Standard Contractual Clauses (SCCs) have been executed with every non-EU provider. EU hosting of our primary backend does not mean that all processing takes place in the EU.

For information about the transfer arrangements applicable to your personal data, please contact privacy@relivance.app.

Our EU representative for the purposes of GDPR Art. 27 will be appointed prior to broadly admitting EU residents to the App. Until that representative is in place, EU residents may exercise their rights by contacting privacy@relivance.app directly.

14. Business Transfers

We may disclose or transfer personal information in connection with a merger, acquisition, financing, reorganisation, bankruptcy, sale of assets, or similar transaction, subject to appropriate privacy protections or legally required notice. Where the transaction would materially affect how your personal information is processed, we will inform you in advance to the extent required by applicable law.

15. Data Retention

We retain your personal data only as long as necessary for the purposes for which it was collected, with the following per-category schedule:

We may retain personal data longer where required by law, regulation, or to establish, exercise, or defend legal claims.

16. Your Rights

Depending on your jurisdiction, you have some or all of the following rights with respect to your personal data:

We will respond to verifiable rights requests within the timeframes required by applicable law (30 days under GDPR, 45 days under CCPA, extendable once by an additional 45 days where reasonably necessary).

17. California Privacy Rights (CCPA/CPRA)

If you are a California resident, you have the rights described in Section 16. In addition:

18. Data Security & Human Access

We implement administrative, technical, and physical safeguards designed to protect your personal data, including:

Human access. We limit internal access to personal information to personnel and service providers who need access to operate, secure, support, or improve the Service, comply with law, or respond to your requests. We do not routinely review the contents of your contacts, notes, emails, transcripts, or uploaded files.

No system is perfectly secure. We cannot guarantee that unauthorised access will never occur. If we become aware of a security incident affecting your personal data, we will notify you and any required regulators in accordance with applicable law (GDPR Art. 33–34: 72 hours to the lead supervisory authority where feasible; state-level breach-notification statutes in the United States).

19. Cookies & Tracking

The Website does not use cookies for tracking. The App does not use cookies. The App does not perform cross-app or cross-site tracking. We have not enabled Apple’s App Tracking Transparency framework because we do not engage in any tracking that would require it.

Our backend uses session tokens (JWTs issued by Supabase Auth) to maintain your authenticated session in the App. These are not advertising or tracking identifiers.

20. Changes to This Policy

We may update this Privacy Policy as the Service evolves or as required by law. The “Effective” date at the top of this document indicates the date of the most recent revision.

We will provide at least 30 days’ advance notice before any material change takes effect, by email or in-app banner, unless a shorter notice period is required to address a security or legal issue. Your continued use of the Service following the effective date of a revised policy constitutes acceptance.

21. Contact Us

Privacy questions, rights requests, or concerns? Reach us at privacy@relivance.app. For general questions and user support, write to hello@relivance.app.

Principal office: Relivance LLC
30 N Gould St Ste N
Sheridan, WY 82801
USA