Orren LLC, a Wyoming limited liability company, provides an Instagram sales workspace for businesses and their teams, with Mac and iPhone apps and a website. This policy explains the personal information we collect, how we use and share it, and your choices. Orren is a connected service: workspace information is processed in the cloud and cached on your devices.
Orren on iPhone
The iPhone app connects to Orren’s cloud workspace. It sends account and device identifiers to sign you in, check access, synchronise your workspace and deliver notifications you enable. Messages, attachments, lead details, team activity and actions you submit are processed on Orren’s servers and by the connected service needed to carry them out. The app keeps a local cache and saves sign-in credentials in the device Keychain. It does not use an advertising identifier or track you across other companies’ apps for advertising.
Your choice about AI sharing on iPhone
Before using AI chat or suggested replies on iPhone, you can allow or decline sharing. If you allow it, your prompt and relevant messages, lead details and business context are sent to Google Cloud’s hosted AI services to generate a response. Your choice and the disclosure version are saved with your account. Change it in Profile → AI privacy. Declining blocks new AI requests from the iPhone; it does not turn off business automations or background AI processing previously enabled for your workspace.
Apple and Google sign-in
If you choose Apple or Google sign-in, Orren receives the verified account identifier and the name and email address the provider shares. Apple may provide a private relay email address. These identifiers connect the sign-in method to your Orren account. Apple also handles iPhone app distribution and, when you allow notifications, delivers push notifications through Apple Push Notification service.
Who this policy covers
- Customers. People who install Orren and hold a licence.
- The people in your records. Your leads, clients, and the people who message you on connected platforms. Orren processes their information on your behalf and on your instructions. If you are one of those people and have a question about your data, please contact the Orren customer you dealt with; you can also contact us at privacy@tryorren.com for help with a request.
- Website visitors. Covered in The website below.
Your devices and workspace
The apps keep local records, cached media and preferences so you can use your workspace. Sign-in credentials are protected using the device’s secure credential storage. Synchronisation, messaging, connected services and hosted AI require an internet connection and valid account access.
Workspace owners and authorised teammates can access business information according to their roles and the sharing controls in Orren. Hiding or archiving a conversation changes its visibility or organisation; it does not delete it from Orren or Instagram.
Information we process
- Account and access: your name, email, sign-in provider identifiers, workspace membership, role, subscription status, device identifiers, notification settings and records of agreement acceptance.
- Sales workspace: messages and attachments, comments, available profile information, leads, assignments, stages, notes, follow-ups, business documents, resources, automation settings and activity.
- Connected activity: authorised channel and video information, meetings and invitees, available attendance records, tracked-link activity, and payment, refund and team-earnings information.
- AI requests: your questions, relevant workspace context, generated results, feedback and media you ask Orren to process.
- Website and service activity: bookings, waitlist registrations, referrals, support requests, subscription transactions, selected analytics events and diagnostics, as explained below.
We use this information to provide the features you request, keep teams in sync, administer accounts and subscriptions, communicate with you, understand product performance, and protect the service against errors and abuse.
Service providers and sharing
Orren uses service providers for hosting and storage, AI processing, payment handling, email delivery, analytics and app distribution. Our primary cloud processing and PostHog analytics are in the United States. The provider list identifies these companies and their purposes.
We share information as needed to operate your requested features, with connected platforms you authorise, and with people you choose to invite or message. We may also disclose information when legally required or necessary to investigate fraud, abuse or security incidents. We do not sell personal information or share it for cross-context behavioural advertising. Any transfer in a business reorganisation remains subject to applicable privacy obligations and, for Google user data, Google’s Limited Use requirements.
AI features
Orren uses relevant messages, lead details and business knowledge to prepare answers, reply drafts, summaries and suggestions. Market Intelligence analyses conversations to surface recurring questions, objections and themes, with supporting examples where available. These results can include information about the people in those conversations and are available to authorised workspace users.
Relevant content is processed through Google Cloud Vertex AI, using Google’s Gemini models, embeddings and ranking services to provide these features. This is a hosted cloud API integration, not a connection to a consumer AI chat account. Orren does not use customer content to create, train, fine-tune or improve general-purpose AI or machine-learning models, and does not authorise its AI providers to do so. Google Cloud’s service terms prohibit training on customer data without the customer’s permission or instruction.
Processing can involve temporary service caches and provider security or abuse monitoring. No-training protection does not mean zero data retention. Saved workspace records and generated results follow the retention and deletion practices below.
AI output can be inaccurate or incomplete; review it before relying on it. A draft is not a sent message. Messages are sent when you or an authorised teammate send them, or through automations you configure. Orren can process voice messages and media you provide. When you start call recording on Mac, Orren records microphone and system audio, including other playing apps, and sends the audio to its cloud AI service for transcription. It does not record screen images or video. You must let participants know and obtain any required permissions before recording. Transcripts attach to the selected lead and call and may be used as context for AI replies and follow-ups. Original machine transcription remains available alongside readable formatting. Raw local audio is deleted after successful transcription; pending recordings expire after seven days when Orren is open. Saved transcripts are workspace records covered by the retention and deletion practices below.
Corrections you choose to share
Business Knowledge you review and approve supplies the offers, policies and other business context used for replies and suggestions. Relevant conversations and workspace activity can also inform the feature you request. This is personalisation of your workspace; it is not training a general-purpose model on your content.
Google user data
Google services also operate under the Google Privacy Policy. By using Orren’s YouTube integration, you agree to the YouTube Terms of Service.
If you connect a YouTube channel, Orren requests these permissions to display your channel and manage tracked links in video descriptions:
youtube.readonly: your channel and the videos on it, meaning titles, thumbnails, publication dates and view counts.yt-analytics.readonly: older connections may include this permission. Current channel view counts come from the YouTube Data API; Orren does not currently retrieve YouTube Analytics reports.youtube.force-ssl: update video descriptions when you approve replacing links with Orren tracked links. Google describes this permission broadly; Orren uses it for the description changes you authorize.
If you connect Google Calendar, Orren requests access to read calendars and create or update meetings you ask it to manage. If you also approve Google Meet access, Orren can read conference and participant attendance records to help show who attended a booked call. Records are available only when Google provides them, and an unidentified participant may require manual review.
Orren’s use and transfer of information received from Google APIs, including raw, aggregated, anonymised and derived Google Workspace user data, adheres to the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including their Limited Use requirements.
- It is used to provide connected video, calendar, meeting and attendance features and related attribution in your workspace. Relevant records may supply context for the AI answers and summaries you request. This is inference for your workspace, not model training.
- It is not sold or used for advertising. Service providers process it only as needed to deliver the features you request, consistent with Google’s Limited Use requirements.
- Raw Google data and data derived from it are not used, sold or transferred to create, train, fine-tune or improve foundational or general-purpose AI or machine-learning models. We do not send this data to AI services that train on it.
- Human access is limited to the circumstances Google permits, such as your affirmative agreement to review specific data for support, necessary security investigation, or legal obligations.
- Orren reads channel and video information and can update video descriptions when you authorize tracked-link changes. Orren does not upload or delete videos, or post ratings or comments.
- Connection tokens are stored on your device or Orren’s servers as needed for the integration, including server-side calendar and attendance synchronisation. Synced metadata and meeting records are held with your workspace records.
You can revoke Orren's access at any time at myaccount.google.com/permissions, or by disconnecting inside the app. Revoking prevents further authorised access through that connection. It does not itself delete records already synchronised; see Keeping and deleting.
Platforms you connect
When you connect Instagram or another platform, data moves between Orren and that platform using the access you granted. What each platform does with it is governed by that platform's own terms, not by ours.
Connecting Instagram authorises Orren to read and send messages, read and reply to comments, and read your account and media insights, for the Instagram professional account you connect and no other.
- Connection credentials. Orren retains the access credentials needed to keep your authorised connection working and carry out the actions you request.
- What Instagram sends us. Instagram notifies Orren's servers when someone messages you, comments on your posts, taps a button Orren sent, reacts to a message, or reads one. Those notifications can include the sender’s platform identifier and the message or comment content. Orren stores them with the connected workspace and synchronises them to authorised devices.
- Who the other person is. For someone who messages or comments, Orren may read the public profile Instagram exposes to us (name, username and profile picture) so the conversation is identifiable to you rather than a number.
- Automations. If you build an automation, messages and public comment replies are sent from your account by Orren's servers, in response to the triggers you configure. Nothing is sent that you have not set up. Instagram permits a business to send messages only within a window after the other person last contacted you; Orren enforces that window.
- Disconnecting. Removing Orren in Instagram's Apps and websites settings, or disconnecting inside Orren, ends that access. Orren deletes the stored token. Records already synchronised are removed under Keeping and deleting, and the steps are spelled out in Data Deletion Instructions.
Orren does not publish feed posts or reels to your Instagram account. Replies to messages and comments are separate actions described above.
Calendly
When you connect Calendly, Orren stores the authorised connection on its servers and receives booking and cancellation information, including invitee details, so appointments can be matched to leads and shown in your calendar.
Stripe and FanBasis, as sources of your revenue
Separately from paying for Orren, you may connect your own Stripe or FanBasis account to match payments to leads and view revenue and calculated team earnings. Orren processes the payment information supplied by that authorised connection, such as customer identifiers, email, amounts, dates, fees, refunds and payment status. These integrations report and attribute activity; they do not give Orren permission to charge your customers on your behalf. Calculated commissions are not completed payouts.
Other AI tools you connect to Orren
External AI assistant connections are temporarily unavailable while we review provider data-use terms and isolation of Google data. The hosted connector is disabled, and current Mac releases also disable the optional local connector. If you previously configured an external assistant with an older Mac release, update Orren and remove that connection in the other tool. Orren’s built-in AI features continue to use the cloud services described above.
When someone opens a tracked link
Orren lets a business create a link associated with a recipient. Opening it can record the link, associated lead, time, referring site, browser and device categories, and approximate country, region and city. A shared or forwarded link can attribute another visitor’s activity to the original recipient, so a click does not prove who viewed the destination or that they watched or read it.
Network information, including IP address and browser user-agent, is processed to serve the request, estimate location, recognise automated previews and help distinguish repeat activity. Customer-facing click reports use approximate location and device categories, rather than raw IP addresses. Infrastructure providers may process network information for delivery and security. Approximate geolocation uses DB-IP data; that lookup does not send the visitor’s IP address to DB-IP.
The redirect itself does not require a tracking cookie. The optional website pixel below uses browser storage to connect later activity. Automated preview detection is not perfect.
The optional Orren website pixel
If a customer installs the Orren pixel on their website, it can report page views, referral and campaign information, form submissions and purchase events configured by that customer. It uses browser local storage for a visitor identifier and attribution information. A tracked-link token or matching information, including hashed email or phone values, can associate website activity with a lead. Hashed identifiers can still be personal information. The customer is responsible for the website’s notices, consent and lawful use of this tracking.
Product analytics
New Mac and iPhone builds use PostHog to measure selected actions such as opening a conversation, requesting or confirming a reply, setting a follow-up and using a draft. Opaque member and workspace identifiers connect activity across devices without sending your email address. Events can include your role, plan, app version, timing and a safe success or failure category. They do not contain messages, lead identities, team notes, prompts or generated answers. Product screen recordings are disabled. Contact privacy@tryorren.com to request exclusion from product analytics.
Diagnostics and crash reports
Orren processes operational diagnostics such as app and operating-system versions, device identifiers, usage counters, error information and crash reports to maintain and troubleshoot the service. Support requests include what you write and the attachments you choose to provide, along with relevant diagnostics. Avoid including sensitive information that is not needed to resolve the issue.
Sign-in and subscription
You can sign in using the methods offered in the app, including an email code, Apple or Google. We keep account, subscription and device information to authenticate you, administer team access and enforce your plan’s device and usage limits. Stripe processes subscription payments and supplies billing status and transaction details; Orren does not store your full card number or card security code.
Booking a call with Orren
We collect the contact details, business information, qualification answers and notes you submit, along with your selected time and booking type. We use them to assess fit, prepare for the call, schedule or change it, and send confirmations and reminders. Successful bookings and relevant answers are included in our Google Calendar event and Orren booking records; Google Meet provides the meeting link. Customer setup bookings can also include plan and eligibility information. Our analytics receives booking outcomes, not your answers or meeting notes.
Keeping and deleting
We keep workspace information while needed to provide your account and requested features. Cancellation or a payment failure pauses access as described in the Terms; it does not automatically erase the workspace. Booking, support, analytics and diagnostic records are retained for their operational purposes, with access limited to those purposes.
On iPhone, use Profile → Privacy and account → Delete account, or the deletion option on the access screen. Confirm with a fresh email code. You can also request deletion or an export at privacy@tryorren.com, including without an active subscription. We complete verified account-deletion requests within 30 days and confirm by email. Use Manage subscription to stop renewal while a request is processed; we resolve the account’s subscription before completing deletion.
Deletion covers the account and associated personal information, subject to records we must retain for legal, tax, fraud-prevention, dispute or security purposes. We also retain a minimal email suppression record to honour an unsubscribe request. Backup copies expire through their retention cycle and are not used for normal product access after deletion. Local files and cached information on your own devices require separate removal.
A teammate’s deletion request does not delete the business owner’s workspace or business records the organisation is entitled to keep. Hiding, archiving and disconnecting are not account deletion. Deleting information in Orren does not necessarily delete its original on Instagram, Google or another connected service. See the deletion instructions for these distinctions and requests about individual records.
Your rights
Depending on where you live, you may have the right to access, correct, export, restrict, or delete personal information we hold about you, and to object to certain processing. You can exercise all of them by writing to the address below; we answer within 30 days. We do not sell personal information and do not share it for cross-context behavioural advertising. If you are in the European Economic Area or the United Kingdom, we rely on the contract to provide your account and requested services, legitimate interests for proportionate security and service improvement, legal obligations for required records, and consent where required for optional analytics or communications; our processing of the people in your records is done on your instructions as a processor, subject to any data processing terms agreed with that customer. If you are unsatisfied with our answer, you may complain to your local data protection authority.
Where data travels
Orren's servers are in the United States. If you use Orren from elsewhere, your data is transferred to and processed in the United States. Contact privacy@tryorren.com before using the service for processing that requires a separate data processing agreement or international-transfer safeguards, so the applicable arrangements can be confirmed.
Children
Orren is a business tool and is not directed at anyone under 18. We do not knowingly collect information from children.
Security
We use encrypted connections, cloud storage encryption, account and workspace access controls, and restricted administrative access to help protect information. No service can guarantee absolute security. Keep your devices and sign-in methods secure and invite only people who should access your workspace. See our Security Policy for reporting a concern.
Waitlist and early access
When you join the waitlist, we store your email address, the sign-in method you used, whether that address was verified, the date you joined, the waitlist you selected, and a record of your consent to early-access and launch updates. We use these details to manage the waitlist and contact you about your invitation and important launch updates.
If you continue with Apple or Google, we verify the sign-in response and use the email address the provider shares with us. Apple may share a private relay address instead of your personal address. Signing in for the waitlist does not give Orren access to your mailbox, contacts or connected-platform data. Email-only submissions are stored without provider verification.
Waitlist records are held with our cloud service providers. Cloudflare handles website and signup requests on their way to our services. Social sign-in uses a short-lived, secure cookie to complete authentication; it expires after ten minutes and is cleared after a successful sign-in.
We keep your waitlist record while we manage early access and launch communications, unless you ask us to remove it. To leave the waitlist or request deletion, write to privacy@tryorren.com. Joining the waitlist does not start a product trial, create a paid subscription or charge you.
Email preferences
You can stop Orren marketing emails, including trial tips and waitlist updates, through Email preferences or the unsubscribe link in a marketing email. You do not need to sign in. Opting out of marketing does not cancel your subscription or prevent essential sign-in codes, billing notices and replies to your support requests.
To remember your opt-out, we keep a one-way hash of your normalized email address and the time of the request. If we issue a personal unsubscribe link, we store a hashed random token linked to that preference. We retain this minimal suppression record to avoid sending marketing again, including after an account is deleted or someone submits the waitlist form again. Contact privacy@tryorren.com with questions about this record.
Referral credits
If you open an Orren referral link or enter a code at checkout, we remember that code in your browser for up to 30 days so it can follow you to checkout. You can remove it at checkout. This is separate from optional analytics.
When a referral is applied, we connect the referrer's account to the new subscription and keep records of eligible payments, refunds, credits earned and credits used to administer the program. The referrer sees aggregate counts and their own credit balance, not the referred customer's name, email, card or payment details. Referral billing records are retained as needed to administer credits, resolve disputes and maintain financial records.
The website
We use PostHog, hosted in the United States, to understand website visits, page views, checkout starts, booking and download actions, and the steps of joining our waitlist. Website and waitlist activity are reported separately. We collect selected events, browser and device categories, and recognized referral labels. PostHog uses browser storage for a random analytics identifier. We do not currently enable session recordings, heatmaps or automatic form and click capture.
For visitors identified as being in the United States, analytics can run automatically unless you have opted out or your browser sends a Global Privacy Control signal. Elsewhere, or when the country check fails, analytics stays off until you choose “Accept cookies.” Cloudflare supplies this check; we do not store your IP address or country for the decision. Use “Cookie settings” to change your choice. Refusing analytics does not affect checkout, booking or product access. An explicit preference lasts up to six months.
We do not send names, email addresses, form answers, card details, private link parameters or sign-in tokens to PostHog. Page URLs omit query strings and fragments. IP-based location enrichment is disabled. For permitted sessions, our servers can confirm a new or repeat waitlist signup, trial, booking or first successful subscription payment. Reports can include the plan, billing interval and payment amount, never card details. Temporary checkout attribution expires after 35 days; turning analytics off in the same browser requests suppression of future linked outcomes. Waitlist analytics identifiers are not stored with the subscriber’s email record.
New website analytics is collected in PostHog. Previously collected Google Analytics reports remain historical records. See PostHog’s Privacy Policy.
What we do not do
- We do not sell your data, and we have no advertising business to sell it to.
- We do not use your content to train models.
- We do not store the payment card details you use to buy a licence; Stripe handles those.
- Human access to private records is limited to authorised support, necessary security or abuse investigations, and legal obligations. Google data is also subject to the stricter Limited Use rules above.
Changes
When this policy changes, we update its date and provide notice of material changes through the service or email. During onboarding, we record the account, server timestamp and exact versions of the Terms accepted and Privacy Policy acknowledged. A receipt is also saved on the device. If a new acknowledgement is required, the setup flow asks for it before completion.
Contact
Privacy questions, export requests and deletion requests: privacy@tryorren.com. Orren LLC, a Wyoming limited liability company.
