Skip to content
Safe Deposit Guide

Privacy policy

What we collect, why, who receives it, how long we keep it, and the choices you have.

Last updated November 10, 2026

The short version

  • We collect what you type into our forms or give us when you create an account, plus the basic technical data every website receives.
  • We use it to run the directory, pass your requests to the vaults you choose, run operator accounts and payments, answer you, and protect the site against spam and abuse.
  • We do not sell your personal information, and we do not share it for advertising on other sites. We run no advertising tools and no third-party analytics, and set no advertising cookies. We count page views and clicks on listings in aggregate, per day, without cookies and without storing your IP address or any identifier.
  • We keep each kind of data for a limited time. The periods are in “How long we keep it”.
  • You can ask to see, correct or delete your information at any time: write to [email protected].

Who we are

Safe Deposit Guide (“we”, “us”) is an independent online directory of private vaults and of the banks and credit unions that rent safe deposit boxes. We run it from France.

Our postal address: Safe Deposit Guide, 31 rue Pablo Picasso, 93400 Saint-Ouen-sur-Seine, France

For anything about this policy or your information, write to [email protected] (you can also use our contact page). We handle privacy requests by email only, not by phone.

What we collect, and why

If you browse the site

  • Technical data your browser sends: your IP address, browser and device type, the page you asked for, and the time. We and our hosting and security providers use it to deliver pages, keep the site secure and fix problems. It is kept in server logs (see “How long we keep it”). We do not store your IP address in our database.
  • Page views and clicks, counted in aggregate: when a page has loaded, your browser sends our own server one short message with the type of page (for example “city page”) and, on a vault's page, which vault it is. If you tap a vault's Call, Website or Directions link, it sends the same kind of message for that vault. We add each one to a daily total: for a given day, a page type and a vault, “how many views” and “how many clicks”. We do not store your IP address, a cookie, a device or browser identifier, a time of day or the page you came from, so nobody's visit can be looked up or followed from one page or day to the next. To stop one connection from inflating the totals, a limit counter uses a scrambled version of your IP address that changes every day and expires within the day. Known robots are not counted. Nothing is sent to any other company. Vault operators see these totals for their own listing (page views, phone clicks, website clicks and requests), and we use the site-wide totals to see which pages are useful.
  • Searches: a ZIP code or city you search for is used only to show results. We do not save searches in our database, but the words are part of the page address, so they appear in the server logs.
  • Maps: pages with a map load map tiles from OpenFreeMap, a free map service run from Hungary. Your browser contacts OpenFreeMap directly, so it receives your IP address and the area of the map you look at. OpenFreeMap says it uses no cookies or tracking. We send it nothing else.
  • Bot check: pages with a form use Cloudflare Turnstile, which tells people from automated programs. Cloudflare receives your IP address, browser details and similar signals for that check, under its own privacy addendum.

If you send a request to a vault

  • What we collect: your name, email, phone number if you give one, the box size and timing you choose, what you plan to store and your monthly budget if you answer those optional questions, your message if you write one, the date you agreed to share the request, and a one-way, keyed fingerprint (a hash) of your IP address that helps us spot spam and abuse. The fingerprint is not your address, and we cannot read an address from it.
  • What we do with it: we pass your request to that vault so it can contact you. You agree to this with the box you tick on the form. If the listing is covered by the operator's paid plan, the request goes to them by email right away. Otherwise it goes in one summary email a day: to the operator's account if they have claimed the listing, or, if nobody has, to the business email address published for that listing, with a link to stop these emails. (When a listing gets many requests in one day, or when the site's daily limit of immediate emails is reached, the later requests go in the listing's next daily summary instead of right away.) If we have no address for the vault, or the business asked us to stop, we pass the request on ourselves. We never hold a request back to push an operator to pay. We also receive a copy by email (or, on a very busy day, a summary) and can read it in our admin area.
  • If you ask several vaults at once: on a city page you can tick up to 3 vaults in that city and send one request to all of them. We choose none for you. We create one request per vault you ticked, with the same answers and the same date of consent, and pass each one on exactly as described above, so each of those vaults sees your answers and knows the request also went to up to 2 other vaults in the same city. We receive one email for the whole group. We allow 3 grouped requests per email address per day (UTC). We check this with a short-lived counter whose key is a one-way fingerprint of the normalized address. The counter is kept for about 26 hours at most and does not contain your address.
  • After the vault gets it: the vault handles your information under its own practices. Our Terms ask operators to use it only to answer you. We can delete our copy; we cannot make a vault delete its own.

If you write to us

The contact form and the form on the operators page ask for your name, email and message (and the name of your company, on the operators page). We also keep the date you agreed and the one-way IP fingerprint. We use them to answer you.

If you ask for a city alert

We collect your email address and the city. We email you a link to confirm it. The link works for 7 days, and we send alerts only after you confirm. If you never confirm, we delete the request 30 days after the last link we sent you. Each alert has an unsubscribe link, and unsubscribing deletes your subscription.

If you ask for a bank alert

On a bank's page you can ask us to email you if that bank stops renting safe deposit boxes. We collect your email address and the bank. We email you a link to confirm it. The link works for 7 days, and we send alerts only after you confirm. If you never confirm, we delete the request 30 days after the last link we sent you. We keep a note of which changes we have emailed you about, so that we never send the same one twice. We do not store your IP address with this request. Each email has an unsubscribe link, and unsubscribing deletes your subscription and that note.

If we send you a preview link

While the site is not fully open, we sometimes send private preview links. A link carries a label we choose (it can be your name or your company's), and we record when it was last opened and how many times. A cookie on your browser lets the link work.

If you create an operator account

  • Account: your name, work email address and password. We store the password only as a one-way hash, so we cannot read it. When you choose one, we check it against the Have I Been Pwned list of leaked passwords. Only the first five characters of a one-way (SHA-1) fingerprint of the password leave our server, so neither that service nor anyone else can tell which password you picked.
  • Proof that you agreed: the date, the version of the Terms and this policy that you accepted, and a one-way fingerprint of your IP address.
  • Your choices before sign-up: if you came from a pricing button or a listing page, we remember which plan, number of listings or listing you picked, so your dashboard can start there.
  • Your answers in the short setup: right after sign-up we ask three optional questions: which listing is yours, how many locations you run, and what matters most to you right now. We use the answers to suggest a plan and a starting number of listings on your Plans page, and, in aggregate and without your name, to see which answers and plans operators pick. They are kept with your account and deleted with it, and you can skip any question.
  • Two-factor authentication: optional for operators. If you turn it on, we store your authenticator secret and recovery codes, encrypted.
  • Staying signed in: a session record in our database holds your account number and what the session needs. It does not record your IP address or browser. If you tick “Remember me”, a longer-lived sign-in cookie keeps you signed in on that browser.
  • Email we send you: service email only: confirming your address, decisions about your listings, requests forwarded to you, password resets and notices about your plan. We do not send marketing email to operators with accounts.

If you claim or add a listing

  • The request: the listing, your name and work email, the date you agreed, a one-way fingerprint of your IP address, and what we checked to decide: for example, whether your verified email address is at the same domain as the business's website, and any note we make in review. If we send a confirmation code to an email address the business has published, we keep that address with the request.
  • How we decide: a request can be approved automatically when your verified email address matches the website's domain and nobody else manages the listing. Otherwise a person reviews it.
  • A listing you propose: if the business is not in the directory, the details you enter (name, address, website, phone, a note). They become public only after we check and source them. What you tell us about yourself does not.
  • Once approved: we keep a record linking your account to the listing: who, which listing, when and how it was verified.

If you write to us from your account

We keep your message, its topic, the listing it is about if you chose one, and your name and email from your account. Only our team reads these messages. We never pass them to other operators or to visitors.

If you subscribe to a paid plan

  • Stripe takes the payment. You pay on a page hosted by Stripe (Stripe Checkout), which collects your card or other payment details, your billing address and, if you give them, your legal name and tax number. We never see or store your card number.
  • What we send Stripe: your account email, an internal account number, the plan and a one-time checkout code that ties the payment to your account. What we keep: your Stripe customer and subscription identifiers, the plan, its status and renewal dates.
  • Receipts, invoices and cancellation are handled by Stripe, including its Customer Portal. Stripe has its own privacy policy, and also uses some information for fraud prevention and to meet legal obligations.

Business information in the directory

Listings show public business information: names, addresses, phone numbers, websites, hours, prices and policies. We collect it from the businesses' own websites, from public sources such as the FDIC, the NCUA and the Census Bureau, and from calls and emails to the businesses. When a business is run by one person, some of it can relate to that person. We use it only to describe the business. To correct or remove a listing, write to us.

Why we use it

To pass your request to the vault you chose, to send the alerts you asked for, to answer you, to run operator accounts, listing verification and payments, and to protect the site against spam and abuse. We do not use your information for advertising, and we do not build profiles of you.

Who receives your information

  • The vault or vaults you contact, with your consent (every vault you ticked, for a grouped request), and a vault's operator for the requests sent to its own listing.
  • Our service providers, who may use the information only to provide their service to us:
    • Hostinger: the server that runs the site and holds its database (Boston, United States).
    • Supabase: our former database host (United States, North Virginia). It keeps an inactive copy of the database until we delete it, no later than November 24, 2026.
    • Cloudflare: DNS, protection against attacks, the Turnstile bot check, incoming mail for [email protected], and encrypted backup storage (North America).
    • Resend: sending the email the site sends (United States).
    • Stripe: payments for operators who subscribe.
    • Google (Gmail): the mailbox where we read and answer email.
    • OpenFreeMap and Have I Been Pwned: the map tiles and the leaked-password check described above.
  • Authorities and others, when the law requires, to protect people's safety or our rights, or to look into fraud or abuse. If the business is ever sold or merged, the information goes to the new owner, who must follow this policy.

We do not sell your personal information and we do not share it for cross-context behavioral advertising, and we have not done so in the past 12 months. That includes information about people under 16. Sending your request to the vault you chose is not a sale: you asked us to do it. If we ever add sign-in with another provider (for example Google), we will update this policy before it goes live.

Cookies and similar technologies

  • Session cookie and XSRF-TOKEN: keep your session and protect forms from forged requests. They expire after 2 hours without activity.
  • sdg_preview: only if you open a preview link. It lets the link work, for as long as the link is valid (60 days at most when a link has no end date).
  • Remember-me cookie: only if you tick “Remember me” when you sign in to the operator area. It lasts about 13 months.
  • Cloudflare: Cloudflare protects the site and may set its own security cookies, for example to tell people from bots. They are strictly necessary for security, and we do not use them for advertising. See Cloudflare's cookie policy.

We use no advertising cookies, no third-party analytics and no third-party trackers. The page-view and click counts described in “What we collect, and why” set no cookie. Our fonts and icons come from our own domain. Because we do not track you across other websites and do not sell or share your information, there is nothing for a “Do Not Track” or Global Privacy Control signal to switch off.

How long we keep it

Deletion is automatic where it says so: a nightly job removes what is past its time. These are the periods in force today.

Visitors

  • Requests to vaults (single or grouped, with your answers), contact messages and messages from the operators page: 12 months after you send them, then deleted. A grouped request is deleted with its individual requests.
  • City alerts: until you unsubscribe. A request you never confirm is deleted 30 days after the last link we sent you.
  • Bank alerts: until you unsubscribe. A request you never confirm is deleted 30 days after the last link we sent you.
  • Preview links: until they expire, plus 30 days. A link with no end date stays until we delete it.

Operators

  • Your account: for as long as it is open. An account whose email address is never confirmed, and that has no listing, claim, message or paid plan, is deleted automatically 30 days after sign-up. When you ask us to close your account, we delete it, except what we must keep for billing.
  • Messages you send us from your account: 24 months after you send them, then deleted.
  • Listing claims and the evidence we used: 24 months after the decision (approved, refused, expired, withdrawn or removed), then deleted. A claim that is the basis for a listing you still manage is kept for as long as you manage it. A request nobody decides on expires after 30 days.
  • Payments: Stripe keeps payment, invoice and tax records under its own policy and the law. We keep your plan, its status and renewal dates for as long as your account exists, and afterwards for as long as tax and accounting rules require.
  • Payment technical records: our log of Stripe notifications holds only identifiers, no contact details: 90 days after processing, and never more than 12 months. One-time checkout codes: 30 days if unused, 24 months after use.

Technical records

  • Sessions: end after 2 hours without activity, and expired ones are deleted automatically.
  • Password-reset links: valid for 1 hour. Expired ones are deleted every day.
  • Counters that limit how often a form can be sent, or a page view counted, from one connection: they use a hashed (scrambled) version of your IP address. They expire within a day and are deleted by the nightly job.
  • Daily totals of page views and clicks: 25 months, then deleted. They hold only numbers per day, page type and vault, never a person.
  • Failed background tasks: 30 days, because they can contain a name or an email address.
  • Server logs (IP address, time, page requested, browser): kept only as long as we need them for security and troubleshooting, not for advertising or profiling.
  • Email copies: we also receive requests and messages by email. We aim to delete those copies within the same periods.
  • Backups: every night we make an encrypted backup of the database. We keep recent ones for about three weeks, then one a week, one a month and one a year, the oldest for up to 3 years. Information we delete from the live site can stay in older backups until they are replaced. We use backups only to restore the site after a failure, and if we ever restore one, we delete again what had been deleted.
  • Privacy requests: we keep a record of each request and our answer for 24 months, as California law requires.

Where this page gives no period, we keep information only as long as we need it for the reason we collected it, or as the law requires.

Your rights and choices

If you live in California, the California Consumer Privacy Act (CCPA), as amended by the CPRA, gives you these rights. We give the same options to everyone who writes to us, wherever they live.

  • Know and access: ask what personal information we hold about you, where it came from, why we use it and who gets it, and get a copy.
  • Delete: ask us to delete the information we hold about you.
  • Correct: ask us to fix information that is wrong.
  • Opt out of sale or sharing: we do neither, so there is nothing to opt out of.
  • Limit sensitive information: the only sensitive information we hold is your account login (the password hash and, if you use it, the two-factor secret). We use it only to sign you in and protect your account, so there is nothing further to limit.
  • No retaliation: we will not treat you differently for using these rights.

How to ask: email [email protected]. To protect you, we may ask you to reply from the email address on file, or to confirm a few details, before we act. An authorized agent can write for you with your written permission. We confirm we received your request within 10 business days and answer within 45 days. If we need more time, we tell you why and take up to 45 more days.

What we may keep: information we must keep by law (such as billing records), or need to prevent fraud and abuse or settle a dispute. A vault that already received your request keeps its own copy: ask the vault to delete it.

Categories of personal information. In the past 12 months we collected, from you and from your browser: identifiers (name, email, phone number, account number, the IP fingerprint); commercial information (your plan, its status and renewal dates); internet and network activity (pages requested, browser and device type, in server logs); business and professional information (your role and the business you run, and the evidence for a listing claim); and sensitive information (account login credentials). We use them for the reasons above. We disclosed identifiers and what you submitted to our service providers and, at your direction, to the vault you contacted. We collected no precise location, no inferences and no characteristics of protected classes.

Children

This site is not for children under 16, and we do not knowingly collect their information. If you think a child has sent us something, write to us and we will delete it.

Security

Traffic between your browser and the site is encrypted. Passwords are stored as one-way hashes, database backups are encrypted, and the admin area where we read requests and account details requires two-factor authentication. Operators can turn on two-factor authentication for their own accounts. No system is perfectly secure, so we cannot promise absolute security. If a breach affects your information, we will tell you as the law requires.

Where your information is processed

We run Safe Deposit Guide from France. The site's servers, database, email delivery and backups are hosted in the United States, and most of our providers are US companies. So your information is stored in the United States and is accessed from France by the people who run the site. Data protection laws in those places can differ from the ones where you live.

Links to other sites

Listings link to vaults, banks and other sites. Their privacy practices are their own.

Changes

If our practices change, we will update this page and the date at the top. For a material change, we will also email operators with an account.

Contact

Questions, requests or complaints about your information: [email protected].