Privacy · Everly
Everly · Privacy policy · Version 2026-09-26

Privacy

This policy explains what Everly (Memorial Products and Services Unlimited LLC, Elberton, Georgia) collects when you use everly.memorial, why, who sees it, how long we keep it, and what you can do about it. It is written from what the service actually does today, and it is part of the terms. You will be told when it changes.

1. Who this covers

Account holders; people who visit a public memorial without an account; people who are invited, named or connected by others; and, in a limited way, the people memorials are about.

2. What we collect

Your account. Your email address, the name you give, an optional photograph of yourself and a short bio, whether you have chosen to be discoverable by name, and your email preferences.

What you add to memorials. Memories, photographs, video, recordings and documents, with the dates you attach to them; the obituary and biography of the person the memorial is for; tags; replies and reactions. Original files are kept exactly as you gave them, so a photograph may carry the data its camera embedded, such as the date taken and, if the camera recorded it, the location. The smaller copies we make for display do not carry that data.

People and relationships. The roles you hold on memorials; who invited you; the connections you make and how each side describes the other; relationship labels; who you name in a memory; who you name as a steward, by email.

Statements we record. The relationship statement you make when you publish a memorial, with the date and your account; your acceptance of the terms; a steward's claim and any owner's objection.

Activity and security records. The day you last used Everly, kept to the day. A security log of who changed what and when on each memorial, with the network address the change came from. Sign-in records: each session's start, the browser it was started from and its network address. Sign-in links and codes, which expire. How a new account came to Everly: through an invitation, a public memorial, Find a memorial or the front door, and, if you first arrived from one of our advertisements, the campaign labels in that link (see section 6).

Technical records. Server logs of requests to everly.memorial (network address, browser, page, time, errors) and performance traces that show how long each request took, kept on our own server. Aggregate counts we use to run the service, such as memorials created and storage used.

Analytics and advertising measurement. We use Google Analytics to see how the site is used in aggregate, and the Meta Pixel to measure whether our advertising on Facebook and Instagram brings people here. Section 6 says what each collects.

Payments. When purchases open: the amount, date and a transaction reference from our payment processor, and the share set aside in the preservation fund. We will never receive or store your card number.

Reports, feedback and email to us. Anything you send through the report form, the feedback form or to hello@everly.memorial, including your reply address.

Email delivery. Whether an email we sent you was delivered, bounced or was marked as spam, as reported by our email provider.

3. Where it comes from

Most of it comes from you. Some comes from other people: a member who names you in a memory or labels your relationship, an owner who invites you by email, someone who names you as a steward or connects with you, or a person who reports a memorial. When an owner imports an obituary from a funeral-home or newspaper page they give us the address of, we fetch that page once and keep the text and portrait it provides.

4. How we use it

To run the service. To show memorials to the people their visibility allows; to send the invitations, mentions, replies and steward notices the product is built on; to keep copies of files and check them; and to enforce plans and storage.

To keep it safe and fair. To limit sign-in attempts, detect abuse, act on reports, freeze memorials during disputes, and keep the record needed to decide them.

To measure and improve Everly. To understand how the service is used, which pages people arrive at and from where, whether our advertising works, to fix problems and to build new features. This may include using content and data on the service to train or improve machine-learning systems.

To pay for Everly. Like most internet services, Everly funds itself in part from data: aggregated and de-identified information about how the service is used, placements from partner organisations, and improving our own systems with what is on the service. We do not show advertisements inside a memory or a photograph, and we do not publish the contents of a private memorial. Section 11 of the terms states the licence that allows this.

To show placements. Everly may show placements from organisations whose services follow a death or prepare for one: aftercare and grief support, estate planning, and future memorialization. These would be Everly's own placements, chosen for the setting, never inside a memory or a photograph. None are shown today.

To take payment, when purchases open, and to account for the preservation fund.

To meet legal obligations, respond to lawful requests, and establish or defend legal claims.

5. Who sees it

Other people on the memorial, according to its visibility and their role. On a public memorial that is anyone, and the page may be indexed by search engines. Your name, relationship label and contributions are visible to the memorial's family; your bio and person page only to people who share a memorial or a connection with you. Your Friends & Family list is never shown to anyone.

The providers that run Everly, each seeing only what its job needs:

  • Liquid Web hosts our server and database in Lansing, Michigan, United States.
  • Cloudflare carries all traffic to everly.memorial, protects the site, and stores original files and the copies made for display. It sees network addresses and requests.
  • Backblaze holds the second copy of every preserved file.
  • Resend delivers our email and reports delivery status.
  • Google serves the typefaces on every page (Google Fonts, which sees your network address), runs Google Analytics, and holds the hello@everly.memorial mailbox (Google Workspace).
  • Meta receives what the Meta Pixel sends, described in section 6.
  • A payment processor, when purchases open, which will take payments and hold card details. This policy will name it before the first sale.

Partner organisations. Nothing is shared with any partner today. When placements begin, this policy will say what is shared, and it will carry a "Do Not Sell or Share My Personal Information" choice where the law where you live requires one, before it happens.

The people you share with. If you use the share sheet to post a public memorial's address to Facebook or another service, that is a link you open; those services then apply their own policies.

A person harmed by a false statement. We may provide the relationship statement to someone harmed by it, as the terms say.

A successor. If Everly is sold or wound up, data passes to the successor under the same terms, and every owner is told. Otherwise, only where the law requires.

6. Cookies, analytics and the pixel

Our cookies. We set two cookies of our own. everly_session keeps you signed in for up to 30 days; it is removed when you sign out or when it expires. If you arrive from one of our advertisements, we set a second cookie, ev_src, for 30 days. It holds only the campaign labels in the link you followed (utm_source, utm_medium, utm_campaign and Facebook's click id), so that a new account made from that visit can be counted toward the advertisement; if you create an account, those labels are kept with it. Neither cookie is readable by other sites. Your choice of light or dark theme is kept in your browser's local storage and never sent to us. Cloudflare may set its own operational cookie to protect the site.

Google Analytics. On everly.memorial, Google Analytics records the pages you open, how you arrived, your approximate location derived from your network address, and your device and browser type, and sets cookies beginning _ga that last up to two years so that return visits count as one visitor. We use the reports in aggregate. Google's own privacy policy governs what Google does with it, and Google offers a browser add-on that stops Google Analytics on every site.

Meta Pixel. On everly.memorial, the Meta Pixel tells Meta that a page was loaded, with the page address, your browser type and network address, and a cookie named _fbp that lasts 90 days. If you are signed in to Facebook or Instagram in the same browser, Meta may connect that visit to your account. We use this to see whether our advertising brings people to Everly and to measure it; we do not send Meta the contents of any memorial or anything you write. Meta's data policy governs what Meta does with it. You can limit this in your Facebook and Instagram ad settings, by blocking the pixel with your browser, or with a tracking-protection setting.

Neither Google Analytics nor the Meta Pixel runs on private, family-only pages any differently from public ones: both see the page address, never the page's contents. Neither runs on our staging site.

7. People who have died, and living people named in memories

A memorial is about a person who has died, or about a living person who made it for themselves. Most privacy law does not protect the dead, but their estate may have rights in their name and likeness, and the family has an interest we take seriously. The relationship statement, the dispute policy and the ability to freeze a memorial exist for this.

Memories often name living people. If you are named in a memory on Everly and want your name removed or a memory hidden, use the report form; a person reads every report. We will weigh your request against the family's record.

8. Children

Everly is not for children under 13, and we do not knowingly hold an account for one. Photographs of children appear in memorials because families' lives include them; they are added by adults responsible for that choice. If you believe a child holds an account, write to us and we will close it.

9. How long we keep things

Memorial contentWhile the memorial exists. After an owner removes it: 30 days private, then deleted from both providers.
Database backupsEncrypted nightly copies. The 14 most recent are kept on our server; an encrypted copy also leaves the server each night and is deleted on a rolling schedule. Deleted content leaves the backups on that cycle.
Your accountUntil you close it. Memorials you own alone then follow the removal path; your contributions to others' memorials stay, attributed to you.
Security log and dispute recordsFor the life of the memorial, and afterwards as long as a dispute or legal obligation requires.
Relationship statements and consentsFor the life of the account and the memorial, and afterwards as long as needed to defend a claim.
Sign-in sessionsUntil you sign out, end them in Settings, or 30 days pass.
Sign-in links and codes15 minutes, or until used.
Server logsUp to 90 days. Performance traces, 7 days.
Uploads that were never completedDeleted after 24 hours.
Analytics and pixel dataHeld by Google and Meta under their own retention periods; the cookies are described in section 6.
Payment recordsWhen purchases open: 7 years, for tax and accounting.
Reports, feedback and email to usAs long as needed to act on them, and with the memorial's dispute record where relevant.

10. How we protect it

Traffic to everly.memorial is encrypted. Sign-in uses links and codes sent to your email, so there is no password to steal. Session tokens are stored hashed. Files are checked against checksums and, for preserved memorials, held with two providers. Database backups are encrypted before they leave the server. Access to the server is restricted to named people. No method is perfect; if we learn of a breach affecting you, we will tell you as the law requires.

11. Your choices and rights

Export. Any owner can export a memorial in full at any time. You can ask us for a copy of the data we hold about you.

Correct. Edit your name, photograph, bio and email preferences in Settings; edit your own memories on any memorial where you hold a role.

Delete. Close your account from Settings, or write to us. What happens to memorials and contributions is in section 9.

Be found or not. Turn Discoverable off in Settings and nobody can find you by name or email except people who already share a memorial with you.

Email. Switch off mentions, replies and relationship emails in Settings. Notices about removal, disputes, stewardship, payment and changes to the terms are not optional while you hold an account.

Analytics and the pixel. The opt-outs are in section 6. We do not yet read the Global Privacy Control signal from browsers.

Your state or country. Residents of California and other states with privacy laws have rights to know, delete, correct, and opt out of certain sharing, and not to be discriminated against for using them. Residents of the European Economic Area and the United Kingdom have rights under the GDPR, including to object to processing. To use any right, write to hello@everly.memorial. We will verify that it is you, using the email on your account, and answer within 45 days.

12. Where data is held

Our server and database are in the United States. Files are held with Cloudflare and Backblaze in the United States. Email is sent from the United States. Google and Meta process analytics and pixel data in the United States and elsewhere under their own policies. If you use Everly from outside the United States, your data travels there.

13. Changes and contact

When this policy changes materially we will email every account at least 30 days before the change takes effect and show the date of the current version at the top of this page. Questions go to hello@everly.memorial, or by post to Memorial Products and Services Unlimited LLC, Elberton, Georgia.