Privacy Policy
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 NSheridan, 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:
- The Website (relivance.app) — a pre-launch information site that includes an early-access email-capture form. The App is not yet generally available; the Website is informational only.
- The App (Relivance for iOS) — the relationship-intelligence application, currently in private early-access distribution via Apple’s TestFlight platform and (when generally available) the Apple App Store.
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.
- Account & identity data: email address, hashed password (when you sign up with email), full name, organisation, professional title, timezone, and (optionally) a secondary email address. If you choose Sign in with Apple, we receive an Apple-issued identifier and the email and name you authorise Apple to share with us.
- Contacts data: names, email addresses, phone numbers, postal addresses, professional roles, employer history, educational history, social-media handles, profile photographs, custom fields, and free-text notes for individuals you add to or import into your network.
- Interaction data: dates, times, locations, participants, summaries, and free-text notes for meetings, calls, messages, and other shared-time events you log or sync from your Apple Calendar.
- Tasks & commitments: descriptions, due dates, recurrence settings, and participant associations for items you track within the Service. If you enable Apple Reminders sync, we mirror tasks between Relivance and your “Relivance” list in iOS Reminders.
- Goals & strategy data: free-text goal descriptions, milestones, intentions, and any files you attach to a goal (PDF, DOCX, XLSX, CSV, text, or images). Goal attachments auto-expire after 30 days unless promoted into a milestone.
- Voice input you create in the App: optional voice recordings you make inside the App where voice input is available (your own dictation), plus the AI-generated transcripts derived from them. The App does not record meetings, calls, or conversations on your behalf; you record yourself.
- Audio you attach: audio files you voluntarily upload to the App as attachments. You are solely responsible for the lawfulness of any audio you attach, including obtaining any consents legally required from people whose voices appear in that audio under the laws applicable to you and to them.
- Imported third-party data: contact lists from CSV / Excel / vCard files you upload; LinkedIn connection archives that you export from LinkedIn and upload manually (we do not access LinkedIn’s API directly); Apple Contacts (when you authorise import); content from screenshots you submit to OCR.
- Google integration data (only if you explicitly connect a Google account): Gmail thread metadata and message content for sync, Google Calendar events, Google Tasks lists, and OAuth refresh tokens for ongoing access. You may disconnect at any time from the App’s Settings.
- Device permissions you grant (device-side only unless the resulting content is uploaded by you): Apple Contacts framework reads (with your authorisation), EventKit calendar and reminders access, microphone (for voice input where available), camera (for contact avatars), and photo library (for avatars and OCR).
- Subscription & purchase data: Apple StoreKit transaction identifiers, product identifiers, original-transaction IDs, expiry dates, environment (Sandbox/Production), and entitlement status. We do not collect or store payment-card numbers — Apple processes all payments. We also receive Apple App Store Server Notifications about renewals, refunds, and revocations on your subscription.
- Diagnostic data: crash reports, performance metrics, application hangs, and stack traces, collected via Sentry when an error occurs. We have configured Sentry to minimise personal data collection where reasonably practicable, but stack traces, breadcrumbs, and contextual data may contain incidental personal information.
- Derived intelligence: relationship-health scores, behavioural signals, AI-generated briefs, summaries, scores, suggested outreach drafts, and milestone recommendations. These are computed from the items above and stored under your account as decision-support tools surfaced to you. They are not used to make legal or similarly significant automated decisions about you or about the contact subjects of your network, and they may be deleted in accordance with the app’s data controls and the retention schedule in Section 15.
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
- Directly from you: Website email submission, account registration, profile completion, contact entry, file uploads, goal creation, voice recordings, manual notes.
- From your devices, with your permission: Apple Contacts, Apple Calendar, Apple Reminders, microphone, camera, photo library.
- From integrations you authorise: Google (Gmail, Calendar, Tasks via OAuth), Apple StoreKit (subscription state), LinkedIn (only via files you upload yourself — we do not access LinkedIn directly).
- Automatically generated by the Service: timestamps, device-type metadata included in crash reports, and derived-intelligence outputs.
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:
- Performance of a contract (Art. 6(1)(b)): processing necessary to provide the Service you have signed up for — account, contacts, interactions, goals, AI-generated outputs, subscription handling.
- Consent (Art. 6(1)(a)): for the early-access email-capture form, optional integrations (Google), microphone access, camera access, and any feature you must explicitly enable. You may withdraw consent at any time without affecting the lawfulness of prior processing.
- Legitimate interests (Art. 6(1)(f)): for security monitoring, fraud and abuse prevention, debugging via crash reports, and aggregate product analytics — balanced against your rights and freedoms.
- Compliance with legal obligations (Art. 6(1)(c)): retention of certain financial records as required by law.
8. How We Use Your Information
We use the personal information described above strictly for the following purposes:
- Provide the Website and the early-access programme, including sending you launch updates if you submitted your email through the early-access form.
- Provide the core App: authentication, contact management, interaction logging, task tracking, goal planning, and AI-generated relationship intelligence.
- Operate integrations you authorise: sync with Google Calendar, Gmail, and Google Tasks; mirror to Apple Calendar and Apple Reminders.
- Process subscriptions: validate Apple StoreKit transactions against Apple’s pinned root certificates, track entitlement status, and handle renewals, refunds, and revocations via Apple’s App Store Server Notifications.
- Improve the Service: product analytics, debugging, and error correction via crash reports.
- Communicate with you: service notifications (purchase receipts, password resets, security alerts), responses to your support inquiries, and early-access announcements if you opted in via the Website.
- Comply with law: respond to lawful requests from authorities, enforce these terms, and prevent fraud or abuse.
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:
- Supabase (dedicated waitlist project hosted in Central EU / Frankfurt, Germany) — receives early-access submissions through a server-side Edge Function and stores only the submitted email address and signup timestamp in an isolated waitlist table, separate from App accounts and contacts. Processing is governed by the applicable Supabase Data Processing Addendum.
- Cloudflare, Inc. — provides Turnstile security verification for the early-access form. Cloudflare processes technical request and browser/device data to detect automated abuse. We send the verification token to Cloudflare for validation; we do not send the submitted email address to Turnstile. Cloudflare also processes security signals to improve Turnstile, acting as a controller for that purpose. See Cloudflare’s Turnstile Privacy Addendum.
- GitHub, Inc. (a Microsoft subsidiary, United States) — hosts the static Website on GitHub Pages. May keep standard request logs for the files we publish.
App sub-processors:
- Supabase, Inc. (Delaware, United States; Relivance project hosted in Central EU / Frankfurt, Germany) — primary backend infrastructure: PostgreSQL database, authentication, file storage, and Edge Functions. Row-level-security policies isolate each user’s data at the database level. We use the EU-hosted Supabase project for Relivance production app data and rely on applicable data-processing terms, transfer safeguards, and technical measures to support GDPR compliance.
- OpenAI (United States; the OpenAI entity for our account is under verification) — spreadsheet import. When you import a CSV or Excel file and OpenAI is configured on our backend, the App’s import sends the file’s column headings and up to three sample rows to OpenAI to map columns to contact fields. If it is not configured, the import uses built-in rules instead. Sample rows may contain names, email addresses, phone numbers, addresses, and notes, including about people who are not Relivance users. OpenAI’s published terms state that API inputs and outputs are not used for training by default unless the customer opts in, and that abuse-monitoring logs may be kept for up to 30 days, or longer where required by law or to prevent harm. We do not provide your content to OpenAI for advertising.
- Anthropic (the Anthropic entity for our account is under verification) — large-language-model API (Claude) used for conversational assistance, request interpretation, answers using selected saved context, relationship and meeting briefs, outreach drafts, recap processing, contact-information extraction, goal planning and coaching, and screenshot interpretation. Depending on the feature, the information sent may include your messages and conversation history; goals, milestones, and attachments; meeting titles, dates, and participants; the full text of recaps and notes; interaction summaries; tasks; contact names and birthdays; roles, organisations, education, and email domains; relationship context; selected correspondence; and screenshots you submit. Names are generally sent as written. This includes information about people who are not Relivance users. Anthropic’s published commercial terms state that it may not train models on customer content, with exceptions for feedback and programmes a customer joins. Its published default is deletion of API inputs and outputs within 30 days. Published exceptions include content kept to enforce its usage policy (flagged content for up to 2 years, and related safety scores for up to 7 years), feedback (5 years), retention required by law, and separate agreements. Its published commercial terms incorporate its data processing addendum. Our Anthropic organisation’s default retention setting is 30 days, and zero data retention is not enabled at that level. We have not yet confirmed the customer of record for that organisation, or that it is the account our production backend uses. We do not provide your content to Anthropic for advertising.
- Deepgram, Inc. (United States) — speech-to-text API used to transcribe voice recordings where that feature is available. Audio is sent to Deepgram’s US endpoint, and the transcript is returned to the App. Deepgram’s published terms allow it to retain audio and transcripts and use them to improve and train its models unless a request opts out. Since our November 4, 2026 deployment, our transcription requests opt out, and Deepgram’s published documentation states that it then keeps that content only as long as needed to process the request, with request metadata available for 90 days. Before this deployment, our transcription endpoint did not explicitly set the request-level model-improvement opt-out parameter. We have not verified historical requests or account-level opt-out settings. We do not provide your content to Deepgram for advertising.
- Apple Inc. (California, United States) — App Store distribution, StoreKit in-app purchase processing, Apple ID authentication (when you choose Sign in with Apple), App Store Server Notifications for subscription state changes, and EventKit for on-device calendar and reminders.
- Google LLC (California, United States) — only if you explicitly connect a Google account: OAuth 2.0 authentication, Gmail API, Google Calendar API, Google Tasks API. Subject to Google’s privacy policy.
- Functional Software, Inc. (d/b/a Sentry, configured for Relivance in the EU region) — crash reporting and error monitoring. Sentry receives crash reports, stack traces, device-model metadata, and limited contextual data needed to diagnose errors and improve reliability. We configure Sentry to minimise personal data collection where reasonably practicable, and we do not use Sentry data for third-party advertising, cross-app tracking, retargeting, sale of personal data, or data-broker sharing.
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.
- We use Google user data only to provide and improve user-facing features that you enable, such as Gmail, Google Calendar, and Google Tasks functionality inside the App.
- We do not sell Google user data.
- We do not use Google user data for advertising or cross-context behavioural advertising.
- We do not use Google user data to train generalised AI models.
- Human access to Google user data is limited to security, legal compliance, abuse investigation, user-requested support, or where you have given explicit permission.
- You may disconnect Google at any time in the App at Settings → Google → Disconnect, and from your Google account permissions at myaccount.google.com/permissions.
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:
- Early-access email addresses (Website): retained until you ask us to remove them, or until twelve months after Relivance has publicly launched and the early-access list is no longer in active use, whichever comes first.
- Account data (App): for as long as your account is active.
- Contacts, interactions, tasks, goals, voice recordings, and derived intelligence: for as long as your account is active, unless deleted earlier. Deleting an item in the App does not establish that every related record or provider-held copy has been erased. Complete deletion coverage remains under verification.
- Account-deletion grace period: when you request deletion (from Settings → Delete Account in the App, or by emailing privacy@relivance.app), your account is immediately disabled and you are signed out. The account deletion process includes a 30-day grace period. Some user-owned records are not currently covered by automated deletion, so we cannot represent that all personal data is erased when that period ends. Backup retention and provider-held copies are also not yet fully verified; we do not state a maximum period for those copies here. To request erasure or information about remaining data, contact privacy@relivance.app. These implementation limitations do not restrict your statutory rights or extend any applicable deadline for responding to a request.
- Apple subscriptions are managed separately. Deleting your Relivance account does not automatically cancel an Apple subscription, and cancelling an Apple subscription does not automatically delete your Relivance account or your account data. You must manage subscription cancellation through your Apple ID subscription settings (Settings → Apple ID → Subscriptions on your device, or apps.apple.com/account/subscriptions on the web). If you used Sign in with Apple to register, Relivance revokes the associated Sign in with Apple token during account deletion as required by Apple.
- Subscription and transaction records: retained in pseudonymised form for up to seven years to comply with U.S. tax law and Apple’s audit requirements.
- Crash and analytics data: retained for up to 90 days, then aggregated or deleted.
- Logs (web request logs, security logs): we aim to keep these for up to 30 days. Retention of hosting-provider logs remains under verification, and server logs may contain limited incidental personal data.
- AI usage records: records of AI calls (feature, model, token counts, cost, and status, without prompts or responses). We have not yet set a fixed deletion period. After account deletion they are kept without your user identifier.
- Copies held by AI providers: these follow the provider terms summarised in Section 9. We have not verified how those terms apply to our accounts.
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:
- Right to access (“Right to Know”): request a copy of the personal information we hold about you. The App includes an in-app data-export feature (Settings → Your Data → Export My Data) that delivers a ZIP archive containing selected account data in JSON and vCard formats. This export does not currently cover all account data and should not be treated as a complete response to an access request. Contact privacy@relivance.app to request access to information not included in the export.
- Right to rectification: correct inaccurate or incomplete personal data. Most fields are user-editable in the App; for anything you cannot edit, contact privacy@relivance.app.
- Right to erasure (“Right to Delete”): request deletion of your personal data. Use the in-app account-deletion flow or email privacy@relivance.app. To remove your email from the early-access list, email privacy@relivance.app and we will remove it within 30 days.
- Right to data portability: receive your personal data in a structured, commonly used, machine-readable format. The in-app export provides some data in these formats; it does not replace your right to request other personal data covered by applicable law. Contact privacy@relivance.app to make a portability request.
- Right to restrict processing: ask us to limit how we use your data while a question or correction is pending.
- Right to object: object to processing based on our legitimate interests.
- Right to withdraw consent: where processing is based on consent, you may withdraw it at any time without affecting prior lawful processing.
- Right to non-discrimination: we will not discriminate against you for exercising any of these rights — your access to the Service will not be reduced and we will not charge you a different price.
- Right to lodge a complaint: if you are in the EU/EEA/UK and believe our handling of your personal data violates applicable law, you may lodge a complaint with your local supervisory authority. In Germany, this is typically the Bundesbeauftragte für den Datenschutz und die Informationsfreiheit (BfDI) or your state-level Landesdatenschutzbehörde.
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:
- Sale and sharing: We do not sell your personal information for monetary or other valuable consideration. We do not share your personal information for cross-context behavioural advertising. We have not sold or shared your personal information in the preceding 12 months and have no plans to do so.
- Sensitive personal information: certain data we collect — for example, voice recordings, contact records about identified individuals, free-text notes — may constitute “sensitive personal information” under CPRA. We use sensitive personal information only for the purposes for which it was collected (i.e., providing the Service) and will not use or disclose it for any purpose other than as permitted by CPRA §1798.121.
- Authorised agents: you may use an authorised agent to submit a request on your behalf. We require verification of the agent’s authority and your identity before responding.
- Shine the Light Law: California Civil Code §1798.83 permits California residents to request information about disclosures of personal data to third parties for direct-marketing purposes. We do not engage in such disclosures.
18. Data Security & Human Access
We implement administrative, technical, and physical safeguards designed to protect your personal data, including:
- Encryption in transit (TLS 1.2 or higher) for all client–server communication.
- Encryption at rest for our primary database and file storage.
- Row-level-security policies that isolate each user’s data at the database level.
- Apple-hardened cryptographic verification of in-app purchase transactions, validated against Apple’s pinned root certificates.
- Principle of least privilege for personnel access, with access logs reviewed periodically.
- Regular dependency updates and security patching of our infrastructure.
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 LLC30 N Gould St Ste N
Sheridan, WY 82801
USA