Privacy Policy
Our Sea is a private app for two people. This page explains exactly what it stores, where, who can see it, and how to get rid of it. Every statement here describes what the software actually does.
The short version
- Only you and the one partner you paired with can see what you create.
- There is no advertising, no data selling, and no tracking across other apps or websites.
- Our Sea never reads your device's location.
- Payments are handled by Apple (App Store) or Google (Google Play). We never see your card details.
- You can export everything, and delete everything, from inside the app.
Who we are
Our Sea is made by Harun Yazgan, İstanbul, Türkiye. For anything on this page, write to support@harunyazgan.com. If you are in the EEA or the UK, Harun Yazgan is the data controller for the information described below. If you are in Türkiye, Harun Yazgan is the veri sorumlusu under KVKK (Law No. 6698); the information notice KVKK Article 10 requires is at KVKK Aydınlatma Metni (in Turkish) and KVKK Information Notice (in English).
What Our Sea is
Our Sea is a shared space for exactly two people who have paired using a one-time invite code. There is no public profile, no feed, no discovery, no friend list, and no way for anyone outside your pair to see anything you make. Each account can belong to one pair at a time, and this is enforced by the database rather than by a setting anyone could get wrong.
What we store
| What | Why | Where |
|---|---|---|
| Email address | To create your account, sign you in, and send a password reset if you ask for one | Database |
| Password | Stored only as a salted one-way hash. We cannot read it, and neither could anyone who obtained the database | Database |
| Apple or Google account identifier | Only if you use Sign in with Apple or Sign in with Google. It is an identifier Apple or Google gives us for you. With Apple it is not your Apple ID or your email unless you chose to share one; with Google it comes with the email address and name on your Google account | Database |
| Display name and a colour | So your partner sees who wrote what. Optional | Database |
| What the two of you make — island names, the free-text place you typed, dates, weather you picked, notes, wishes, decorations, the special days you keep (such as the day you met or a birthday, with a birth year only if you add one), and how often you fed Kraki | This is the app. It is the content you came to keep | Database |
| Photos you attach | To show on your islands | Object storage, under a path private to your pair |
| Subscription state — the product you bought, the store's transaction identifiers, status and renewal date | To know which features to unlock | Database |
| Sign-in tokens and password-reset tokens | To keep you signed in and to make a reset link work once. Both are stored hashed, never in a form that could be replayed | Database |
| Push token and the language of your phone — only if you allow notifications | So we can tell your phone that something new arrived from your partner, in your language. The token is an address Apple or Google issues for this app on this phone; it is stored as issued, because it has to be handed back to them to deliver a notification | Database |
| Crash reports and a few product events, as described below | To find and fix bugs, and to see whether the app's main features are used | Database |
Crash reports and product events
When something goes wrong in the app, it sends a crash report to our own
server: the type of error, a short message and a short excerpt of the stack
trace (the lines of code that were running). It also records a handful of named
events: island_created (with the kind of island),
paywall_shown, partner_joined, kraki_fed,
subscription_synced, and, while one of the guides that walk you
through your first island, the sky or Kraki is on screen,
guide_step_reached, guide_step_completed and
guide_skipped (with the number of the step and which guide it
was). These are linked to your pair, not to
you personally, and they never contain anything you wrote, your email or your
name — the server refuses them if they try to. We use them only to fix bugs and
improve the app, never for advertising or tracking, and they are not sent to
any analytics company. They are deleted after 90 days. When your pair is
deleted, they are unlinked from it and no longer connected to you.
Feedback you send us
If you write to us from Settings › Send feedback, we store the message you typed, the kind you picked (an idea, a bug, a note of love or something else), your app version, phone platform and language, and which account and pair sent it, so that we can read it and reply. A copy is emailed to our support inbox, with your email address as the reply address. Nothing is sent unless you press Send.
What we never collect
- Your location. Our Sea has no maps or geocoding component and never asks the operating system where you are. The place attached to an island is text you typed yourself.
- Advertising identifiers. There is no advertising in Our Sea and no advertising software in it.
- Your contacts, calendar, health data, or browsing history.
- Behavioural tracking. Our Sea does not record which screens you open or how long you spend in them. Beyond the crash reports and named events described above, nothing about how you use the app is recorded.
Permissions the app asks for
Our Sea asks for photo library access only when you choose to attach a photo, and camera access only if you choose to take one instead. iOS ties microphone access to the camera picker because that picker can also record video; Our Sea does not record audio. Declining any of these leaves every other part of the app working.
Notifications
Reminders — for plans coming up, anniversaries of your memories, milestones of your days together, and the Kraki tide — are made on your own phone. Nothing about them reaches us or anyone else.
Notifications about your partner work differently. If you allow notifications, the app gives our server a push token and your phone's language, so that when your partner adds something we can tell your phone it arrived. We send these through Google Firebase Cloud Messaging, which on iPhone passes them on to the Apple Push Notification service. What is sent is the token, a fixed generic phrase such as “A new island in your sea” in your language, and an in-app link that points at the new item by its identifier. It never contains your name, your partner's name, an island's name, a note, a wish or a photo. You can turn them off in Settings › Notifications in the app, or in your phone's settings.
Signing out or deleting your account deletes the push token.
Who can see your content
You and your partner. Nobody else has an account that can read a pair's content, and the server checks on every single request that the person asking belongs to the pair they are asking about, rather than trusting a claim made when they signed in. Photos are reachable only through links that are minted for a member of your pair and expire within the hour.
We do not sell your data, and we do not share it with advertisers, data brokers or analytics companies. The only companies involved are listed below.
We may look at stored data only where it is necessary to investigate a specific technical problem you report, to act on an abuse report, or where the law requires it.
The companies involved
| Who | What they do | What they see |
|---|---|---|
| Cloudflare | Runs the servers, the database and the photo storage | Everything listed above is stored on their infrastructure, on our behalf |
| Apple | Sign in with Apple, payments on iPhone (App Store), and delivering notifications to an iPhone (Apple Push Notification service) | Your Apple account and your payment details. We receive a subscription receipt, never a card number. For notifications, your phone's push token and the generic notification text |
| Sign in with Google, only if you choose it | Your Google account. We receive your Google account identifier, email address and name | |
| Google (Firebase Cloud Messaging) | Delivers notifications about your partner's activity, only if you allow notifications | Your phone's push token, the identifier Firebase uses for this installation of the app, and the generic notification text — never your name, your email or anything you made |
| Google Play | Payments on Android | Your Google account and your payment details. We receive a purchase record, never a card number |
| RevenueCat | Checks subscription purchases with the App Store and Google Play and tells us which are active | Your subscription status and purchase records, keyed by your Our Sea account identifier — not your name, email or content |
| Resend | Sends the password-reset email, and delivers the copy of any feedback you send to our support inbox | For a reset: your email address and the reset code, only when you ask for one. For feedback: the message you wrote, your email address, display name, account and pair identifiers, app version, platform and language |
These are the only companies that receive data from Our Sea. The app contains no advertising software, and its crash reports and product events go only to our own server.
Where your data is
Our Sea runs on Cloudflare's global network, and every company in the table above is based outside Türkiye (in the United States or the EU), so data is stored and processed in countries other than your own, including outside the EEA, the UK and Türkiye.
If you are in the EEA or the UK, these transfers rely on the European Commission's Standard Contractual Clauses included in those companies' data processing terms.
If you are in Türkiye, transfers abroad are governed by KVKK Article 9. The safeguard relied on for them is the standard contract published by the Personal Data Protection Board. As of the date at the top of this page, signing that contract with each of these companies and notifying it to the Kişisel Verileri Koruma Kurumu has not yet been completed; this page will be updated when it has. The European clauses mentioned above are not, on their own, a safeguard under KVKK.
How long we keep it
- Your content stays until you delete it. Deleting an island, a note, a wish, a special day or a photo marks it as deleted so that both phones agree it is gone, and it is never shown again. A deleted photo's file is removed by a nightly clean-up. The marked record itself is kept, hidden, until your shared sea is deleted — when you delete your account, or when you both leave it — and is then erased with everything else.
- Sign-in tokens are deleted once they have been expired for a week, or revoked for a month.
- Password-reset tokens are deleted once used or expired.
- Invite codes stop working after 72 hours, and are deleted a month after that.
- Crash reports and product events are deleted after 90 days.
- Push tokens are deleted when you sign out, when you delete your account, and when Apple or Google report them as no longer valid. A token that has not been used for 90 days is removed by a nightly clean-up. The record of which notifications were queued for you, which holds no text, is deleted after 30 days.
- Feedback messages are deleted from our database when you delete your account. The emailed copy stays in our support inbox; ask us at the address above and we will delete it too.
- Your account, when you delete it, is handled as described below.
Your choices
Export everything
Settings › Export gives you a single file containing your pair's islands, notes, wishes, special days and photo links. It is machine-readable and yours to keep.
Delete your account
Settings › Delete Account, inside the app, with no email to write and nobody to ask. It removes your membership of the pair and erases the personal information on your account — your email, your name, your password and your Apple or Google identifier are all cleared, and your push tokens, notification settings and feedback messages are deleted. Content you and your partner made together is not destroyed by one person leaving, because it belongs to both of you; when the second person deletes their account, the pair and everything in it is deleted too. An active subscription follows the person who bought it.
Correct or ask about your data
Most of what we hold is editable in the app. For anything else, write to support@harunyazgan.com.
If you are in the EEA or the UK
You have the right to access, correct, delete, restrict or object to the processing of your personal data, and to receive it in a portable form. Our legal bases are: performance of a contract (running the app and your account), legitimate interests (keeping the service secure and preventing abuse), and legal obligation where one applies. You may complain to your local supervisory authority.
If you are in Türkiye
Under KVKK Article 11 you may ask whether your personal data is processed, request information about it and its purpose, learn who it is transferred to in Türkiye or abroad, ask for correction or erasure and for those to be passed on to the recipients, object to conclusions drawn solely by automated analysis, and claim compensation for damage caused by unlawful processing. Requests go to support@harunyazgan.com, sent from the email address on your account, and are answered free of charge within 30 days; you may also apply to the Kişisel Verileri Koruma Kurumu. The full notice under KVKK Article 10 is the KVKK Aydınlatma Metni.
If you are in California
We do not sell or share personal information as those terms are defined by the CCPA/CPRA, and we do not process it for cross-context behavioural advertising. You may request access or deletion, and we will not treat you differently for asking.
Children
Our Sea is not directed at children and is not for anyone under 13, or under 16 where local law sets that age. We do not knowingly collect anything from them. If you believe a child has an account, write to us and we will remove it.
Security
Traffic is encrypted in transit. Passwords, sign-in tokens and password-reset tokens are stored hashed. Push tokens are stored as issued, because they have to be handed to Apple or Google to deliver a notification; they are useless for signing in. The server checks membership of a pair on every request rather than trusting a sign-in claim, and photo storage is partitioned per pair so that one pair's files cannot be addressed by another. No system is perfect, and we do not claim otherwise.
Changes to this page
If we change what we collect or what we do with it, we will update this page and the date at the top, and — where the change is significant — tell you in the app before it takes effect.