Privacy notice
Who we are
Andrii Co. is a Washington for-profit corporation employing one or more Notaries Public licensed in the State of Washington, USA. We provide mobile notarization and apostille services across the Greater Seattle area, with an office in Bothell, WA, where we meet clients by appointment. We also do business as Bellevue Notary (bellevuenotary.net, +1 425 800 8688), a trade name of Andrii Co. on file with the Washington State Department of Revenue; this notice covers it too, including texts to and from that number.
The person responsible within the meaning of the GDPR and other national data protection laws of the member states as well as other data protection regulations is:
Andrii Co.Mailing address (post only — not an office or a meeting place):
816 Evergreen Point Rd Unit 288
Medina, WA 98039-4780
UBI number: 604505773
D-U-N-S® Number: 117198250
Email: privacy@andrii.co
Customer portal
If you create an account in our customer portal (hosted at andrii.net, separate from this marketing site), we process the personal data you enter there to schedule and deliver your services:
- Account details — your name, email address, and phone number.
- Passkey credentials — we use passkeys (WebAuthn) instead of passwords. Your device keeps the private key, and biometrics such as Face ID, Touch ID, or Windows Hello never leave your device; we store only the matching public key and a device label.
- Appointment details — the service you book, the date and time, and any meeting address you enter (including a customer address for mobile signings).
- Order, document, and shipment details — the documents you add to an order (type and apostille destination), any draft you upload, the resulting notarized or apostilled files, and the recipient name, address, phone, and email for any shipment.
- Do-it-yourself apostille requests — if you are signed in when you fill in our free apostille request form, its answers (the destination, the number and kind of documents, your name, address, email and phone), what each print put on paper, the steps you tick and the tracking numbers you add are saved to your account as a request, so you can come back to it and open it from the QR code on your printed checklist. We ask USPS or FedEx about those tracking numbers, as for any shipment, and email you when the office has your envelope and when your documents are on their way back. If you buy our prepaid labels for it, your name, address and phone go to the carrier you choose to make the two labels (you are the sender of the first and the recipient of the second): FedEx, or, for a Washington request, USPS — which also receives your email, because its rules require a label made for someone else to name that person. You pay by card through Stripe, and we email you the labels. A draft you leave untouched for 90 days is deleted. If you are not signed in, the form keeps nothing: what you type stays in the open page.
- Saved addresses — up to five postal addresses you choose to save (the names, street, city, state or region, postal code, country and phone), stored encrypted, to fill in your forms and requests. Only you see them, on your profile, where you can change or delete them; they are deleted with your account.
We are the controller of this portal data. It is stored on our application backend at andrii.net, and a sign-in token is kept in your browser's localStorage (not a cookie) to keep you signed in. We use this data only to provide, schedule, perform, ship, and account for the services you request, and we do not sell it or share it with advertising networks.
Retention. We keep your account and order records for as long as your account is active and for as long as professional, tax, and legal recordkeeping requires. Entries in the notarial journal are kept for 10 years under RCW 42.45.180, and audio-video recordings of any remote online notarization are retained for the period required by Washington's notary rules (chapter 308-30 WAC).
Identity verification
Notarial work requires us to establish who is signing, and the paperwork for a power of attorney, a consent, or an apostille has to repeat a person's details exactly as their identity documents show them — often in the destination country's own script. When the service you ask for needs them, we therefore record, in addition to the account details above:
- Your name in full — both in its native script (for example Cyrillic) and in Latin letters, because the destination country's document usually requires a particular one of them.
- Your date of birth.
- Your taxpayer number, where the destination document requires one — for example a Ukrainian ІПН/РНОКПП or a Russian ИНН.
- Your identity document — which kind it is, its number, the country that issued it, and when it expires (a passport, or a driver's licence or ID card).
- Your registration (residence) address, where the document requires it.
- Our own working notes about your matter.
Most of this you give us directly. Some of it we read from the document itself: rather than retype it, our notary may scan the machine-readable strip of a passport or the barcode on a driver's licence, which is quicker and avoids transcription mistakes. Documents you upload to an order — and the finished notarised or apostilled files — also routinely contain identity details, scans, and signatures.
If your passport has a chip. With your agreement, our app can read it on the device in front of you. The photograph and the signature held in the chip never leave that device and we never receive them. What reaches our server is only the chip's cryptographic security data, which lets the server check for itself that the passport is genuine and unaltered. We keep the result of that check — confirmed, or not proven, and why — not the data it was performed on.
How we protect it. This profile is encrypted in our database under a key kept apart from it. It is visible only to the notary: it never appears in your account pages, in any list, in a booking made through an AI assistant, or in anything a courier or other third party receives. The one exception is you — "Download my data" on the Account page includes your own profile (our internal working notes excepted).
Legal bases. Performing the service you asked for — Art. 6(1)(b) GDPR — and, for the notarial act itself, our legal obligation as a Washington notary — Art. 6(1)(c) GDPR, RCW 42.45.
How long we keep it. For as long as your account exists; it is erased when the account is deleted. The exception is the notarial journal: an entry already recorded there must be kept for 10 years under RCW 42.45.180 and cannot be deleted on request.
Booking through an AI assistant
We publish a connector that lets an AI assistant — ChatGPT, Claude, or another that supports one — look up our availability, quote a price, and send us a booking request on your behalf. Using it is entirely your choice, and nothing else in this notice depends on whether you do.
What reaches us. Only what you ask the assistant to send: the service you want, your full legal name, an email address and/or a phone number, the meeting address for a mobile signing, your preferred time, how many documents and of what kind, and any note you add. A booking made this way is a request, not a confirmed appointment — we follow up to confirm it.
What we send back. Availability, prices, turnaround estimates, and general apostille guidance carry no personal data. For a request you have already made, a status check returns only its reference, the service, its status and its times — deliberately never the meeting address, the names on the order, or our notes, so that none of those can be copied into a chat transcript. If you additionally sign in through the assistant, it can list, book, reschedule and cancel your own bookings, and that listing does include each booking's location.
No payment ever happens in the chat. We take no card or bank details through an assistant.
The assistant's provider sees your conversation. Whatever you type to ChatGPT, Claude, or any other assistant is processed by that provider under its own privacy policy and its own terms with you, before any of it reaches us. We are not the controller of that conversation and we cannot delete it for you — ask the provider. Once your request reaches us it becomes an ordinary booking record, covered by the rest of this notice.
Text messages (SMS)
We text a mobile number only as described in the “Text messages (SMS)” section of our Terms, from +1 833 876 5431, +1 877 987 7987, and +1 425 800 8688 (our Bellevue Notary line).
When we text you. Account texts — sign-in and verification codes, account and appointment notifications, and order status and delivery updates — go only to a number that has agreed to them: by ticking the account-texts box on our booking or sign-up form or on the customer portal's profile page, or by texting us from that number the verification code our website shows you, or START. When you text us, we reply in that conversation. The first time a number texts us or agrees to our texts we send it one welcome text, and never more than one in any 12 months for that number. Marketing texts go only to customers who separately opted in to them.
What we record. Your mobile number; each consent decision with the form or text it came from, the version of the wording you saw, and the time; the texts we send you and the texts you send us; and, if you reply STOP, the number and the time of the opt-out.
Legal bases. Your consent — Art. 6(1)(a) GDPR — for account and marketing texts; performance of a contract — Art. 6(1)(b) GDPR — for answering a text you send us about your booking or order; our legitimate interest — Art. 6(1)(f) GDPR — in keeping the record of each consent and of each opt-out, so that we can show why we texted a number and never text a number that said STOP.
Who receives it. Only the providers that carry our texts — Telnyx and, for texts to a number we used previously, Infobip — which receive your number and the messages only to deliver them and to register our numbers with the mobile carriers. We never sell, rent, or share your mobile number as a texting contact, or your text-messaging consent, with anyone else, for marketing or for any other purpose.
How long we keep it. The texts we send you and the texts you send us, 12 months; consent records, for as long as the account or booking they belong to exists; an opt-out, until you reply START.
Stopping. Reply STOP to any of our numbers to stop every text from all three, START to resume, HELP for help. A keyword is acted on automatically when it is the whole message; if you ask us in other words to stop texting you, a person reads it and we stop. To stop only marketing texts, use Communication preferences in the customer portal.
Network operations site (noc.andrii.net)
noc.andrii.net is the network operations site and looking glass of AS402801, the network behind this site. It runs network measurements on request (ping, traceroute, DNS and TLS checks) and shows each visitor what our network sees of their own connection.
What we record. For each request to that site: your IP address and port, the time, the host name and page requested (with its query string), the protocol, the response status, size and timing, the referring page, and your browser's user-agent string. For each measurement you run: the parameters you sent, such as the target, the address that was measured, and the outcome, including measurements we refuse. If you are signed in with PeeringDB, your PeeringDB user id is recorded with each request and measurement too. For each ticket event (a ticket opened, a reply, a change of status): your IP address, your PeeringDB user id, the ticket's number and kind, what happened and, for a change of status, the new status, but never the text. We do not keep the report about your connection, or the results of your measurements apart from the public records they find (see "Public records we keep" below), unless you attach a result to a ticket you open (see "Tickets" below).
Why. To answer abuse complaints: a measurement leaves from our addresses, so a complaint about one has to be matched to the request behind it, and repeated abuse may be reported to the network it came from. And to understand how the site is used, such as which pages send visitors to it and which tools they use. Legal basis: our legitimate interest in operating our network and that site securely and improving it — Art. 6(1)(f) GDPR.
Signing in with PeeringDB. Signing in is optional; it raises your measurement limits and lets you open tickets (below). You sign in on PeeringDB's own site, and with your approval there PeeringDB tells us your PeeringDB user id, your name, your email address, whether PeeringDB has verified your affiliation with an organization, and the networks you are affiliated with. The access tokens PeeringDB gives us are used once to read that and then discarded. Signing in creates no account on our servers: your session is a cookie in your browser holding your user id, name, email address (if PeeringDB has confirmed it), verification status, networks and its expiry, encrypted so that only our server can read it, and it lasts 7 days or until you sign out. Your email address is in the session only to fill in the ticket forms; apart from that, we keep it only in the tickets you open and the emails about them. Legal basis: providing the service you ask for — Art. 6(1)(b) GDPR — and, for the access-log entries, our legitimate interest above.
Who receives it. No one routinely. When we report abuse, we give the network the request came from its time, IP address and what was run, and if the request was signed in, the PeeringDB user id. Google Cloud stores our copy of the record (see below) as our processor.
How long we keep it. One year. Each day's record stays on our own server for about a week after the day ends; a compressed copy is kept in our Google Cloud Storage bucket in the United States (Oregon) and deleted a year after the day it covers.
Tickets. Signed in with an account PeeringDB has verified, you can open a ticket: a peering request, a question about a looking-glass result, or a general one. A ticket holds its kind and, as its owner, your PeeringDB user id, name and email address. It may also hold the network it is about and a NOC address you give us; its status and the history of its changes; the details of your request, or the result you chose to attach; and its messages, each with its time, its author and its text. Only you and the operator of AS402801 can see it. When you open a ticket or reply to one, we email the ticket or your reply to noc@andrii.net and alert ourselves internally; when we reply or change its status, we email you at the address PeeringDB gave us to say what changed, with a link to the ticket. Replies to these emails are not read: replies go on the ticket's page. Google (Gmail) sends these emails for us as our processor, and our copies of them are deleted like our other email correspondence, within 18 months after the ticket is closed. A ticket is deleted one year after it is closed; an open ticket stays until it is closed. Legal basis: providing the service you ask for — Art. 6(1)(b) GDPR.
API keys. Signed in with an account PeeringDB has verified, you can make keys that let your scripts use the site's API as you. For each key we keep a name you give it, your PeeringDB user id as its owner, when it was made and the hour it was last used, and a one-way hash of the key; we never keep the key itself, which is shown to you once. A request made with a key is recorded like any other request (above), with your PeeringDB user id and the key's id in place of the key. Revoking a key deletes it at once. Legal basis: providing the service you ask for — Art. 6(1)(b) GDPR.
The mail check. At noc.andrii.net/mail/, or through its API, you can have an email message checked: you send us its file, and we report how it was authenticated, how it travelled and what it contains. Our server reads the message once, in memory, and never writes it down or logs it; the report is shown to you and not kept. A message names other people, such as its sender and recipients: we process what it says about them only to produce the report you asked for, and keep none of it. What we keep from a message is only the public names it carries, as "Public records we keep" below describes, and nothing else of the message or of you. To report, our server looks up every host the message names in DNS and, for up to 16 networks and domains, asks the registries (RDAP) for their abuse contacts; a host name made for a single recipient may tell its owner that the message was looked at, from our server's address, never yours. For each check we record, as for a measurement, your IP address and the time, your PeeringDB user id and the API key's id if you used them, how the message reached us (as a file, or through the API), its size, the domain in its From field, and the outcome — never its content. Legal basis: providing the service you ask for — Art. 6(1)(b) GDPR — and, for the people a message names and the record of each check, our legitimate interest in providing, protecting and improving that service — Art. 6(1)(f) GDPR.
Public records we keep. When our tools check a message, a domain, an address or a network, they look up what the internet publishes about it for anyone to read: DNS records (such as a domain's SPF, DKIM keys, DMARC and MX records, and the addresses of its servers) and, where a domain signs them and our tools receive them, the DNSSEC signatures that prove what it published; the certificates servers present; the files mail standards place at fixed addresses (the MTA-STS policy, BIMI's logo and its certificate); and registration records (RDAP, which replaced WHOIS), including the network an address belongs to. We keep what our tools find, each with the dates we first and last saw it, as a history: which key signed a domain's mail and when it was replaced, which servers sent its mail, how its records changed. From a message you send us we also keep the public names it carries: the domain and selector of each signature, the server that delivered it to its recipient, and the host names its links point to (never the links themselves), each with the month it was seen. None of it is kept with anything about you: not your IP address, your account, or which check found it. We do not keep the approximate locations our tools show for addresses. The records come from public DNS, from the servers themselves and from the internet registries, not from you.
Why, and for how long. We use this history to prevent fraud (for example, to check years later that a message was really signed by the domain it names, which needs the key that domain published at the time, or to see that a domain was set up just before it was used); to keep networks and email secure, ours and others', including filtering spam and abuse and reporting it to the networks it comes from; and to diagnose problems. It is public: our tools show a domain's, an address's or a network's history to anyone who looks it up. Its value is in its length, so we keep it for up to 50 years, and review that every year. It is kept on our own servers in the United States and, from the month after it is recorded, in our Google Cloud Storage bucket in the United States (Oregon). Legal basis: our legitimate interest, and that of the people and networks our tools serve, in preventing fraud and in the security of networks and email — Art. 6(1)(f) GDPR (see its Recitals 47 and 49).
When a record is about a person. Most of these records describe machines and organizations, not people, but some can relate to a person: a domain registered in a person's name, a server run from a home connection, a name in a certificate. We never keep a person's contact details from a registration record (their name, email address, phone number or postal address): from a registration we keep its registrar, dates, status and name servers, its abuse contact, and an organization's name and country. If a record we keep relates to you, you can object to our keeping it (see "Your rights"): we will then stop showing it and delete it from every copy within a month, unless we need it to deal with fraud or abuse that involves it, or to establish, exercise or defend legal claims. We keep a note of what was removed, only so that our tools do not record it again.
That site sets cookies only when you sign in: one while you sign in, which expires after 10 minutes, and the session cookie described above. Both are needed for signing in. It runs no analytics or advertising scripts.
Data we collect
- Request logs. Our hosting provider records the IP address, user agent, and timestamp for every page request. Kept for 14 days, used only for security, abuse prevention, and debugging.
- Error reports. When something breaks in your browser — a script fails, a file will not load — the page sends us a short technical description: the error message, the file and line, and the address of the page you were on. Web addresses are cut off before any
?or#, so the identifiers and one-time links they can contain are never sent, and anything resembling an email address or a security token is masked out of the message. Your IP address is not stored and nothing identifies you or your session; identical reports are merged into a single counter. Kept for at most 30 days on our own server, and used only to find and fix faults. Legal basis: our legitimate interest in a working service — Art. 6(1)(f) GDPR. - Cookie choice. A single JSON record in your browser's
localStorage. Never transmitted to us. See the cookie table below. - Site measurement (only if you opt in). Our own first-party script counts page views — the page's address without its query, and the site that sent you there — with a random visit id and a per-tab session id it keeps in your browser, plus a small queue of unsent events (at most 200 KB, 7 days) so a visit cut short is counted when you return. On the booking form it records the steps you reach and the options you pick from our lists — for example the service, how many documents, how many days ahead the chosen time is, the destination country, the shipping carrier, and the price shown, rounded to the nearest 5 — and the codes of any errors. It also records which kind of contact link you tap (for example phone, email, text message or a messaging app), how long each page is in view and how far you scroll it. It never sends what you type — no names, emails, phone numbers, addresses, or other free text — and runs only with your analytics consent, never under a Global Privacy Control signal. Our server adds the approximate location (country, region and city) and network of your IP address, and your device type (phone, tablet or computer), operating system and browser family; it keeps the exact IP address and browser identification string for 72 hours only, for security and to match an ad conversion you consented to. Everything else is kept 14 days on our own server, used only to understand aggregate use of this site. Legal basis: your consent — Art. 6(1)(a) GDPR.
- Ad attribution (only if you opt in to advertising). If you arrive from one of our ads and you consented to advertising cookies, we keep the click reference and campaign tags from that landing — for example the Google, Meta, or ChatGPT click id and any
utm_*tags — for up to 90 days, to attribute a later enquiry or booking to the ad that brought you. Without that consent we keep none of it. Legal basis: your consent — Art. 6(1)(a) GDPR. - Information you send us. Names, document text, contact details, and any attachments — only what you choose to email to notary@andrii.co or text to our numbers (see "Text messages (SMS)").
- Payment data. When you use the "Buy" Stripe button, card details go straight to Stripe — we never see them.
- Booking, identity, and order data. If you actually engage us, we process more than the above — see "Customer portal", "Identity verification", and "Booking through an AI assistant" for what, why, and for how long.
Purposes and legal bases
Where the GDPR or a similar law applies, we process personal data only on a legal basis. In short:
| Processing | Legal basis |
|---|---|
| Account, booking, and order data — scheduling, performing, shipping, and invoicing the services you request. | Performance of a contract — Art. 6(1)(b) GDPR. |
| Establishing who is signing, and recording the identity details a notarial act, an apostille, or a consular document has to carry. | Performance of a contract — Art. 6(1)(b) GDPR; and, for the notarial act itself, legal obligation — Art. 6(1)(c) GDPR, RCW 42.45. |
| Keeping the notarial journal and the audio-video recordings of remote online notarizations. | Legal obligation — Art. 6(1)(c) GDPR; RCW 42.45.180 and chapter 308-30 WAC. |
| Security logs, sign-in IP and device history, and fraud prevention. | Our legitimate interest in keeping the service secure — Art. 6(1)(f) GDPR. |
| Analytics cookies, and texts to your mobile number — account texts and, only if you opted in to them, marketing texts. | Consent — Art. 6(1)(a) GDPR; off by default and withdrawable at any time. |
| First-party site measurement and, with advertising consent, ad attribution and conversion counting. | Consent — Art. 6(1)(a) GDPR; off by default and withdrawable at any time. |
Cookies and similar technologies
Cookies are small text files placed on your device to store data that can be recalled by a web server in the domain that placed the cookie. We use cookies — and equivalent browser storage (localStorage) — for storing and honoring your preferences and settings and, with your permission, for analyzing how this site performs. We do not use cookies for advertising, social-media targeting, or sign-in. Our separate customer portal does have a sign-in, but it keeps its sign-in token in your browser rather than in a cookie — see the “Customer portal” section below. The measurement script also carries a short-lived request token (random each time the script loads, valid 2 hours) that lets our server tell genuine reports from forged floods. It is strictly necessary to prevent abuse, needs no consent, and is not stored beyond the 14-day window above.
This site uses only the storage listed below. Optional categories are off by default; choose them via the cookie banner on first visit, or at any time via the "Cookie settings" link in the footer of any page. Where required, we obtain your consent before placing or using optional cookies that are not (i) strictly necessary to provide the website, or (ii) for the purpose of facilitating a communication.
| Name | Provider | Purpose | Retention |
|---|---|---|---|
consent_v1 | Andrii Co. (this site) | Stores your cookie choice as a single JSON record in localStorage. | 13 months in your browser only. |
pap_lang | Andrii Co. (this site) | Remembers your last selected language so we don't ask again. | Until you clear your browser data. |
andrii_portal_token | Andrii Co. (customer portal) | Keeps you signed in to the customer portal — a sign-in token in localStorage (not a cookie), set only when you sign in. | Until you sign out or the token expires (14 days). |
andrii_apple_resume:booking, andrii_apple_resume:apostille-order | Andrii Co. (this site) | Briefly saves your in-progress booking form so it can be restored after a sign-in round-trip or a reload. Never contains your cookie choice or a sign-in token. | 15 minutes in your browser only. |
| Measurement request token (inside the analytics script) | Andrii Co. (this site) | Lets the server reject forged measurement reports. | 2 hours, strictly necessary. |
ana_vid | Andrii Co. (this site) | Random visit id for opted-in site measurement. | 2 years in your browser — set only after you opt in. |
If your browser sends a Global Privacy Control (GPC) signal, we honor it as a rejection of optional cookies — we record an automatic "reject all" without asking you again.
You also have browser-level tools to control cookies and similar technologies. Most browsers let you limit which sites can set cookies, clear cookies that have already been set, or block them entirely; you can use those controls to withdraw your consent at any time. Doing so may break parts of this site that depend on the storage marked "Always on" above (language switching, payment processing).
Third parties
- Google Ads conversion measurement (Google LLC). With your advertising consent only, we report that an enquiry, booking, or payment happened — never what you browsed — so Google can count the conversion against the ad you clicked.
- Meta ad measurement (Meta Platforms, Inc.). Same, for ads on Meta's services: conversion facts for opted-in visitors only.
- ChatGPT ads measurement (OpenAI). Same, for ads in ChatGPT: conversion facts for opted-in visitors only.
- Stripe (Stripe, Inc.). If you pay online via a Stripe-hosted checkout, Stripe receives your payment details directly — we never see your card. Stripe privacy notice.
- PayPal. If you choose to pay with PayPal, you approve the payment on PayPal's own site, and PayPal receives your account and payment details directly — we never see them. We send PayPal only the amount, the currency, and our reference for your order, and we keep the confirmation number PayPal returns as the record of your payment. PayPal is an independent controller of the data it receives. PayPal privacy statement.
- CDN providers —
unpkg.comfor Phosphor Icons - Firebase Hosting (Google LLC). Serves this site and produces the request logs described above.
- Google Maps Platform (Google LLC). Address lookup and routing for bookings — when you type a meeting or delivery address, our server sends it to Google to suggest and locate addresses.
- Google Cloud (Google LLC). Hosts our application backend at
andrii.netand stores its encrypted backups. - Google Workspace / Gmail (Google LLC). Delivers our transactional email — verification codes, booking confirmations, receipts. It also holds our mailbox: we read there the emails you send us, and documents attached to them may be added to your order after we verify the message's authenticity.
- Infobip (Infobip Ltd.). No longer sends our SMS. Inbound texts to a previously used number may still transit their network.
- Telnyx (Telnyx LLC). Sends and receives our SMS — sign-in and verification codes, the verification code you text us to confirm your number, the one-time welcome text, account and appointment notifications, order status and delivery updates, the texts you send us and our customer-service replies, the automatic STOP, HELP and START answers and, only for customers who opted in to them, marketing texts — and handles the toll-free and A2P messaging registration for our numbers. It receives your mobile number and the content of those messages, which we give it only so that it can deliver them.
- Vultr. Provides the server in Seattle, WA, on which we run our own phone system: calls to +1 833 876 5431, +1 877 987 7987 and +1 425 800 8688 reach it over Telnyx's network, and it answers them. Calls to our Bellevue Notary line (+1 425 800 8688) are recorded from the greeting on, including the request you leave after it: the greeting says so before you speak and is itself part of the recording; a call to our other numbers is recorded only if an announcement at the start of the call says so. On +1 877 987 7987 you can also leave us a voicemail, after the greeting that announces the recording. The recordings and voicemails stay on that server and are deleted after about a year, and the call log (the numbers and the time of each call) after about 30 days. In addition, the request you leave on our Bellevue Notary line and a voicemail you leave on +1 877 987 7987 are copied, encrypted, to Google Cloud storage in the United States (Oregon), so that we can listen to them in our own system; Google cannot read them, because only we hold the key, and they are deleted after about a year. The phone system transcribes no call and sends none to an AI service, except when a caller to our Bellevue Notary line chooses our automatic interpreter (see Google Gemini API, below). It puts calls through to our mobile phone or, on +1 877 987 7987, to the person or office at the extension you dial. On +1 833 876 5431 and +1 877 987 7987, whoever answers hears that the call may be recorded and takes it by pressing 1, so a call nobody takes is not left on that phone's own voicemail. On the Bellevue Notary line, your request is played to us before we answer, and a call we miss can reach our mobile phone's own voicemail, which can also capture that request. If the system cannot take a call at all, Telnyx forwards it to our mobile phone directly, unrecorded, and a call we miss there can reach that phone's own voicemail. For every call it answers, the system also sends us a short record — the number you called from, if it is shown, the number you called, the time and length of the call, whether it was answered, and, if you left a request or a voicemail, a link to its encrypted copy, but no transcript — which is kept with your texts in our customer inbox on our application backend (see Google Cloud, above) for 12 months, so that we can call you back; a call nobody took also alerts us by email and on our own phone. Calls to +1 206 319 3543 ring that mobile phone directly and never reach our phone system.
- Google (Gemini API). Provides the automatic interpreter that a caller to our Bellevue Notary line (+1 425 800 8688) can choose. The line first plays an announcement in the caller's language that names Google, and the interpreter starts only if the caller presses 1. For that call, the voices of both parties are sent to Google, which transcribes and translates them and generates the translated speech. We keep no transcript. The call recording itself stays on our phone system, as described under Vultr. Google processes this for us under its terms for the paid Gemini API and does not use it to train its models. It may keep what it receives and returns for up to 55 days to detect abuse, and it may store it transiently in any country where Google or its agents have facilities. Authorized Google staff may review content that its safety filters flag.
- Apple (Apple Inc.). Sign in with Apple, if you choose it, and push notifications for our iOS app.
- AI assistant providers (for example OpenAI, Anthropic) — only if you choose to reach us through an assistant. That provider processes your conversation under its own privacy policy before any of it reaches us; we send it nothing on our own initiative and have no access to your chat history. See "Booking through an AI assistant" above.
- MaxMind GeoLite2. Approximate location of a visitor's IP address, resolved locally on our own server — no data is sent to MaxMind.
- Nova Poshta (including its Ukrainian domestic service). Receives the recipient name, phone, and address of shipments you request.
- CDEK. The same, for deliveries to the CIS region.
- FedEx, DHL Express, UPS, USPS, and Canada Post. The same, for mail and courier shipments to other destinations.
- RON platforms (Proof / BlueNotary). Will be named here when remote online notarization launches — the session then runs on the platform under its own terms.
- SANS Internet Storm Center / DShield (SANS Institute, USA). Our server exposes a decoy ("honeypot") service that no customer ever reaches: it authenticates nobody, holds no data, and exists only to observe attacks on us. The sign-in attempts made against it are submitted to the Internet Storm Center, a public attack-telemetry dataset used by security researchers — the time, the source IP address, and the username and password the attacker offered, which are often credentials stolen from someone else and replayed. ISC publishes what it receives and states that submitted data cannot be deleted, so a submission is permanent, public, and beyond our power to recall. No customer data is involved: nothing from your account, your documents, or anything you send us is ever submitted. Legal basis: our legitimate interest in network and information security (Art. 6(1)(f) GDPR). ISC privacy policy.
- AbuseIPDB (AbuseIPDB LLC, a Pennsylvania limited liability company, USA). A public IP-reputation database that network operators query before deciding whether to block an address. When an address attacks us, we may file a report against it: the address, the time, and a short description of what was attempted, written from a fixed vocabulary. Anyone who looks that address up can read the report, AbuseIPDB's terms let it republish reports, and reports do not expire — only their weight decays over time. Our reports deliberately carry no credentials, no typed input, and nothing else supplied by the reported party. AbuseIPDB operates a takedown-request procedure for a report you believe was made in error. Legal basis: our legitimate interest in network and information security (Art. 6(1)(f) GDPR). AbuseIPDB privacy policy.
We do not sell your personal data. With your advertising consent only, we report conversion facts — that an enquiry, booking, or payment happened, never what you browsed — to the advertising services we measure with: Google Ads conversion measurement (Google LLC), Meta (Meta Platforms, Inc.), and ChatGPT ads measurement (OpenAI). Each receives only what it needs to count that conversion, and only for visitors who opted in. With each conversion go its amount and a one-way-hashed (SHA-256) copy of the email address you gave us — never the address itself, and never your phone number. Google and ChatGPT also receive the ad's click id, and Meta and ChatGPT a hashed customer number and the visit's IP address, browser and approximate location (the country, region and city), to match it. We do not otherwise share your data with advertising networks. No mobile information will be sold or shared with third parties or affiliates for promotional or marketing purposes. Your text-messaging opt-in data and consent (your mobile number and your agreement to receive texts) are never sold, rented, or shared with any third party or affiliate, for any purpose. The only exception is the carriers that deliver for us: the providers that carry our texts (Telnyx, and Infobip for inbound texts to a number we used previously) receive them only to carry them, and for a shipment you ask for, the courier delivering it receives the recipient's phone number with the address — never your consent to texts. Marketing texts are sent only to customers who separately opted in to them (the marketing box on our booking form, or the Communication preferences in the customer portal); that consent is recorded with your account and can be withdrawn there or by replying STOP at any time.
If someone ships documents to you
A customer may ask us to deliver notarized or apostilled documents to you. In that case we received your name, delivery address, phone number, and possibly email address from that customer — not from you. We use these details only to deliver that shipment: they are passed to the carrier handling it (for example FedEx, DHL Express, UPS, USPS, Canada Post, Nova Poshta, or CDEK) and are kept as part of the order record.
You have the same rights over these details as our customers — access, correction, deletion, objection — described under "Your rights" below. To exercise them, email privacy@andrii.co.
Your rights
Depending on where you live, you may have the right to:
- Access the personal data we hold about you;
- Correct or delete it;
- Object to processing based on our legitimate interests, and ask us to restrict processing while your request is checked;
- Withdraw consent at any time — use the "Cookie settings" link in the footer of any page; for texts, reply STOP or use Communication preferences in the customer portal;
- Receive a copy of your data in a portable format;
- Complain to a regulator — for example, the Washington State Attorney General, the U.S. Federal Trade Commission, or your local EU/UK data protection authority.
If you have a portal account, the two most common requests are self-service: "Download my data" on the Account page gives you a copy of your data, and "Delete my account" deletes your account.
To exercise any right, email privacy@andrii.co. We aim to respond within 14 days.
International transfers
We are based in Washington State, USA. If you contact us from outside the United States, your personal data is transferred to the US. We rely on your consent and on contractual safeguards with sub-processors (e.g., Google's Standard Contractual Clauses for Analytics and Firebase Hosting).
Retention
- Cookie record: 13 months in your browser only.
- Request logs: 14 days.
- Sign-in IP and device history: 180 days.
- API request logs: kept in size-rotated files on our own server — when the fixed space fills, the oldest entries are overwritten.
- Identity profile (names, date of birth, taxpayer number, identity-document details, registration address): kept while your account exists, erased when it is deleted — except anything already recorded in the notarial journal.
- Notarial journal entries: 10 years, as required by the Revised Code of Washington 42.45.180.
- Email correspondence: deleted within 18 months after the matter is closed, unless we are required to keep it longer.
- Text messages: the texts we send you and the texts you send us, 12 months; consent and opt-out records as described under "Text messages (SMS)".
- Site measurement events: 14 days.
- Ad attribution records: up to 90 days.
- Phone calls: recordings, requests and voicemails on our phone system, about a year; its call log, about 30 days; the record of each call in our customer inbox, 12 months.
Children
This site is not directed at children under 13, and we do not knowingly collect their data.
Changes to this notice
We update this notice when our practices change. The "Last updated" date above always reflects the current version.