Privacy Policy

01Di short version

Tide an Wedda nuh have no personal account — nutten fi sign up fa, no email, no password — an it nuh run advertising or sell or share yuh data wid nobody. Every install get a anonymous device identifier weh mek up at random (through Firebase Anonymous Authentication) so di app can save yuh preference dem — di tide location yuh pick an yuh save location dem, notification an Lock Screen preference dem, an display preference dem pon wi server; nutten bout who yuh is attach to it. Wi also collect usage analytics as total count, weh yuh can turn off inna di app — see §06 fi exactly wah dat include an nuh include.

02Location

Di app ask fi yuh location only if yuh tap di compass button inside di tide-location search screen, fi find di tide location weh closest to yuh. Dat location:

• get read one time, pon di device, when yuh tap di button;
• get send one time to wi server fi look up di closest tide location dem, an wi use it fi dat lookup one;
• neva save wid yuh install — a only di tide location yuh end up pick get save (see below). Like any web request, it might show up fi a short time inna wi hosting provider request log dem.

Yuh can use every part a di app, including search fi a tide location by name, widout ever give location access.

03Wah save pon wi server

Yuh install anonymous device identifier a di only key to wah wi backend (Firebase Cloud Functions an Firestore, weh wi run) keep fi it:

• Yuh tide location an save location dem — di tide location yuh pick (identifier, name, country, coordinate an which tide dataset fi draw) an any location yuh star;
• Yuh preference dem — display, BoatScore an BiteScore preference dem, an yuh smart-notification an Lock Screen schedule dem, so wi server can send wah yuh ask fa an a reinstall can pick dem up again;
• Yuh subscription status — which plan an when it done, tek from Apple signed confirmation, so di Pro feature dem weh run pon wi server know seh yuh entitle;
• Invite dem, if yuh use dem — di invite code dem weh di app mek fi yuh when yuh invite fren, an di month a PRO weh yuh earn. A code weh mek fi one particular fren can carry a name or initial weh yuh type: a only yuh see it, it keep wid di code pon wi server, an di fren neva see it. If somebody invite yuh, wi also keep which code yuh use an di day dem inna yuh first week weh yuh open di app (date one, inna yuh device time zone at first launch), fi decide if unu both earn a month a PRO. If yuh put in a invite code from a club, shop or odda group, wi record which code, fi see which club an shop di app reach, wid di date an di country, device model an app version weh describe below;
• Yuh device an app version — model, iOS version, screen size an a country weh work out from yuh IP address when di app start (nutten finer), so wi know which device an build fi support;
• Di day di app last open, an di setup report weh describe inna §06;
• Push token dem an a widget key — see §04.

Every install data keep separate from every odda install own. Di forecast data itself (di tide an wedda number fi a tide location) cache an share across every install weh use dat tide location, because it nuh depend pon who a ask. Tide location dem yuh look pon lately stay pon yuh device.

04Notification, Lock Screen, widget & Apple Watch

Every one a dese involve wi server only how it describe yah so:

• Tide notification get schedule pon yuh device. Wi server only learn if dem on an how far ahead dem warn yuh (§06).
• Smart notification: iOS give di app a push token so wi server can send di BoatScore an BiteScore summary an window alert dem weh yuh set up, through Firebase Cloud Messaging an Apple Push Notification service. Di token get remove from wi server when yuh turn dem off or yuh subscription done.
• Lock Screen summary: iOS give di app a token weh mek wi server start a Live Activity; it only get use if yuh set up a schedule. While a summary a run, a second token mek wi server freshen it up, an dat one clear when di summary done.
• Home Screen widget an Apple Watch complication dem fetch dem own data from wi server wid a random key tie to yuh install, weh di app hand to dem. Di key read yuh forecast an nutten else. Wi server note, to di day, which a dem fetch last, fi di count dem inna §06.

05Third-party data source dem

Fi show yuh a forecast, wi backend fetch data from di provider dem below. None a dem get nutten weh identify yuh — at di most, di position a di tide location yuh pick.

Odda service dem weh di app depend pon:

• Google Firebase (Cloud Functions, Firestore, Hosting, Authentication, Cloud Messaging, Analytics) run wi backend, keep di data weh describe inna dis policy, an deliver di smart-notification banner dem.
• Apple: place name weh yuh type get look up pon yuh device wid Apple MapKit search; subscription handle completely by di App Store — wi neva see payment detail, only Apple signed confirmation seh a subscription active; Lock Screen update an notification dem deliver by Apple Push Notification service; an pon first launch, di app ask Apple DeviceCheck service if dis iPhone did run di app before, an set a flag wid Apple seh it run it now. DeviceCheck keep two bit fi every device wid Apple; it nuh give wi no identifier fi di device an it nuh tell wi nutten else bout it, an wi use it only fi stop one iPhone from earn invite reward more dan one time.
• Crisp run di support chat inna di app, an only if yuh open it. It get di message dem yuh send, any name yuh give, an detail weh help wi answer: di tide location yuh pick, di app version, yuh device model an which feature dem turn on.

06Usage analytics & wah wi nuh do

Wi use usage analytics, inna two part weh wi limit on purpose. Firebase Analytics record which screen get open an name action dem — change tide location (how it get find an it country, neva which one), turn feature on or off, onboarding step, paywall an purchase result, tap pon notification an change to display preference dem. It tie to Analytics own separate anonymous identifier, weh wi neva connect to di device identifier weh describe inna §03. Separate from dat, di app tell wi server, along wid di data inna §03, which feature it set up: which kind a Home Screen widget an Apple Watch complication install, if tide alert on, if notification allow, an di display preference dem (language, unit, colour mode, haptics, moon shape). Wi server only ever read dese, an di tide location dem weh people pick, as total count every day — how much install use every feature, preference an tide location — neva as a record a any one install. Yuh can turn off all a it unda Preference dem → Data an legal → Share usage analytics: dat stop Firebase Analytics pon yuh device an lef yuh install out a every count. Beyond dat:

• No personal account, sign-in, email, or profile a no kind, an neva yuh name — di only ting weh look like a name a a nickname or initial weh yuh can choose fi a fren invite code, weh only yuh see an weh get delete wid yuh invite code dem
• No advertising, ad identifier, or tracking across app
• No selling, renting, or sharing a data wid third party fi dem own purpose
• No background location tracking — location only get read di moment yuh tap di compass button

07How long data keep & delete

If yuh change yuh tide location or preference dem, it write ova di one before — no history nuh keep. Wah keep fi yuh install stay till yuh ask wi fi delete it: if yuh delete di app it nuh remove it from wi server, because a uninstall look exactly like a phone weh just nuh open di app fi a while.

Fi get everyting weh keep fi yuh install delete, message wi from Preference dem → Help inna di app — di chat identify yuh install, so wi can find it — or email di address inna §10, an wi wi work wid yuh fi identify it.

Fi delete everyting weh keep fi yuh install also delete yuh invite code dem, weh den stop work, yuh own first-week record an any PRO weh yuh earn from invite. Fren dem weh yuh invite keep wah dem earn. Di DeviceCheck flag weh describe inna §05 a Apple hold it, nuh wi, an it stay set.

Di usage count every day inna §06 nuh hold no data fi any one install an dem keep. Firebase Analytics keep it event data unda Google standard retention setting, an Crisp keep support conversation till dem delete — ask an wi wi delete fi yuh.

08Pickney privacy

Tide an Wedda a a utility fi everybody. It neva ask fi yuh own name, age or contact detail (di only name it ever hold a a nickname or initial weh yuh might type fi a fren invite code, weh only yuh see), an it nuh collect personal information from pickney unda 13 on purpose — only di install-level preference an count dem weh describe up top.

09Change to dis policy

If dis policy change, di "Last update" date at di top a dis page wi change wid it. Change weh matter — anyting weh affect wah get collect or why — wi show yah so before dem tek effect.

10Contact