Privacy Policy

01

Information we process

The public FCC website is primarily an information and community website. Most pages can be viewed without creating an account or giving FCC your name or email address.

Information may be processed when you choose to interact with particular features, such as reading or liking a Shekhem Mekazin article, using an authorized editor account, receiving an editor invitation or contacting FCC through our published communication channels.

02

Shekhem Mekazin reader engagement

Shekhem Mekazin uses a randomly generated browser identifier to provide article view and like statistics.

The identifier is stored in your browser using local storage under the namefcc-mekazin-visitor-id. When you read or like an article, the article identifier and this random browser identifier are sent to the FCC Mekazin statistics service.

The public article page does not send your name or email address with these engagement requests. The identifier helps avoid repeatedly counting the same browser as a new view for the same article during the same day and helps remember whether that browser liked an article.

If browser storage is unavailable, the website can use a temporary identifier for the current page session instead.

03

Authorized editor accounts

FCC provides a restricted editorial system for authorized people who help manage Shekhem Mekazin and selected website content.

Editor account information may include a Google email address, display name, profile image, Google account identifier, assigned role, account status, login information and records of authorized editorial or administrative actions.

Google sign-in is used to authenticate approved editor accounts. FCC requests the basicopenid, email andprofile information required for this sign-in process.

Invitation records may also contain an invited email address, role, invitation status and expiration information.

04

Cookies & browser storage

FCC does not currently use advertising cookies or advertising-profile tracking on this website.

05

Third-party services

FCC uses a limited number of external services to provide website and church functions.

If you follow a link to another website or use an embedded third-party service, that provider may process information according to its own privacy practices.

06

Security

FCC uses technical safeguards appropriate to the website's functions. Editor access is restricted to authorized accounts and protected through Google authentication, role-based permissions and authenticated sessions.

Editor session tokens are not stored directly in the editor database. A cryptographic hash of the session token is stored instead.

No website or online service can guarantee absolute security, but FCC aims to limit access to information and administrative functions to people who need that access.

07

Data retention

Editor login sessions are configured to expire after seven days. Editor invitations are also configured with a seven-day expiration period.

Editor account records, publishing records, audit history and related administrative information may be retained for as long as reasonably needed to operate the editorial system, maintain publishing history, manage access and protect the website.

Mekazin reader engagement records may be kept to maintain article view and like statistics.

08

Your choices

You can remove the Mekazin reader identifier from your browser by clearing local storage or website data for the FCC website. A new random identifier may be created the next time you use a Mekazin article engagement feature.

You may also choose not to interact with third-party embedded content and instead use other FCC communication channels.

If you have questions about information associated with an FCC editor account or other information you have provided to FCC, please contact us.

09

Changes to this policy

FCC may update this Privacy Policy when the website, its services or privacy practices change. The latest version will be published on this page with an updated date.