개인정보 처리방침

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.

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).

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.

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.

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.

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 record the report about your connection or the results of your measurements: they are shown to you and not kept, 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.

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.