Privacy

No analytics, and no cookie banner

This site loads no third-party script of any kind — no analytics, no tag manager, no advertising pixel, no embedded widget, and no webfont fetched from someone else’s server. The fonts are served by Omnia from this domain.

Nothing is stored on your device. The only cookie this domain sets is the sign-in cookie for Omnia’s own admin dashboard, which exists only after the owner signs in and is strictly necessary for them to stay signed in. That is why you were not asked to accept anything: there is nothing here to consent to.

What you give us when you book a call

Booking a call asks you for three things and nothing else: your name, your email address and your phone number. Stored alongside them are the time you chose, the timezone your browser reports — so that a confirmation can show your own local time beside ours — and, if you cancel and choose to say why, whatever you type in that box.

They are used to hold the call and to talk to you about it. Specifically:

• to put the call in the owner’s calendar and create the Google Meet link for it;
• to email you the confirmation, that link, a reminder an hour beforehand, and your own links to cancel or move the call;
• to attach a calendar invitation to those emails, so the call lands in your own calendar;
• to get back in touch with you about working together.

They are not sold, not rented, not shared with anyone beyond the two providers named below, and never added to a marketing list. There is no newsletter.

Where it goes

• Omnia’s own server. Your details live in a database on a server Omnia rents and administers.
• Google. The call becomes an event in the owner’s Google Calendar, and your email address appears on it as an attendee. That is what carries the Google Meet link. Google also hosts the mailbox at contact@omniaweb.io, so anything you write to that address sits with Google as ordinary email does.
• Resend. Every email is delivered by Resend, which keeps a log of messages it has sent. That log holds your name, your address and the time of your call.

How long it is kept

• Your details and your calls: indefinitely, until you ask us to delete them. There is no expiry clock — someone who spoke to us two years ago is still someone we might sensibly call back — so we would rather say that plainly than write “as long as necessary”.
• Backups: 14 days. Encrypted copies of the database are taken nightly and the older ones are destroyed.
• Resend’s log of sent email: 30 days. This is the longest anything described on this page is kept anywhere. The 30-day window is fixed by Resend and is not ours to shorten, and there is no way to delete an individual message from it.
• Web server logs: 14 days — see below.

Web server logs

Like every web server, the one serving this page records the requests it answers: your IP address, the time, the address of the page you asked for, the page you came from, and the identifying string your browser sends. The IP address is not masked or shortened, because it is the only durable record of who has been hammering the booking form if anyone ever is.

These logs are used for security and to count how much traffic the site gets — with no analytics script, they are the only measurement there is. They are kept for 14 days, then deleted automatically, and they are not backed up.

Deleting your data

Write to contact@omniaweb.io and ask. There is a button in the dashboard that does it, so this is something we can actually carry out rather than something we intend to.

You are removed from live systems immediately, along with every call you booked — and the calendar events for them, past ones included, are deleted from Google at the same time. Two copies then age out on their own, and we would rather name them than claim an erasure we cannot perform: the encrypted backups (14 days) and Resend’s log of email already sent (30 days).

If what you ask for is that we never contact you again, we keep a minimal record of that request. It sounds like a contradiction and is not: that record is how the request is honoured, and deleting it would mean forgetting you made it.

Google user data

This section is about the owner’s Google account rather than yours, and it is here because Omnia asks Google for permission to write to it.

• The permission asked for is the single scope https://www.googleapis.com/auth/calendar.events.owned — events Omnia itself created on the owner’s calendar, and no others.
• What it is used for, and the only thing it is used for: creating, updating and cancelling the Google Calendar event for a booked call, and attaching the Google Meet link that event generates. Omnia writes to the calendar and never reads it to decide anything.
• What is stored is the refresh token Google issues, held as an AES-256-GCM encrypted value in Omnia’s own database. It is never written to a log or an email.
• What is never done with it. Data obtained through Google APIs is not sold, not shared with anyone, not used for advertising, and not used for model training. Omnia’s use of it follows the Google API Services User Data Policy, including the Limited Use requirements.
• Withdrawing it takes one click in the owner’s Google account permissions. Omnia then stops writing to the calendar; bookings keep working and stop carrying Meet links.

Your rights

You can ask what we hold about you, ask us to correct it, ask us to delete it, or object to us keeping it — by writing to contact@omniaweb.io. You are also entitled to complain to your national data protection authority. Omnia decides what is collected here and is responsible for it.

Changes to this page

This page changes when the system does — it is written and reviewed alongside the code, and the date at the top is the date of the last change.