Heavens Window

Install Heavens Window

On iPhone or iPad, tap Share in Safari, then Add to Home Screen.

On Android or desktop, open your browser menu and choose Install app or Add to Home Screen.

Heavens Window · Faith, remembrance and fellowship

Privacy policy

Effective 2026-10-23 · Site edition 2026-10-23

On this page
  1. Scope and operator
  2. Information you provide
  3. Technical information and each visit
  4. Location and maps
  5. Public visitor panel
  6. Visibility, flower identities, and shared links
  7. Payments, gifts, and financial records
  8. Contact messages and replies
  9. Service providers and external content
  10. Cookies and installed-app storage
  11. Use, access, and protection
  12. Retention, corrections, and requests
  13. Children, security incidents, and policy changes

Scope and operator

This policy explains how Heavens Window handles information for its remembrance and prayer community. It covers guests and members, accounts, posts, replies, tributes, flower gifts, payments, donations, advertising requests, Contact, and visitor reporting. The operator’s published contact details appear below when configured; the Contact page is the site’s general request channel.

Information you provide

Account records include your name, email address, password hash, avatar, bio, profile location, and account status. A password hash is not your readable password. We also store content and files you submit, privacy choices, friendships, blocks, reactions, reply approvals, notifications, contact messages, and administration records needed to run those functions. An administrator may create an account with a temporary password for a person requesting help.

Remembrance records can include a name, life dates, places, “where from,” biography, photos, audio, video, veteran status, service details, ownership information, and source links. A creator may supply information about someone else; proof of kinship is not routinely required. Please obtain appropriate permission and avoid exposing sensitive details about living people or children. Prayer requests and biographies may reveal religious beliefs, health information, family circumstances, or other sensitive matters. Choose carefully what to submit and who may see it.

Technical information and each visit

The site records network IP addresses, approximate locations when available, visit times, return visits, pages viewed, associated account IDs when signed in, and available member/content thumbnails and names for visitor functions. Each page visit may create a new record. Shared networks and changing addresses make IP counts imperfect; they do not reliably identify a unique person.

Authorized administrators can review detailed visit records, mark or delete records, and restrict addresses. The public visitor panel excludes administrator visits, but this is not a promise that the hosting server has no administrative access logs. Hosting and payment providers may retain their own operational and security records.

Location and maps

A location entered in a member profile may appear publicly on that member’s normal profile and map where access settings allow. Tribute maps use the submitted “where from” location. Enter a city or general area rather than a home address if you do not want an exact address shown. Locations help prioritize your own and nearby tributes, including a default nearby radius of about 20 miles where available.

When estimating location from an IP address, the site sends that address to ipwho.is. The application caches a keyed hash of the address and the returned location, and ordinarily reuses a fresh cached result for seven days. That is a refresh interval, not an automatic deletion deadline; older cache rows can remain, and an older result may be reused when a lookup fails. The separate visitor report can retain raw IP addresses and visit history until deleted. Place lookups and map displays use OpenStreetMap/Nominatim services, which receive the location query or map coordinates; a map loaded in your browser also discloses ordinary connection information to its provider.

IP-derived positions are estimates, not proof of someone’s home, identity, or exact whereabouts. A precision marker in the visitor panel describes the site’s source classification and should not be treated as verified GPS location or permission to locate a person. This application does not request browser GPS permission for these functions.

Public visitor panel

When enabled, the visitor panel can show recent locations, approximate maps, visit totals, guest heart icons, member photos/profile links, and the name or image of viewed content according to admin settings and the viewer’s access. Guest repeat indicators relate to IP counts, not a verified identity. The panel is public to the audiences enabled by the host. Closing or minimizing it changes your display; it does not erase records or stop server-side visit recording. Sign-out does not erase earlier member-associated visits. Public data omits raw IPs, email addresses, administrator visits, and locations hidden by the site team; a combination of location, time, photo, and viewed page can nevertheless identify someone.

Visibility, flower identities, and shared links

Everyone material may be publicly accessible; Friends only and Only me restrict ordinary display but do not prevent authorized administrative access. An anonymous prayer post hides its author from ordinary viewers, not administrators or necessary account records. Blocking is a site-access feature, not a guarantee against screenshots, another account, or a logged-out visit to public material.

The host may restrict tribute details for guests while permitting a preview with the person’s name, main photo, and flower gifts. Separate options can allow public tribute comments/replies, flower sender names/profile links, and guest sharing. When the limited flower-sender profile option is enabled, qualifying active senders on approved public tributes can have a guest-readable name, avatar, bio, and permitted public posts. This exception does not itself unlock a location map or private contact fields. Removing the last qualifying flower or restricting the tribute removes that exception for later requests, but cannot recall previous copies.

Public social previews may contain the tribute’s name and main photo with a generic description. Social platforms may crop, cache, or retain these after a site setting changes. A disabled sharing button does not prevent copying a public URL. Other people and search engines may retain public material independently.

Payments, gifts, and financial records

The site stores order references, account and tribute associations, flower choices or ad requests, recipient and purpose snapshots, amounts, currency, selected methods, status changes, provider order/capture identifiers, and accounting/admin notes. Donation notes and donor records are not intentionally shown publicly by the donation module. Flower sender identity can be shown under the settings described above, but it does not reveal whether a flower was paid, free, or host-sponsored to every viewer.

PayPal processes enabled PayPal and eligible Venmo transactions. Its services receive information needed for checkout and may provide the merchant with transaction and payer information under their rules. The site does not ask you to enter full card numbers or payment-provider passwords in its own forms. Checks and money orders disclose information to the named recipient and the financial or delivery services involved. The site cannot control the privacy of a financial institution or postal service.

A refund/status record is retained as part of accounting where needed. Deleting an account, flower, or placement does not necessarily erase records required to reconcile funds, handle disputes, prevent fraud, or meet legal obligations.

Contact messages and replies

Contact submissions start private in the site’s message module. The administrator can select a conversation for publication in Past messages, including the sender’s name, original message, and admin replies. The module does not separately publish the sender email field, but an email address or other personal information typed into the message body can appear with that body. Do not include sensitive information; ask the site team to keep a sensitive request private or redact it before publication.

An administrator can choose to email a reply to a supplied valid email address from the site’s no-reply address. Email may include the original message and the reply, passes through hosting/mail providers, and cannot be recalled by editing or deleting the site record. Email delivery is not guaranteed, and the no-reply address is not the request channel.

Service providers and external content

Hosting, mail delivery, payments, IP geolocation, maps, and enabled third-party media services receive information needed to provide their functions. Embedded videos, external preview images, and maps can contact third parties when loaded, including YouTube, GodTube, Vimeo, and other supported providers. They may receive your IP address, browser information, referring-page information subject to browser/referrer settings, and their own cookies. They may process information outside your state or country. The present site does not provide a universal third-party tracking opt-out or a consent-management banner.

Server-side link previews and ad-product imports request information from destination sites. Clicking a social share link or ad takes you to another service with its own practices. The present ad-placement module does not provide advertisers with a private visitor report or add advertiser-supplied tracking scripts. Public posts and creative are still visible to the same audiences as other public material. We do not operate a feature for selling private account or visitor-report data to advertisers. This description is not a claim of certification under every privacy law or a substitute for rights that apply to you.

Cookies and installed-app storage

Session cookies support sign-in, form protection, and account operation. An installed web app or browser may cache application assets such as styles, scripts, logos, and icons for availability. The current service worker caches selected app assets, not a complete offline copy of your personal pages. Third-party services may set their own cookies or storage. You can clear browser/site data or uninstall the app, but doing so does not delete server records or financial transactions. Disabling cookies may prevent sign-in or forms from working correctly.

Use, access, and protection

We use information to operate accounts and content, apply visibility and moderation, send requested account/contact communications and site notifications, process and reconcile transactions, support nearby sorting and visitor features, respond to requests, and address abuse or legal obligations. Authorized administrators have broad operational access. Access permissions, password hashing, form protections, and protected-upload delivery are used where configured; no system is completely secure, and older direct-upload copies may remain accessible until the host completes the media-protection migration. Keep private credentials out of all submitted content.

We may disclose relevant information to necessary service providers, with your direction, or as lawfully required for a valid legal process, safety issue, fraud investigation, or protection of rights. We do not promise every disclosure requires your advance permission. Any significant operator transfer must honor applicable legal duties and existing privacy commitments rather than treat private data as unrestricted public property.

Retention, corrections, and requests

There is no application-wide automatic deletion schedule for all accounts, visitor records, content, or financial records. Records remain while needed to run the service, maintain a remembrance, reconcile transactions, handle security or disputes, or satisfy legal requirements, unless removed earlier through site controls or administration. Backups and third-party logs can persist separately. A legal preservation requirement can delay deletion. We should not retain information indefinitely without a legitimate need; the host reviews retention and deletion requests case by case.

Members can edit available profile/content fields and visibility choices. Use Contact to request access, correction, a copy, account/content removal, a sensitive-message restriction, or a privacy review. Identify the relevant account or URL without sending passwords or full financial details. We may reasonably verify authority before acting and explain when lawful retention prevents complete deletion. We will honor rights and response requirements that apply to the request; this policy does not promise a right or automatic export feature that the site has not implemented. We do not charge or retaliate merely because you raise a privacy concern.

Children, security incidents, and policy changes

The service is not directed to children under 13, and they must not create accounts or submit personal information. We do not operate a parental-consent program for under-13 accounts. If you believe such information has been collected, contact the site team so it can investigate and take appropriate action. Adults posting memories or photos involving children remain responsible for permission and careful disclosure.

We investigate reported security incidents and provide notices or remedies when applicable law requires them. This policy does not establish that the operator has completed a security certification or every legally required security program. Updates show an effective date and version; material changes should be communicated through suitable site notices and require consent where law requires it. Contact the site team with privacy or security concerns.

Contact the site team

Contact form · About · Terms and payment policies · Privacy