Skip to content
OurWay
Back to OurWayContact support ↗

OURWAY / THE DETAILS

Privacy Policy

What you share, where it goes, and the choices you have.

Last updated: 16 September 2026

Who is responsibleInformation we usePhotos, contacts and locationWhy we use informationWho can see informationStorage and retentionDeleting your account and dataYour choices and rightsChildren and sensitive informationThis websiteChanges and contact

The short version

Your event content is shared with its participants. Device permissions are optional and specific to the features you use. Account deletion is available in Settings.

1. Who is responsible

OurWay is operated by Artem Lavrentiev, Ukraine ("we", "us"). This policy describes the OurWay iPhone app, its App Clip and this website. For privacy questions, requests or concerns, email support@our-way.app.

2. Information we use

  • Account and identity: an account identifier and session credentials for guest access; your chosen display name; and, if you choose Sign in with Apple, the identifier and identity information Apple supplies, which may include your name and email or private relay address.
  • Events and participation: event titles, types, dates, start and end times, places, addresses, coordinates, invitation links and their status, guest names, participation and confirmation records.
  • Shared content: chat messages, sender names and timestamps, read positions, uploaded event photos, notes, highlights and expense records such as amounts, currencies, payers and participant shares.
  • Notification settings: an Apple push token, app/device registration information, enabled preferences, language, time zone and 12- or 24-hour format, so reminders and updates reach the appropriate device.
  • Safety and support: reports, the reported message or photo and its author, reasons, review status, blocking relationships, and information you send to support.
  • Product analytics: Firebase Analytics receives app interactions and screen names, such as creating an event, opening a memory, adding content, and using the paywall, together with SDK-generated app-instance identifiers and technical usage information such as app version and device/operating-system information. Our custom analytics events do not include your event titles, names, message text, photos, notes, contact details or precise event coordinates.
  • Subscriptions: RevenueCat receives your OurWay account identifier and purchase information needed to validate transactions, manage trial and subscription status, restore access and analyse subscription performance. This record is linked to your OurWay account, including when you use guest access. Apple handles payment; OurWay does not receive your full payment-card details.
  • Technical information: requests to our hosting and backend services necessarily include information such as IP addresses and request metadata. Service logs and deletion receipts may be used for reliability, security and confirming completed requests.

Profile photos, selected contact details, preferences, cached content and some draft materials are stored on the device. Not every local item is uploaded to our backend.

3. Photos, contacts and location

Photos: the system photo picker gives OurWay access to the images you select, rather than your entire library. Event photos uploaded to an online event become available to its participants. Saving an image to your phone requests permission to add to Photos. A profile image is a separate device-stored setting.

Contacts: you choose contacts through the system picker. Their selected names and contact methods help prepare invitations locally. OurWay does not upload your entire address book. Sharing an invitation through another app is your choice; that app handles delivery under its own terms.

Location: "Use my location" requests device permission when you use it. You can instead search or choose a place manually. A location saved as the event venue, including its coordinates, is shared with participants. OurWay does not provide continuous background tracking of participants.

Notifications: you control permission in iOS and preferences in OurWay. Message alerts may show the event name, author and message text on the lock screen. You can restrict notification previews in iOS. Turning off an optional permission does not automatically delete content you already shared.

4. Why we use information

We use information to create and display your plans, identify participants, provide shared chat and collections, calculate expense splits, deliver requested notifications, restore supported account access, respond to support requests, investigate abuse and maintain the service. We also analyse feature usage to improve the app and process subscription records to provide paid access, restore purchases and understand subscription performance.

Where data-protection law requires a legal basis, essential service processing is based on providing the service you request; optional uses may rely on your consent; security and abuse prevention may rely on legitimate interests, subject to your rights; and some records may be necessary to meet legal obligations. The permissions described in this policy apply to the relevant optional device features. You can withdraw those permissions without affecting earlier lawful processing. Any additional consent required by applicable law is separate from Apple’s ATT permission.

Analytics and advertising choices: Firebase product analytics is enabled automatically in the current full app and does not have an in-app off switch. The app does not pass your OurWay account identifier to Firebase Analytics. Advertising data use and ad personalisation are disabled in the current Firebase configuration; Firebase does not collect IDFA or IDFV in this configuration. The App Clip does not include this Firebase integration.

Advertising measurement with AppsFlyer: The latest full app uses AppsFlyer to measure installations, app opens and fixed in-app actions, such as opening screens, creating an event or completing a purchase flow. AppsFlyer starts only after you authorize Apple’s App Tracking Transparency (ATT) request. It may receive advertising and installation identifiers (including IDFA, IDFV and AppsFlyer ID), IP address and approximate location derived from it, device and app information, timestamps, campaign attribution and the actions you perform. This information is used to measure the effectiveness of advertising for OurWay and may be matched with advertising interaction data. We do not send AppsFlyer your name, email, OurWay account identifier, messages, photos, notes, expense amounts or precise event locations.

If you decline ATT, AppsFlyer is not initialized and no AppsFlyer events are queued; ordinary Firebase product analytics remains enabled as described above. You can revoke tracking permission in iOS Settings under Privacy & Security → Tracking; the app stops AppsFlyer when it next becomes active and checks permission before sending each event. Refusal does not block app features. Google Ads campaign integration is not enabled in the current configuration. The App Clip does not include AppsFlyer. We do not sell personal information or use shared event content to target advertisements. Any separate consent required by applicable law remains separate from ATT.

5. Who can see information

Event participants: an organiser and accepted participants can access shared event details and materials. An invitation link provides access to the invitation flow; treat it as sensitive and share it only with intended guests. A guest session is an account even when no email or password is requested.

Service providers: Supabase provides account, database, file-storage and server-function infrastructure. The currently configured project region is Ireland. Apple provides iOS system services, optional Apple sign-in, App Clip distribution and push delivery. Map searches use Apple mapping services; opening a route in Google Maps passes the selected destination to Google. Google’s Firebase Analytics provides product-usage measurement. RevenueCat provides subscription validation, paywall delivery, entitlement management and subscription analytics. AppsFlyer provides advertising attribution and marketing measurement after tracking permission is granted. Website hosting providers process requests to serve and secure this site. You can read Google’s Privacy Policy and RevenueCat’s Privacy Policy and AppsFlyer’s Services Privacy Policy for information about these providers.

Providers may process technical or support data in other locations under their own arrangements. A project region is not a promise that every service log or provider operation remains in that region. Where required, appropriate legal transfer safeguards must apply to international processing.

We may disclose information where legally required, to protect people or service security, or to a successor operating the service under appropriate privacy protections. We do not describe shared content as end-to-end encrypted: authorised backend operators may access it to operate the service or investigate reports.

6. Storage and retention

OurWay combines device storage with online services. Shared information stays available while the related account or event is retained. Closing an event makes it a read-only memory; it does not automatically delete its content. Uninstalling the app does not by itself delete an online account.

We retain operational and security records only for the purposes they serve, including investigating abuse, completing deletion requests and meeting applicable legal requirements. Relevant criteria include whether an account or event remains active, whether a request or dispute is unresolved, and whether a legal retention duty applies. Service-provider backup and log lifecycles may differ from live application storage.

Other participants can save shared photos to their own devices. We cannot remotely delete copies, screenshots or exports another person has saved outside OurWay. Device caches, personal backups and legacy content not reliably linked to an account may also require separate handling; contact us if identifying information remains after deletion.

7. Deleting your account and data

Use the account-deletion option in Settings and confirm the request. This removes the account and its associated live server data, including events you organise and their shared materials, your messages and participation, push registrations, and content attributed to your account. Deleting an organiser’s event affects its other participants too.

If the account uses Sign in with Apple, you may be asked to authenticate with Apple again so access can be revoked. A failed or interrupted deletion should be retried; do not assume it finished until the app confirms completion. A limited deletion receipt may remain to verify the result and make retries safe. Resetting analytics data on the device does not by itself erase records already held by Google. The current in-app deletion flow does not automatically delete the associated RevenueCat customer record or historical AppsFlyer records. Contact support for requests concerning provider-held records; we will handle applicable deletion rights and explain any records that must be retained. Apple may retain purchase records under its own policies. Account deletion does not cancel an Apple subscription; manage it separately in your Apple Account subscription settings.

You can also request help at support@our-way.app. We may ask for information reasonably necessary to verify that the request concerns your account. Do not send passwords, Apple verification codes or private keys.

8. Your choices and rights

You can edit supported profile and event information, control optional permissions, change notification preferences, save shared photos, block chat participants and request account deletion. Guest access may be lost after removal or a device change unless linked to a supported persistent sign-in.

Depending on the law that applies, you may request access, correction, deletion, restriction, portability or object to certain processing. You may withdraw consent and complain to the relevant data-protection authority. Contact support to exercise applicable rights; requests are subject to identity verification and lawful exceptions.

9. Children and sensitive information

OurWay is not designed as a service directed at young children. Use must comply with the applicable age and consent requirements where you live. If you believe a child provided personal information without the required consent, contact us so we can investigate.

Avoid sharing information you would not want the event’s participants to see. Do not upload other people’s personal or sensitive information without the necessary permission or other lawful basis.

10. This website

Web invitations and chat: a necessary, secure browser-session cookie remembers your guest identity, invitation response and access to the event chat. Shared messages, read positions, reports and blocking use the same event service as the app. Clearing browser data may remove your access to a personal invitation. The website does not cache invitation pages or chat history for offline use.

Optional Android installation and notifications: on supported Android browsers, you can add an OurWay invitation to your home screen or install it as a web app. After accepting an invitation, you can separately choose to allow browser notifications for that event. We store the browser push address, encryption keys and expiration information, linked to your guest identity and the events you have enabled. Our server uses these details to deliver a generic new-message alert through your browser’s push service, such as Google or Mozilla. The alert does not contain the message text, sender’s name or event title; opening it returns to your invitation and chat, where access is checked. Push services process the technical connection and encrypted delivery under their own privacy policies. Installation may be handled by your browser’s installation service.

Browser push retention: active registrations are kept while needed for enabled event notifications. Disabled or expired registrations and event bindings are cleaned up after 30 days; completed delivery records are removed after 7 days, and pending delivery attempts stop after 24 hours. These delivery records do not contain message bodies. Deleting the linked guest account or event also removes associated registrations or bindings.

You can turn off notifications for one event on its invitation page, or revoke permission for the whole site in your browser or Android settings. We check participation, invitation validity and blocking before sending: declining, removal from the event or an expired invitation prevents further alerts for that event. An alert already delivered to your device can remain until dismissed. Browser notification features on this website are offered only on Android and do not change notification settings in the iPhone app or App Clip.

The landing and legal pages do not contain advertising pixels, analytics scripts, account forms or non-essential cookies. Basic delivery, security and access-control logs may still be processed by the hosting service. Following external links or emailing support uses the relevant third-party service.

11. Changes and contact

We will update this page when the service or our practices change and provide additional notice where required. The date above identifies this version. Contact Artem Lavrentiev at support@our-way.app for questions or privacy requests.

OurWay© 2026 Artem Lavrentiev
PrivacyTerms of UseSupport ↗