Chronological privacy policy

Who we are

FierceSpeed makes Chronological. FierceSpeed is based in New Zealand, and the New Zealand Privacy Act 2020 applies to the personal information we hold.

For anything in this policy, including a request to access, correct or delete your information, use the contact form.

The short version

• Nothing is public. There are no public profiles, name searches or public directories.
• Chronological is invite-only. You join through an invite link from someone who's already a member.
• Contact matching sends only hashes of your contacts' email addresses and phone numbers, and the server doesn't keep them.
• People who know your exact verified email address, or have your verified email address or phone number in their contacts, can find you. This is on by default, and you can turn it off.
• In the app, only a circle's members can read what's in it.
• Circles, messages and media are stored with Google Firebase in Sydney, Australia.
• New chat text is encrypted on your device before it is saved. Firebase stores the ciphertext and a separate decryption key so you can restore messages on a new device. This is not end-to-end encryption: circle members and people with privileged access to Chronological's Firebase project can access the key and decrypt the text. Existing messages, media, posts and comments are not encrypted this way.
• You can connect an AI assistant such as Claude or ChatGPT to search recent messages, posts and event titles or places in your circles. Only after you approve the connection, Chronological returns matching excerpts to that service, including decrypted chat text. The service handles those excerpts under its own privacy terms.
• Calls go straight between the two phones, end-to-end encrypted, and aren't recorded.
• You can delete your account in the app or on the web.

What we collect and why

To have an account, you need an invite link from a member, an email address or a Google or Apple sign-in, and a name for your profile. Everything else, such as a photo, a bio, a phone number or access to your contacts, is optional. Without it, the features that use it don't work.

Your account

• Email address, and whether you've verified it. We use it to sign you in, for the emails Chronological sends you, such as a link to confirm your address or reset your password (see Emails from Chronological), and, once it's verified, to let people find you by that exact address or by matching their contacts (see Contact matching). That's on by default, and you can turn it off (see Your choices).
• Password, if you sign in with email. Firebase Authentication checks and keeps it. Chronological's own database never stores it.
• Google or Apple sign-in. If you continue with Google, or with Apple on iOS, that service confirms who you are and shares basic account details, such as your email address, your name and, from Google, a link to your profile photo. Firebase Authentication keeps these details with your sign-in. Chronological uses the name only to fill in the name field when you set up your profile.
• Phone number, if you choose to verify one. It's used for contact matching. Firebase sends an SMS only after you request verification; Google processes and stores the number for verification and abuse prevention. You can skip verification or remove your number in Settings. We keep a private timestamp showing that you've been offered verification, so the optional offer isn't repeated across devices.
• A private copy of your sign-in details: your email address, phone number and whether each is verified. It's kept with your account. In the app, only you can read it. Chronological's server code, and people with administrator access, can also access it.

Why: to run your account, keep it secure and let people you already know find you.

How you joined

Chronological is invite-only. You join by opening an invite link from a member, and nobody can create an account any other way. A link works for 7 days, for as many people as the member who made it chose (up to 25), unless they turn it off first.

• The invite record. When you join, Chronological records who shared the link you joined through, when you joined, which link it was, how many steps you are from the first member, and how you signed in (Google, Apple or email).
• Your own copy. Your account's private record keeps who invited you: their internal account ID, and their name when you joined. In the app, only you can read it, and it shows you whose invite you joined through. Joining doesn't connect you to them.
• Your invite links. For each invite link you make, Chronological keeps the link, when you made it, when it stops working, how many people it has room for, and how many times it was opened, accepted and used to join. It stores nothing about who opened it. In the app, you see how many people joined through each of your links, not who they are.
• What people who open your link see. While your link works, people who open it see your name and profile photo before they join.
• Joining in progress. When someone accepts an invite, Chronological makes an empty account for them and holds a place on the link for an hour while they choose how to sign in. If they stop before choosing, the place is released and the empty account is deleted automatically.
• Limiting tries. To stop invite links being tried over and over, when you open or accept one, the server works out a keyed hash (HMAC-SHA256) of your connection's IP address (for IPv6, its network prefix) and keeps it with a count. Chronological's code never stores or logs the IP address itself. The hash and count expire within 2 hours and are then deleted automatically.

Who can see it: FierceSpeed administrators, in an internal dashboard that shows the invite record with people's profile names. People with administrator access to Chronological's Firebase project can also access it.

When you delete your account, your place in the invite record is de-identified, not removed: your sign-in method is removed, your entry is marked deleted, and your name is removed from the records of people you invited. The entry still has an internal account ID and its place in the record (who invited you, when you joined and through which link), so FierceSpeed administrators could link it back to you. Your invite links stop working, and people who joined through them stay members.

Why: to understand how Chronological grows, and to make sure every account comes through an invite.

Your profile

• Name (up to 50 characters), photo and bio (optional, up to 160 characters). When you choose a photo, the app shrinks it on your device to at most 1024 pixels on its longer side before uploading it.
• Whether people can find you by email or phone (see Your choices).
• When you created your profile.

Who can see it: any member of Chronological (an account that joined through an invite) that has your internal account ID. The app gives that ID to people you're connected with, people in your circles, people you send connection requests or invites to, people who send you requests, people whose contacts match you, and members who find your exact email address while discovery is on. Someone who already has your ID can still read your profile after you remove or block them. There is no public directory, name search or partial-address search. People who open your invite link also see your name and photo (see How you joined).

Profile photo links. Your profile photo is shared as a hard-to-guess link. Anyone who has that link can open the photo without signing in, until you change or remove the photo or delete your account. When someone opens your invite link, Chronological gives them that link to show your photo.

Why: so the people you know can recognise you.

Contact matching (Android and iOS)

You can also choose to match Google contacts on web, Windows and mobile. With your explicit read-only permission, the app downloads names, email addresses and phone numbers from Google's People API to your device, then applies the same local hashing before matching. It does not read Gmail messages. Google authorization tokens and downloaded contacts are held in memory, not saved by this feature.

Contact matching finds people you already know by comparing hashes, without uploading your contact list.

1. Before it reads anything, the app explains what happens and asks for permission to use your contacts. You can say no.
2. On your device, each email address in your contacts is lowercased and each phone number is put into international format, using your device's region when a number has no country code. Each one is then hashed with SHA-256.
3. The app sends only those hashes to Chronological's server, in batches. Your contacts' names never leave your device, and their email addresses and phone numbers leave it only as hashes. A hash of a phone number, or of a common email address, can be worked back out by trying likely values. What protects them is that the server only uses the hashes to look for matches and doesn't keep them.
4. The server applies a secret key to each hash (HMAC-SHA256) and looks the result up in the matching index. It sends back only matches: each person's internal account ID, name, photo link and your connection status with them.
5. You choose whether to send each match a connection request. Contacts who aren't on Chronological stay on your device unless you invite them.

The matching index has an entry for each verified email address, and each verified phone number, of people who haven't turned the setting off. An entry holds a keyed hash of the address (not the address itself), the account it belongs to, whether it's an email address or a phone number, and when it was added. Addresses are added only once they're verified, so nobody can claim someone else's. An entry is removed when the person turns the setting off or deletes their account.

To stop contact matching being used to test lots of addresses, each person has a daily limit on lookups, requests must come from the genuine app (checked with Firebase App Check), and people who have blocked you or turned the setting off are never returned.

Contact-list matching is available on Android and iPhone. On every platform, members can also enter a complete email address. It is trimmed, lowercased and hashed on the device; the server uses the hash for one lookup and does not keep it. Only opted-in people with a currently verified matching address appear. Either person's block prevents a match. An empty result can also mean discovery is off.

Exact email lookups require a signed-in, verified member and allow 20 attempts per person per UTC day, including misses. This separate endpoint does not require Firebase App Check, so it works on desktop. It creates no connection and sends no email: you choose whether to send a request.

Why: to help you find people you already know, without a public directory.

Connections, invites and blocks

• Connection requests: who sent it, who received it, how they found each other (contacts or email), its status and when it was sent.
• Connections: who you're connected with, since when, and how you connected. A connection exists only after one person asks and the other accepts.
• Blocks: who you've blocked. Blocking removes the connection, and the blocked person can't send you requests or add you to circles.
• Email invites: an invite behaves the same whether or not the address already has an account, so it can't be used to find out who's on Chronological. If the address belongs to a verified account, that person gets a connection request, a notification in the app and an email.
• Invites to people who aren't on Chronological: the email invite keeps a keyed hash of the address. To send the email, the address itself is written to Chronological's outgoing mail queue, where it's kept for up to 30 days, and passed to the email sending service (see Emails from Chronological). The email carries one of your invite links. When the person joins through it and verifies that address, the invite becomes a connection request for them to accept or decline.
• Invite links: you can also share an invite link through your device's share sheet, copy it, or have Chronological email it to one address (see Emails from Chronological). It goes wherever you choose to send it, and anyone who has it can use it to join while it works (see How you joined).

Why: so connections are mutual and you control who can reach you.

Circles, messages and media

• What you add to a circle: messages (text, photos, uploaded videos, videos recorded in the app and voice notes), posts, comments, reactions, events and RSVPs.
• Circle details: the circle's name and photo, who created it, its members, who added each member and when they joined.
• Your circle list: for each circle, the latest preview, your unread count, and whether you've muted or archived it.
• When you last read each circle. Members of that circle can see it.

Who can see it: in the app, only the circle's members. People with administrator access to Chronological's Firebase project could technically access it (see Security), and administrators see content that someone reports (see Safety reports).

Any member can add people they're connected with, and new members can see the circle's earlier messages and gallery. What happens in a circle (photos and videos added, posts, people joining) shows in its activity tab and in its members' feeds.

Photos, videos and voice notes. The app makes each photo smaller on your device before uploading it, to at most 2560 pixels on its longest side; videos and voice notes are uploaded as they are. What is uploaded is the original, kept for as long as the message or post it belongs to exists. An original can still contain details the file carried, such as the location where a photo was taken, and members who save or download it get it with those details.

Copies for display. The versions the app displays (smaller copies, thumbnails, and video and audio that play everywhere) are made on Chronological's server, with location and other identifying details removed.

Events. A get-together in a circle has a title, a date and time, a place, a host and its members' RSVPs. The first Going RSVP creates an event circle for the people going, and later Going RSVPs add people to it.

Posts to your connections. You can share a post (text, photos and videos) with everyone you're connected to, rather than with one circle. Everyone you're connected to can see it, with its comments and reactions, including people you connect with later. People who comment on it can see each other's names and comments, even if they aren't connected to each other. When you remove a connection or block someone, they can no longer see your posts. Chronological keeps the list of who can see your posts (your connections) on its server; nobody else can read it, though each person can see that they're on it.

Why: to provide circles, chat, galleries, feeds and events.

AI assistant search

If you connect an AI assistant, it can search recent text messages, posts and event titles or places in circles you currently belong to. The search covers up to 30 recently active circles, and only the latest 50 messages and 25 posts and events in each one. It returns at most 20 matching excerpts, and tells the assistant when the search window was limited. A search may not find older content.

The connection is read-only and needs your approval in Chronological. When you search, matching excerpts are sent to the AI service you connected. For encrypted chat, Chronological decrypts matching text using the Firebase-stored key before returning it. The AI provider handles what it receives under its own privacy and retention terms. The assistant cannot read your contacts, profile, media files, comments, calls or account settings, and cannot change anything in Chronological.

Calls (Android)

• A call's record: who called whom, whether it was a voice or video call, when it rang, was answered and ended, and whether it was declined, missed or couldn't connect.
• In the chat: a line in the chat that says how it went, such as "Voice call · 4:12" or "Missed video call".

Who can see it: the two people in the call. People with administrator access to Chronological's Firebase project could technically access the call's record, but never its sound or video.

The call itself. A call goes straight between the two phones and is encrypted end to end by WebRTC, the standard it uses. Its sound and video never pass through Chronological's servers, and nothing of it is recorded or stored.

Connecting. To set up a call, the two phones exchange connection details, including their network addresses, through Chronological's Firebase project, and each asks Google's public STUN service for its own internet address. During a call the other person's phone can see your IP address. There's no relay server, so some calls can't connect.

Why: to let the two people in a direct chat call each other.

Safety reports

When you report a message, post, photo or person, we keep what was reported, why you chose from the list of reasons, anything you added in the box, who reported it and when. Chronological's administrators read reports. The person you report isn't told who reported them, and reporting something doesn't remove it.

Why: to deal with abuse.

Device and diagnostic information

• Crash and error reports. Release builds of the Android and iOS apps send reports to Firebase Crashlytics when the app crashes, or when something like signing in or saving fails. A report describes the error, the app version and the type of device, and uses an identifier for your app installation.
• Analytics. Release builds of the Android and iOS apps send usage analytics to Google Analytics for Firebase, such as when the app is first opened and when a session starts. The app also records that something happened, never what was in it: a circle created, a message sent, a post written, an event created, an answer given, a circle archived, something reported, a call started, a call connected and a call that failed to connect. Each one records the kind of thing (text or photos, going or maybe, voice or video, and why a call failed) and, for a new circle, how many people are in it. No name, no text, no photo and no account identifier is part of an event. Analytics records an identifier for your app installation, your device model and operating system, and an approximate location (country, region and city) that Google works out from your IP address. On Android, it also collects your device's advertising ID, unless you've deleted that ID in your device settings.
• No setting to turn these off. The app has no setting for crash reports or analytics. The web app sends neither today.
• Notifications. If you allow notifications, the app stores a notification token for each of your devices, and its platform, so Firebase Cloud Messaging can deliver them. Tokens that stop working are removed. Settings has a switch for each kind of notification, and muting or archiving a circle stops the ones from it.
• Checks that requests are genuine. To confirm that requests come from the real app, Chronological uses Firebase App Check with Google Play Integrity on Android, Apple App Attest on iOS and reCAPTCHA Enterprise on the web. On the web, reCAPTCHA Enterprise runs a Google script that collects information about your browser and device to tell people from bots. Google's privacy policy covers it.
• Permissions. The app asks for access to your camera, microphone, photos, contacts and notifications for the features that use them.
• On your device. The app keeps a copy of your circles and their history so they open offline, and a queue of messages and uploads waiting to send. On the web, these are kept in your browser's storage, along with your sign-in session.

Why: to find and fix problems, see how the app is used, deliver notifications, block fake requests and keep working offline.

Contact form

The contact form on this website, and the deletion request form on Delete your Chronological account, send what you type to Chronological's server code (Cloud Functions), which stores it in Cloud Firestore in Sydney, Australia.

• What you send: your name, your email address, the topic you choose and your message.
• What isn't stored with it: your IP address and browser details. Like any website, the Google services that deliver the form receive them (see This website).
• Limiting messages: to stop the form being flooded, each connection can send up to 5 messages an hour, and the form has a daily limit. For this, the server works out a keyed hash (HMAC-SHA256) of your connection's IP address (for IPv6, its network prefix) and keeps it with a count. Chronological's code never stores or logs the IP address itself. The hash and count expire within 2 hours and are then deleted automatically.
• Emails about your message: when your message is stored, FierceSpeed gets an email alert with your name, email address, topic and message, and you may get a short email confirming it arrived. The confirmation doesn't repeat your name or your message, and it isn't sent if the form, or your address, has already had a lot of them that day (see Emails from Chronological).
• How long: each message is kept for 12 months after it's sent, then deleted automatically. How long the email alert is kept in FierceSpeed's inbox hasn't been decided.

Who can see it: FierceSpeed, which gets each message by email, and people with administrator access to Chronological's Firebase project. They read and answer the messages.

Why: only to reply to you and deal with your request.

Emails from Chronological

Chronological sends a few emails, each for one reason. It doesn't send newsletters or marketing emails.

• A link to confirm your email address, if you sign in with an email address and a password.
• A link to reset your password, when someone asks for one for your address and your account has a password. Chronological answers the request the same way whether or not the address has an account.
• A welcome email, once you've joined and your email address is confirmed. Your account's private record notes when it starts waiting for a confirmed address and when it was queued, so it's sent only once.
• A confirmation that your account was deleted, sent to your account's email address if it was confirmed.
• An invite email, only when a member types your address to send you one of their invite links. It has their name, the link and the date the link stops working.
• Contact form emails: a short confirmation to the address you gave, which doesn't repeat your name or your message, and an alert with your message to FierceSpeed (see Contact form).

Chronological's server code (Cloud Functions, in Sydney) sends these emails through Resend over SMTP.

• What's stored: each email waits in an outgoing mail queue in Cloud Firestore in Sydney, Australia, with the recipient's address, what the email is about (such as which invite link or which contact form message) and whether it was sent. The queue doesn't keep the email's text or its links: links to confirm an address or reset a password are made just before the email is sent. Queued emails are kept for up to 30 days, then deleted automatically.
• Invite emails: the address isn't stored with the invite link. Chronological doesn't check whether the address has an account, so the member who sends the invite can't find out whether it belongs to anyone on Chronological.
• Limiting emails: to stop these emails being used to fill someone's inbox, the server counts them. The counts are kept by account, or with a keyed hash (HMAC-SHA256) of the email address or of your connection's IP address (for IPv6, its network prefix), never the address itself. They expire within 2 days, and are then deleted automatically.
• No tracking: the emails load no images, and have no tracking pixels or tracked links.
• Deleting your account deletes the queued emails about your account, including invite emails you sent (see Deleting your account).

Who can see it: people with administrator access to Chronological's Firebase project, and Resend, which delivers the emails and stores message content and delivery logs. Resend's retention is separate from Chronological's mail queue.

Why: to confirm email addresses, help you back into your account, send the invites members ask for, and tell you your contact form message arrived.

Where it's stored and who processes it

Chronological runs on Google Firebase. Google runs these services for us.

• In Sydney, Australia: Cloud Firestore (profiles, the matching index, connections, invites, invite links and the invite record, the outgoing mail queue, circles, messages, posts, activity, events, reports, contact form messages and AI-connector authorization records), Cloud Storage for Firebase (profile photos, photos, videos and voice notes) and Cloud Functions (Chronological's server code, including contact matching, AI-assisted search, the contact form and the code that sends emails) all run in Google's australia-southeast1 region in Sydney. This means your information is stored outside New Zealand.
• Not limited to Sydney: Firebase Authentication (sign-in), Firebase Cloud Messaging (notifications), Firebase App Check with Google Play Integrity and reCAPTCHA Enterprise, Firebase Crashlytics, Google Analytics for Firebase, and Firebase Hosting (which serves Chronological on the web and this website) are Google services that aren't tied to that region, so Google may process that information in other countries.
• Apple: on iOS, notifications are delivered through Apple Push Notification service, and Apple App Attest checks that requests come from the real app.
• Your browser: on the web, notifications are delivered through your browser's push service.
• Google and Apple sign-in: if you sign in with Google, Google handles the sign-in. If you sign in with Apple on iOS, Apple handles it. Their own privacy policies cover what they do.
• Email delivery: Chronological's emails are sent through Resend. Resend stores message content and delivery logs in the United States (see Emails from Chronological).

What Chronological doesn't do

• No public profiles, name searches or public directories, and no posts anyone outside a circle can see.
• No ranking algorithm. The feed shows activity from your circles, newest first.
• No contact list upload. Only hashes are sent for matching, and they aren't stored.
• No matching on an email address or phone number that hasn't been verified, or for anyone who has turned the setting off.

Security

• Chat text uses Firebase key escrow, not end-to-end encryption. New chat text is AES-GCM encrypted on your device and stored as ciphertext. The matching decryption key is stored separately in Firebase, where current circle members can read it to restore history on another device. People with privileged access to Chronological's Firebase project can also read the key and decrypt the message. Existing messages, posts, comments, photos, videos and voice notes are not encrypted this way. Members who already downloaded keys may retain them after leaving a circle.
• AI search is read-only and needs your approval. It checks current circle membership and returns only matching excerpts to the AI service you connected. It can decrypt encrypted chat text for that search. The service receives those excerpts under its own privacy and retention terms.
• Encrypted in transit and at rest. Connections between the app and Firebase are encrypted, and Google encrypts the data it stores.
• Invite-only accounts. Firebase Authentication refuses any new account that isn't made through an invite link.
• Access rules. Every database read and write from the app, and every upload, is checked against security rules, and anything no rule allows is refused. Only members can read other people's profiles or save anything, and in the app, a circle's content can be read only by its members. Profile photos are the exception: they open through links (see Your profile). Anything that needs trust between two people, such as connecting, adding someone to a circle, matching contacts or sending an invite, is done by Chronological's server code, never by the app directly.
• Verified email first. You can't connect with anyone until your email address is verified. Google and Apple sign-ins count as verified.
• Recent sign-in to delete. Deleting an account needs a sign-in within the last 5 minutes. Otherwise the app asks you to confirm it's you first.

How long we keep it

• Your account and profile: until you change them or delete your account.
• Messages, posts and media: until the person who sent them deletes them or deletes their account. What happens to messages in shared circles after an account is deleted hasn't been decided (see Deleting your account). Deleting a message or post also deletes its photos and videos, including the originals, which are never expired or downsized while it exists.
• Matching index entries: while the address is verified on your account and the setting is on.
• The invite record and invite links: kept, including after a link stops working, so Chronological's growth numbers stay right. When you delete your account, your entry is de-identified (it keeps an internal account ID) and your links stop working (see How you joined).
• Joining in progress: a place on an invite link is held for an hour. An empty account that never chose how to sign in is then deleted automatically.
• Hashes sent for contact matching: not kept.
• Queued emails: up to 30 days, then deleted automatically.
• Hashes and counts used to limit emails: expire within 2 days (see Emails from Chronological).
• A call's record and the connection details: deleted automatically about a day after the call. The line in the chat stays as long as the chat's other messages.
• Notification tokens: until they stop working or your account is deleted.
• Crash reports and analytics: for the retention periods set in Firebase Crashlytics and Google Analytics. Deleting your account doesn't remove what was already sent.
• Safety reports: how long reports are kept hasn't been decided yet.
• Contact form messages: kept for 12 months after they're sent, then deleted automatically. The keyed hash used to limit messages expires within 2 hours. How long the email alert is kept in FierceSpeed's inbox hasn't been decided (see Contact form).
• Hashes used to limit invite link tries: expire within 2 hours (see How you joined).
• AI assistant connection records: authorization codes and rate-limit counters expire automatically; access tokens expire after an hour, refresh tokens after 90 days without renewal, and client-registration records a year after registration or last use. The OAuth server stores token hashes, not bearer tokens. Disconnecting in the AI service may revoke its tokens; if it does not, access ends when its access token expires, and it cannot renew after the refresh token expires.
• After you delete your account: see Deleting your account, below.

Your choices

• Finding you by email or phone. A setting, "Let people who have my email/phone find me", decides whether contact matching can find you. It's on by default, from when you finish setting up your profile. Turn it off and your entries are removed from the matching index.
• Contacts. Contact matching is optional. Choose "Not now", or turn off contacts access in your device settings, and connect by invite link or email instead.
• Other permissions. You can turn off camera, microphone, photos and notification access in your device settings at any time. The features that use them stop working.
• Your profile. Change your name, and change or remove your photo and bio, in Settings, Edit profile.
• Your content. Edit or delete messages you sent, delete posts and comments you wrote, and leave circles. Archiving a circle takes it out of your list and mutes it; it doesn't delete anything.
• Connections. Remove a connection or block someone at any time.
• Your account. Delete it in the app (Settings, Delete account) or on the web at chronological.fiercespeed.nz/settings/delete-account.

Deleting your account

When you delete your account, Chronological deletes your profile, your sign-in and email address, your entries in contact matching, the queued emails about your account, and everything else stored under your account, and turns off your invite links. It then emails a confirmation to your account's address, if the address was confirmed. As designed, it also deletes your circle memberships, the photos and videos you sent (including the originals), your posts, comments and reactions, your RSVPs, and the connection requests and invites you sent.

Some things can remain: a de-identified entry in the invite record (see How you joined), copies other people saved to their own devices, emails already delivered, queued emails to your address that aren't linked to your account (such as the deletion confirmation, contact form confirmations and invites other members sent you) for up to 30 days, crash reports and analytics already sent, and, if you signed in with Google or Apple, Chronological's listing in that account's settings. Some things haven't been decided yet: what happens to messages you sent in circles shared with other people, get-togethers you host, records in other people's circles that name you, and backups.

How to delete your account, and what is deleted

Children

You have to be at least 7 years old to have a Chronological account. A child under 13 needs a parent's or guardian's permission, and the parent or guardian agrees to the terms of use on their behalf.

Chronological holds the same information for a child's account as for anyone else's, and it's described on this page. A parent or guardian can ask to see what's held for their child, or ask for it to be deleted, through the contact form; deleting the account in the app or at delete your account does the same thing straight away.

Access and correction

Under the Privacy Act 2020, you can ask for the personal information we hold about you, and ask us to correct it.

• You can change your name, photo and bio in the app at any time.
• For anything else, use the contact form and choose "Privacy request". Give the email address on your account if you can. We may ask you to confirm it's your account before we act. We'll respond within 20 working days.

Complaints

If you're unhappy with how we've handled your information, tell us first through the contact form so we can try to put it right. If we can't, you can complain to the Office of the Privacy Commissioner at privacy.org.nz.

This website

fiercespeed.nz doesn't use cookies, analytics or scripts, and doesn't load anything from other websites. It's served by Firebase Hosting. Like any website, it receives your IP address, browser details and the address of the page you asked for, and Firebase Hosting (Google) uses them to deliver the page. When you send the contact form, what you type goes to Chronological's server code (see Contact form).

Changes to this policy

When this policy changes, we'll update this page and the date at the top.

Contact

To reach FierceSpeed, use the contact form.