Day0

Privacy Policy

Last updated: September 20, 2026

Version française

Summary

This Policy is drafted in English. A French version of this Policy is available as set out in Section 24. This Policy is to be read together with the Terms of Use and with any notice incorporated into them by reference. In the event of a conflict concerning the processing of personal information, this Policy prevails over the Terms of Use as to the description of that processing. That precedence does not extend to the allocation of risk between the parties, and Sections 25.4 to 25.6 of this Policy and Sections 11 to 13 of the Terms of Use are not displaced by it. This Policy and the Terms of Use prevail over any summary, help article, or interface text describing the same subject matter.

Day0 stores your records on your device. You may use the Application without an account; in that case we operate no service that receives your records. If you sign in, you may enable cloud synchronisation, which stores your records on our service in encrypted form only. The key remains on your devices, and neither we nor our service providers can read the encrypted records. Email from us, if you choose to receive it, does not contain your records. The Application connects to the internet only for the purposes described in this Policy, and it does not include third-party advertising or analytics SDKs.

Section 1 — Scope

1.1 This Privacy Policy (the "Policy") describes how the publisher of Day0 (the "Operator", also referred to as "we", "us", and "our"), located in Canada, collects, uses, discloses, and protects personal information in connection with the Day0 application for iOS, Android, and the web (the "Application") and the optional account, cloud synchronisation, and email facilities offered with it (together with the Application, the "Services"). "User" means the natural person using the Application. "Personal information" means information about an identifiable individual.

1.2 This Policy applies whether or not you sign in. Where a provision applies only to signed-in users, it says so. The Application is not directed to children (Section 20).

1.3 By using the Services you acknowledge that you have read this Policy. Capitalized terms not defined here have the meaning given in the Terms of Use.

Section 2 — Two ways to use the Application

Day0 stores your records in your browser on your device. The web version does not encrypt records stored locally. You may use the Application without an account; in that case we operate no service that receives your records. If you sign in, you may enable cloud sync, which stores your records on our service in encrypted form only. The key remains on your devices, and neither we nor our service providers can read the encrypted records. Email from us, if you choose to receive it, does not contain your records. The Application connects to the internet only for the purposes described in this Policy, and it does not include third-party advertising or analytics SDKs.

2.2 You may also sign in with an optional account. Signing in does not change what remains on your device. It makes two further optional facilities available, cloud synchronisation (Section 7) and email (Section 8), each of which you enable separately.

Section 3 — Information stored on the device

3.1 The following information is created by you and stored in the Application's storage on your device.

3.2 Activity records: date, time, duration, a mood label you select, an optional free-text note, and links to the roles and items you attach.

3.5 Roles: a name, optional aliases, an optional birthday stored as month and day only, an optional note, a colour, and, if you import a public character, a link to its public avatar.

3.6 Items: a name, price, target-use count, purchase date, an optional note, and an optional product link you paste.

3.7 Settings: appearance and feature preferences.

3.8 Usage counters: anonymous counters recorded on your device to draw the statistics shown in the Application. They contain no notes, names, or links, and they remain on your device.

3.9 Reminders: if enabled, scheduled and delivered by your device's own notification system.

4. Local storage in the web version

The web version stores notes, private images, and saved places locally without encryption. Access protection, if enabled, restricts access to the Application but does not encrypt this information.

Encrypted cloud sync and encrypted backups are described in Sections 7 and 12.

5. Access protection in the web version

Biometric unlock is not available in the web version. Optional access protection may be enabled or disabled at any time. It restricts access to the Application in that browser but does not encrypt information stored there. If access protection is disabled, access to the Application is limited only by the security of the device and browser profile.

Section 6 — The account

6.1 An account is optional. If you sign in, this Section applies.

6.2 Sign-in. You sign in with an email address and a one-time code. Sign-in is operated on our behalf by an identity service provider under contract (Section 15). We do not store a password for you.

6.3 One account across applications we publish. The same account may be used with other applications we publish. Signing in to Day0 does not share your Day0 records with any other application, and signing in to another of our applications does not give that application access to your Day0 records.

6.4 Account information. Your email address, an account identifier, and a record of which devices have signed in to Day0 and when. The account does not hold your records.

6.5 Sessions. On the web, remaining signed in relies on a strictly necessary session cookie (Section 21). On iOS and Android the Application stores a sign-in credential on the device for a limited period, after which you sign in again. Signing out ends the session on that device and stops cloud synchronisation from it; it does not delete anything on the device or in the cloud.

6.6 Deleting your Day0 cloud data. In Settings you may delete everything Day0 holds for your account: your synchronised records, your device record, and your email preferences. Deletion of the primary hosted copies takes effect promptly; thereafter those copies are no longer available to you. Encrypted copies retained on backup media for disaster recovery are removed within a reasonable period in the ordinary course of rotation, and cannot be decrypted by the Operator in the meantime. Deletion does not delete the records on your devices, and it does not close the account itself, which you may continue to use with our other applications. To close the account itself, send a request from the account's email address to support@sorrydiary.net; after verification, the Operator closes the account across its applications within the time required by applicable law and deletes any remaining Day0 cloud data.

Section 7 — Cloud synchronisation

7.1 If you sign in, you may enable cloud synchronisation so that your core records are kept consistent across your devices. This Section applies only if you enable it.

7.2 What is synchronised. Activity records, roles, items, works, saved places, and a limited set of appearance and layout settings. Private images are not synced in this version; a photograph remains on the device where it was added, and other devices indicate that it is available only there.

7.3 Encryption. Everything that is synchronised is encrypted on your device with a key created on your device. The key is not sent to us in readable form. Our service stores the encrypted copies together with the minimum technical metadata needed to move them between your devices, such as identifiers, sizes, and timestamps. We do not hold the key, and neither we nor the service providers that host the service can decrypt your records. A breach of the hosted copies would therefore expose ciphertext that we cannot decrypt. Periodic backups of the hosted copies include those encrypted copies and the material needed to restore them on a device that remains signed in and holds the local key, or with the recovery code; the backups cannot be decrypted by us either.

7.4 Recovery. Unlocking your cloud data on a new device requires either a device that is already signed in or the recovery code the Application provides when you enable cloud synchronisation. We do not hold the recovery code and cannot restore access to the encrypted records if it is lost. The records on your devices are not affected.

7.5 What we can see. Because we cannot read your synchronised records, we cannot recover, search, or moderate their contents. We can see the technical metadata described above and standard request logs (Section 15).

7.6 Disabling. You may disable cloud synchronisation at any time. Disabling stops synchronising from that device and leaves what is already stored in place; deleting your Day0 cloud data (Section 6) removes it.

Section 8 — Email

8.1 If you sign in, you may choose to receive email from us. Two kinds exist, each controlled separately in Settings.

8.2 Security notices. We send a short notice to your account email address when a new device signs in to your account, when your recovery code is regenerated, or when your Day0 cloud data is deleted. These messages describe the account event only and contain no marketing. You may disable them in Settings.

8.3 Monthly letter. Off by default. If you subscribe, you receive one email a month containing product news, a selection of public content, and one labelled promotion (Section 10). We request your express consent before subscribing you, send a confirmation email, and begin sending only after you confirm. Every letter contains an unsubscribe link and supports one-click unsubscribe; unsubscribing takes effect immediately.

8.4 Content of email. Email does not contain your records, notes, moods, roles, items, places, images, or statistics. It is generated from public content and account events only.

8.5 Delivery. Email is delivered by an email service provider under contract (Section 15). We do not use open tracking or click tracking. Delivery failures and complaints reported by receiving mail systems are used only to stop sending to that address.

8.6 Information we keep. Your email address, your preferences, your language, the date and source of your consent, and the status of your subscription.

Section 9 — Character discovery

9.1 Character discovery is optional. Adding a character by typing its name does not of itself initiate a network request. Displaying catalogue or search results may cause the device to connect to a third-party content-delivery service for images, as described in the Character Discovery and Third-Party Data Notice. Textual metadata in the bundled catalogue is distributed with the Application and is not re-fetched from its source for that purpose. Online search is a further means of adding a character. This Section describes what is transmitted and to whom. The Character Discovery and Third-Party Data Notice forms part of the Terms of Use and applies to every use of the discovery features.

9.2 When you submit a search, the Application transmits the keyword you typed, the pagination parameters of the request, and the technical information ordinarily transmitted by client software, including the internet protocol address of the device, the time of the request, and basic client characteristics, to Bangumi (bgm.tv), a public community database of anime, games, and characters, to retrieve public entries such as names, aliases, roles, and a public avatar or cover image. The request carries nothing else: no records, notes, moods, roles, items, timers, photographs, settings, backups, encryption keys, account identifier, or authentication state.

9.3 Bangumi is an independent third party, not our service provider. We do not control it, and it handles what it receives under its own privacy practices and terms. Its servers may be located outside Canada, and while your request is held there it is subject to the laws of that place.

9.4 If Bangumi cannot be reached from your network, you may turn on a relay route in Settings. It is off by default. While it is on, search and image requests are sent first to a server we operate, which forwards them to Bangumi and returns the reply.

9.5 The relay does not read, store, or analyse your searches. The Operator's code on that server is prohibited from recording keywords, paths, headers, or bodies. Technical logs kept for operation and security are retained for the shortest period necessary and may include the request address; they are not used to profile you. For the protection of Bangumi against abuse, the relay maintains a short-lived, in-memory count of requests per network address, and retains at the network edge a short-lived shared copy of public replies, being approximately one minute for detail responses and approximately five minutes for search responses, so that an identical public query is not repeatedly transmitted to Bangumi. Those copies comprise the public reply only, contain no identifier of yours, and are not retained in respect of any request bearing an authenticated session. Transmission through the relay discloses the keyword and your internet protocol address to us and thereafter to Bangumi. If you do not wish to make that disclosure, leave the relay disabled.

9.6 By submitting a search you consent to this disclosure for the sole purpose of retrieving entries for your own records, and, if you have turned the relay on, to the relay handling described above. We use the keyword for no other purpose and, unless the relay is on, we never receive it. You withdraw consent by ceasing to search, by disabling the relay, or by declining the Character Discovery and Third-Party Data Notice where the interface affords that option. Withdrawal takes effect prospectively upon the next request. Withdrawal does not reverse any disclosure already made, and does not delete character cards already saved, which you may delete.

9.7 Results you choose to add are copied into a character card in your records on your device and are then stored, protected, backed up, and, if you have turned on cloud synchronisation, synchronised like the rest of your records. We keep no copy of your keywords or of what you added. Results may include characters from works intended for adults and may be inaccurate; reference is made to the Character Discovery and Third-Party Data Notice.

Section 10 — Public content and promotion

10.1 The Application retrieves a small public content file from a service we operate, at most once a day. The file is identical for every recipient and contains promotional images hosted on our service and lists of popular characters, works, and items offered as suggestions. The request carries no cookie, credential, or identifier for you or your device; as with any internet request, it discloses your internet protocol address and basic request metadata to us and our network providers.

10.2 Where the Application or the monthly letter displays promotion, it does so in a small number of fixed places, using images from our own service rather than a third-party advertising network, and each promotion is labelled as such. What is shown does not depend on you or your records, and neither the Application nor the email reports what you have seen. Opening a promotion launches your device's browser and takes you to a site operated by a third party under its own terms and privacy practices; the link passes through a counter on our service that records an aggregate count of activations and nothing that identifies you. Those aggregate counts may be retained while the promotion remains current and for a reasonable period after it is withdrawn.

10.3 The Application does not include third-party analytics, advertising, or social-media SDKs, and it does not track you across other applications or websites. This Policy does not apply to sites and services operated by third parties that you reach from the Application or from our email.

10.4 Searching the item catalogue is performed on the device from the copy of the public content file and of the bundled snapshot already stored there. The text entered for that search is not transmitted. Displaying an image of a catalogue entry may cause the device to connect to a third-party content-delivery service, as described in the Character Discovery and Third-Party Data Notice. If you paste text while adding an item, the Application extracts a name, a price, and an address from that text on the device; it does not retrieve the contents of any address so extracted. Opening a stored address later, if you choose to do so, is a connection to that destination under its own terms.

Section 11 — Purchases

11.1 This version of the Application has no in-app purchases and no paid tiers. Promotion placements are first-party and fixed; they cannot be removed by payment. We therefore receive no purchase records and no payment information from any app store. If a paid option is introduced in a future version, this Section will be updated before it ships.

Section 12 — Backups

12.1 You may export an encrypted backup of your data at any time, with or without an account. The backup is encrypted on your device with a password you choose, using industry-standard password-based encryption; we do not store that password, and it does not appear inside the backup file. Export and restore take place on your device without any network involvement. If you save the file to a cloud service or a computer of your choice, it travels directly between your device and that destination; we do not receive it. If the password is lost, the backup cannot be restored.

Section 13 — Purposes of use

13.1 We use the information described in this Policy only to: (a) operate the Application and the features you have chosen to use; (b) operate the optional account, cloud synchronisation, and email facilities that you have enabled; (c) retrieve public entries you have requested through character discovery; (d) retrieve the public content file and count activations of promotional links in aggregate; (e) maintain the security and integrity of the Services and prevent abuse; and (f) comply with applicable law.

13.2 We do not use your information for advertising, profiling, or automated decision-making, and we do not sell it. Email from us does not contain your records. The keyword of an online search is used for no purpose other than retrieving matching entries.

Section 14 — Legal bases

14.1 Where the law of your place of residence requires a legal basis for processing, we rely on: the performance of our agreement with you (operating the account, cloud synchronisation, and email that you have enabled); your consent (the monthly letter, the relay route, and any other feature you enable); compliance with our legal obligations; and our legitimate interest in keeping the Services secure and preventing abuse.

14.2 US state privacy laws. We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined under US state privacy laws.

Section 15 — Disclosure

15.1 For the optional account, cloud synchronisation, and email facilities we engage service providers in the following categories: identity and sign-in; infrastructure (hosting, database, and storage); and email delivery. They process personal information only under contract, only on our instructions, and only to the extent necessary to operate the Services; they do not use it for their own purposes, and none of them can decrypt your synchronised records. A current description of the categories of providers is available on request (Section 26).

15.2 Apart from the service providers described in Section 15.1, we disclose personal information only: (a) where required by law, regulation, court order, or a lawful request by a public authority, in which case we disclose only the information we actually hold and only to the extent required; (b) where we believe in good faith that disclosure is necessary to prevent imminent harm to a person's life or safety, limited to the minimum necessary; (c) to establish, exercise, or defend legal claims; or (d) in connection with a merger, acquisition, financing, or sale of all or part of our business, in which case the recipient may process the information only as described in this Policy or in a successor policy of which we notify you.

15.3 We cannot disclose the contents of your synchronised records in any of the cases in Section 15.2, because we cannot decrypt them. We do not sell personal information, and we do not share it for cross-context behavioural advertising.

15.4 Our services keep technical request logs for operation and security, as is customary for internet services, and delete them after a short retention period. Those logs may include the request path, a search keyword, an approximate region derived from the network (such as a country code), and a user-agent string. They are not used to profile you. We do not collect your address book, precise location, advertising identifiers, or browsing history across other sites. Bangumi (Section 9) is not our service provider; it is an independent site that you choose to query.

Section 16 — International transfers

16.1 We are located in Canada. If you sign in, your account information, your encrypted synchronisation data and its metadata, and your email preferences are stored and processed by providers located outside Canada, principally in the United States and Japan. While held there, this information is subject to the laws of those jurisdictions, and their courts, law enforcement, and regulators may be able to obtain it under those laws; for synchronised records, what could be obtained is ciphertext that we cannot decrypt.

16.2 We use providers that offer a comparable level of protection and are bound to it by contract and, where the law of your place of residence requires it, by standard contractual clauses or an equivalent transfer mechanism.

16.3 A Third-Party Source receiving a connection from your device, including Bangumi, processes what it receives under its own terms and privacy practices. Its servers may be situated outside Canada and outside your jurisdiction of residence.

Section 17 — Retention

17.1 On-device data: retained on your device until you delete it or uninstall the Application.

17.2 Account information (email address, identifier, device record): retained until you delete your Day0 cloud data or until the account is closed.

17.3 Encrypted synchronisation data: retained in primary storage until you delete your Day0 cloud data. Encrypted copies on backup media are removed within a reasonable period thereafter. Temporary copies used to keep your devices consistent are removed within about ninety days.

17.4 Email preferences and consent records: retained while a subscription or notice setting is active, and removed when you unsubscribe and delete your email record or when you delete your Day0 cloud data. We may retain a record that an address has unsubscribed in order to honour that choice.

17.5 Purchase records: retained for as long as the purchase entitles you to the feature and as required by tax and accounting law.

17.6 Technical request logs: deleted after a short retention period. Aggregate, non-identifying activation counts of promotional links: retained while the relevant promotion remains current and for a reasonable period after it is withdrawn.

Section 18 — Security

For the web version, we protect personal information by keeping synced records encrypted with a key we do not hold, by encrypting backups, and by limiting what our services store to what is needed to operate them. Records stored locally in the browser are not encrypted, and biometric unlock is not available. No method of storage or transmission is completely secure, and the security of the information in the browser also depends on you protecting your device, browser profile, and recovery code. If a security incident involving our Services affects your personal information in a way that creates a real risk of significant harm, we will notify you and the relevant authorities as applicable law requires.

18.2 No method of storage or transmission is entirely secure, and the security of the information on your device also depends on you protecting your device, its lock screen, and your recovery code. We do not represent that the Services are free of vulnerability.

18.3 If a security incident involving our Services affects your personal information in a way that creates a real risk of significant harm, we will notify you and the relevant authorities as applicable law requires.

Section 19 — Your rights and how to exercise them

19.1 In the Application you may view and edit any record, role, or item; delete individual records; hide roles and retire items while preserving their history; export an encrypted backup; and use "Clear all data" to erase records and settings the Application has stored on that device. Cloud-unlock material on a signed-in device is removed when you sign out or delete Day0 cloud data. If you have signed in, you may additionally sign out, remove a device, enable or disable cloud synchronisation, change or withdraw your email choices, and delete your Day0 cloud data, in each case in Settings.

19.2 Email choices. You may withdraw consent to the monthly letter at any time by unsubscribing. Security notices concern your account and may be disabled in Settings. Unsubscribing from the letter does not disable security notices, and disabling security notices does not unsubscribe you from the letter.

19.3 Rights under the Personal Information Protection and Electronic Documents Act (PIPEDA). You may request access to the personal information we hold about you, request that it be corrected, ask about our personal-information practices, challenge our compliance with PIPEDA, and withdraw consent subject to legal or contractual restrictions. Depending on where you live, you may also have the right to delete or export your personal information, to restrict or object to its processing, to data portability, and to lodge a complaint with a supervisory authority. We honour these rights regardless of where you live. Because we cannot decrypt your synchronised records, access to and correction of their contents are exercised directly in the Application; other requests may be sent to the address in Section 26. To protect your information, we act on account-related requests only after verifying them against the account's email address. We respond within the time required by applicable law and in any case within thirty days, unless an extension is permitted.

Section 20 — Children

20.1 The Application is intended for adults and is not directed to children. We do not knowingly collect personal information from anyone under 13 years of age, or under a higher age where the law of your place of residence requires parental consent for online services. If you believe a child has created an account, contact us and we will delete it.

Section 21 — Local storage and similar technologies

The web version of the Application and the Operator's website use strictly necessary session cookies to keep a User signed in, and local storage on the device or in the browser to hold records and preferences. That local storage is not used for advertising or cross-site tracking. The Operator does not use advertising or analytics cookies, pixels, or device fingerprinting. Because the Operator does not track visitors across sites, the Services behave the same whether or not the browser sends a "Do Not Track" signal.

Section 22 — Amendment of this Policy

22.1 The Operator may amend this Policy. When it does, it will revise the "Last updated" date and make the current version available in the Application and on its website. If a change materially affects signed-in users, the Operator may additionally notify them within the Application. Continued use of the Services after an amendment takes effect constitutes acceptance of it, except where applicable law requires prior consent for that change.

Section 23 — Complaints and supervisory authorities

23.1 If you have a complaint concerning the handling of your personal information, you may raise it with us at the address in Section 26; we will consider and respond to complaints in good faith. If you are not satisfied with our response, you may contact the Office of the Privacy Commissioner of Canada (www.priv.gc.ca). A User located in Quebec may lodge a complaint with the Commission d'accès à l'information du Québec. Depending on where you live, you may also lodge a complaint with your local data protection or privacy authority.

Section 24 — Language

24.1 A French version of this Policy is available within the Application and may be selected by the User at any time. A User in Quebec, and any other User who so requests, may obtain that French version within the Application and at the address in Section 26. Where a User, having obtained the French version, expressly elects to be bound by the English version, the parties have by that express election required that this Policy and all related documents be drawn up in English. Une version française de la présente politique est disponible au sein de l'Application et peut y être consultée et sélectionnée en tout temps. Un utilisateur situé au Québec, et tout autre utilisateur qui en fait la demande, peut obtenir cette version française au sein de l'Application et à l'adresse indiquée à l'article 26. Lorsque l'utilisateur, après avoir obtenu la version française, choisit expressément d'être lié par la version anglaise, les parties ont par ce choix exprès exigé que la présente politique et tous les documents connexes soient rédigés en anglais.

Section 25 — General

25.1 Relationship to other documents. This Policy forms part of the Terms of Use. Where this Policy and the Terms of Use are inconsistent as to the collection, use, disclosure, retention, or protection of personal information, this Policy prevails; in all other respects the Terms of Use prevail. The precedence of this Policy extends only to the description of those processing rules; it does not extend to the allocation of risk between the parties, and Sections 25.4 to 25.6 of this Policy and Sections 11 to 13 of the Terms of Use are not displaced by it.

25.2 Severability. Where any provision of this Policy is held invalid, unlawful, or unenforceable, that provision is to be severed to the minimum extent necessary and construed so as to give effect to the intention of the parties to the greatest extent permitted, and the remaining provisions continue in full force.

25.3 Non-waivable rights. Nothing in this Policy excludes or limits any right conferred upon a User by applicable privacy or consumer protection legislation which that User cannot waive. Where the User is a consumer in Quebec, the Consumer Protection Act (chapter P-40.1) applies, and any stipulation of this Policy that is prohibited by that Act does not apply to such User.

25.4 No warranty. The Services are furnished "as is" and "as available". To the fullest extent permitted by applicable law, the Operator disclaims all warranties, conditions, representations, and terms of every kind, whether express, implied, statutory, or collateral, in respect of the Services and of the collection, use, disclosure, and protection of personal information, including without limitation any warranty of accuracy, completeness, or timeliness, and any warranty that the Services or the storage of personal information will be uninterrupted, timely, secure, or error-free. Section 11 of the Terms of Use applies to this Section with the substitution of references. Section 11.3 of the Terms of Use, and the rights there preserved, apply to this Section as they apply to that Section.

Statement for consumers in Quebec, given immediately before the stipulations that follow: the stipulations of Sections 25.5 and 25.6 below, and any stipulation as to the law governing this Policy and as to the forum for its enforcement, are prohibited by the Consumer Protection Act (chapter P-40.1) and do not apply to a consumer in Quebec, who may bring proceedings before the courts of Quebec under the law of Quebec.

25.5 Limitation of liability. To the fullest extent permitted by applicable law, the Operator shall not be liable for any indirect, incidental, special, consequential, exemplary, aggravated, or punitive damages, nor for any loss of data, Records, profits, revenue, goodwill, opportunity, or anticipated saving, arising out of or in connection with the Services or with the handling of personal information, howsoever arising. The aggregate liability of the Operator in respect of all claims arising out of or in connection with the Services, this Policy, or the handling of personal information shall not exceed the amount set out in Section 12.3 of the Terms of Use, which amount this Policy adopts as its own. Sections 12.1 to 12.4 of the Terms of Use apply to this Section with the substitution of references.

25.6 Indemnity. To the fullest extent permitted by applicable law, the User shall indemnify and hold harmless the Operator and its directors, officers, employees, contractors, and agents from and against all claims, demands, proceedings, losses, damages, liabilities, penalties, costs, and expenses, including reasonable legal fees, arising out of or in connection with any use of the Services by the User in breach of the Terms of Use, or any misrepresentation by the User in connection with an access, correction, or deletion request under this Policy. Section 13 of the Terms of Use, including the reservations and undertakings there set out, applies to this Section with the substitution of references.

25.7 Provisions of the Terms of Use that this Policy does not restate. This Policy does not restate, and is not intended to displace, the following provisions of the Terms of Use, which apply as there written: Section 5 (representations and undertakings of the User); Section 6 (acceptable use); Section 16 (notices from rights holders; a counter-notification procedure is not applicable for the reasons there stated); Section 19 (no waiver); Section 20 (survival); Section 21 (assignment); Section 22 (third-party beneficiaries, including Apple Inc. and its subsidiaries); and Section 24 (governing law and jurisdiction, which governs this Policy save where applicable privacy legislation provides otherwise).

Section 26 — Contact

26.1 Questions, requests, and complaints about this Policy may be sent to support@sorrydiary.net and are deemed given upon receipt. The Operator may give notice to the User within the Application.