Information you provide
If you contact us through a form or email, we may receive the name, email address, message, and any information you choose to include. Please do not send sensitive personal information.
Information collected automatically
The hosting provider may process technical information such as IP address, browser type, requested pages, and timestamps in server logs for security, troubleshooting, and service operation. This starter site does not intentionally create member profiles.
Photos and stories
Photos, names, captions, and stories should be submitted only with permission from the people shown or named. We may decline, remove, or correct material at our discretion. Contact us to request a correction or removal.
Cookies and similar technologies
The current static site does not intentionally use advertising cookies or analytics. Hosting infrastructure or embedded third-party content may behave differently. Review all scripts and integrations before publishing this statement.
Use and sharing
We do not sell personal information as part of this starter site. Information may be handled by hosting, security, or communications providers when necessary to operate the site, or disclosed when required by law or to protect rights and safety.
Retention and security
We keep messages and server records only as long as reasonably needed for their purpose, subject to hosting-provider practices and legal obligations. No website can promise absolute security; avoid sending confidential details through public forms.
Your choices
You may ask us to access, correct, or delete information you submitted, subject to legal and operational limits. California and other jurisdictions may provide additional privacy rights depending on the site operator, processing, and applicable law.
Children
This site is intended for a general community audience and is not designed to knowingly collect personal information from children. A parent or guardian may contact us about content involving a child.
Contact and changes
For privacy questions or requests, use the contact page linked in the website navigation. Please include the relevant page and a concise description of your request. Do not send passwords or sensitive identity documents through a public guestbook.
Effective date: October 20, 2026. This page was last updated October 20, 2026.
Information collected through submissions
When a visitor sends a message, submits a guestbook entry, or provides a photograph or story, the information received is the information included in that submission and any technical data needed to receive it. A contributor should limit a submission to details that are relevant to the community page. Do not include passwords, payment card numbers, government identification numbers, private medical information, or another person’s confidential details. If a submission includes an email address or phone number in a public field, that detail may be visible to anyone who can view the page. Private contact channels should be used for requests that are not meant for public display.
Use of public content
Public guestbook messages and community stories may be displayed with a chosen name, caption, or image. Visitors may be able to copy, screenshot, quote, or share public material, and search engines or third-party archives may retain copies. Removing content from the website does not guarantee removal from copies outside the operator’s control. The operator may preserve a submission in a limited backup to recover from accidental loss, maintain site integrity, or address a dispute. Public content should therefore be submitted only when the contributor is comfortable with the intended public audience.
Data minimization and accuracy
We seek to avoid asking for information that is not needed to run a community feature. A visitor may choose a display name rather than provide a legal name, unless a separate feature clearly requires identification. Please keep submitted information accurate and avoid describing uncertain recollections as verified facts. If you need to correct a public contribution, contact the operator and identify the page and the correction. We may ask a reasonable question to confirm that the person making a request has authority over the information, while avoiding unnecessary collection of additional identity documents.
California requests
A California resident who wishes to exercise a privacy right may submit a request through the website’s published contact method. A request should state whether it concerns access, correction, deletion, or information about disclosures and should identify the relevant interaction or page. We may verify the request using information already held, and may ask for additional information only when reasonably needed to protect against fraud or unauthorized disclosure. Applicable California law contains definitions, thresholds, exceptions, and response procedures; a request will be handled according to those rules rather than assuming every request has the same outcome.
Sensitive information and minors
International data protection
Where the GDPR or another data protection law applies, the operator will assess the applicable controller responsibilities, lawful basis, transparency, retention, security, and individual rights. Depending on the circumstances, a person may request access, correction, erasure, restriction, portability, or object to processing, or withdraw consent. Rights are subject to lawful exceptions and verification. Transfers from a regulated region to another country may require an adequacy decision, contractual safeguards, or another recognized transfer mechanism. This policy does not imply that every jurisdiction’s law applies to every visitor.
Service providers
Hosting, security, email, or form providers may process information to deliver the website or a requested feature. We seek to use providers with appropriate safeguards and to limit their use of information to the services they perform, where required by law or contract. A provider may also act as an independent controller for its own legally permitted purposes, such as security or billing. The operator does not control the privacy practices of independent external websites linked from FILMANTRA FRIENDS; review their policies before submitting information there.
Retention and backups
Retention periods depend on the information and its purpose. Public stories may remain for the life of the community archive or until a valid removal request or editorial decision. Operational logs and spam records should be retained only as long as needed for security, troubleshooting, or legal needs. Backups may be retained on a rolling schedule and may not be edited item by item; they should expire through ordinary rotation unless preservation is necessary. When information is no longer required, it should be deleted, anonymized, or otherwise handled in accordance with applicable law.
Security and breach response
Reasonable safeguards may include restricted administrative access, strong credentials, encrypted transmission where supported, software updates, and separate backup handling. No website can guarantee absolute security, and users should avoid sending confidential information through ordinary forms. If an incident compromises personal information, the operator will assess applicable notification requirements, including California breach-notification law and other relevant state or international rules. Notifications, when legally required, will be made to affected people or authorities with the content and timing prescribed by law.
Changes and contact
The policy may change when the site adds accounts, memberships, analytics, advertising, or other functions. Material changes will be reflected on this page and, where required, brought to visitors’ attention or submitted for renewed consent. For a privacy inquiry, use the contact method published on the website and provide the page or feature involved. Please do not send passwords or sensitive identity documents in an ordinary email. The operator will review the inquiry under applicable law and explain any limitation on the request.
Community photographs and stories
When a contributor sends a photograph, caption, or personal story, the operator may receive information embedded in the submission as well as the visible content. Image files can contain metadata such as a camera model, creation time, or location coordinates. Contributors should review and remove metadata they do not wish to share before uploading. The operator may resize or convert images to make pages load more efficiently; such processing should not be used to infer sensitive traits or to create unrelated profiles. If a photograph is published with a caption, the caption is intended to provide context and should not expose private details beyond what is appropriate for a community memory. Please avoid sending images of documents, screens, addresses, or other material that reveals information unrelated to the story.
Data minimization and access
The operator should limit access to nonpublic information to people who need it to maintain the website, respond to submissions, or address a security issue. Administrative credentials should be unique, protected, and not shared through public messages. A volunteer who helps edit stories should receive only the access necessary for that task and should not download a full contact list merely to make a page change. When an account or service relationship ends, access should be removed promptly. These safeguards reduce exposure but cannot eliminate all risk, particularly where a hosting provider or network service is involved. Visitors should use the published contact channel for private requests rather than placing a request in the public guestbook.
Requests from individuals
A person may ask what information the site holds about them, request correction of an inaccurate detail, or ask that a contribution be removed. The operator will evaluate the request under applicable law and the context of the contribution. To locate a record, it may be helpful to provide the page address, approximate submission date, and display name used; do not send a password or unnecessary identity document. The operator may ask a follow-up question where the request is ambiguous or where reasonable verification is needed. A request involving another person's information may be limited to protect that person's rights. If a request is denied in whole or part, the response should explain the reason and any available review or complaint route when law requires it.
Backups and continuity
Website backups are created to recover from accidental deletion, software failure, or a hosting incident. A backup may contain a copy of a guestbook entry or image that has since been changed or removed from the public page. Backup copies are not intended to be a separate public archive or to be searched for unrelated purposes. They may remain until the backup cycle expires or until a recovery process overwrites them. If the operator restores a backup, it should check whether doing so would reintroduce a removed contribution or overwrite newer submissions. Site updates should replace code and design assets without replacing the persistent community data store. This operational separation is important for both privacy and preservation.
Privacy in shared devices
Visitors who use a shared computer or public device should consider whether the browser saves form entries, login sessions, or local preferences. A public guestbook message is visible by design, but a private contact form response may be displayed in the browser history or remain in an open tab. Close the session, avoid saving passwords on shared devices, and clear local browsing data if appropriate. The operator cannot control the configuration of a visitor's device or the behavior of browser extensions. If the site later offers accounts, it should explain how sign-out works and should avoid displaying private account details in public pages or URLs.
Data quality and correction
We try to keep information used to operate the website accurate enough for its purpose. A display name or recollection may be intentionally informal, but contact details used to respond to a private inquiry should be corrected when a person identifies an error. We may ask which submission or page is involved and whether the requested change concerns a public caption, a private communication, or a technical record. A correction to a public story will normally be limited to the information at issue rather than changing unrelated content. If an entry is part of a shared historical account, the operator may preserve an explanatory note or ask the contributor for clarification. We do not promise to maintain a complete profile about any visitor, and we do not use a person's request as permission to collect unrelated information.
Privacy review for new features
Before adding accounts, mailing lists, membership tools, event registrations, or other features that collect new categories of information, the operator should assess what information is truly needed, who can access it, how long it will remain, and whether a separate notice or consent is required. A feature should not collect an email address simply because it might be useful someday. If a mailing list is introduced, visitors should understand what messages they will receive and how to unsubscribe. If account functionality is introduced, passwords should be handled through a secure authentication system and never stored in plain text. This policy will be updated to reflect actual changes, and optional features should not be enabled until their privacy and security implications have been reviewed.