Cookies Policy

What cookies and browser storage do

Cookies are small pieces of information stored by your browser and sent with applicable requests. Local storage and similar technologies can retain information on your device. FOFA uses Supabase authentication to keep authorised users signed in and complete account verification.

Storage currently used

Authentication cookies commonly use a project-specific name beginning with sb- and ending in -auth-token, sometimes split into numbered chunks. Account verification can also use a temporary PKCE code-verifier cookie. Exact names and lifetime depend on the Supabase version, project, and authentication flow.

These first-party cookies support session persistence, authentication token refresh, and account-setup redirects. Persistent authentication cookies can outlast a browser session until sign-out, expiry, or clearing site data. The installed Supabase SSR library defaults its cookie maximum age to 400 days, although token validity and actual cookie lifetime can be shorter. Signing out clears the app’s session cookies; the server may retain separate account and security records.

The fofa-locale first-party preference cookie remembers the language you choose for up to one year. Signed-in users can also save their language and in-app reminder preferences in their account.

The fofa-accessibility-v1 local-storage entry remembers your display, reading and navigation preferences in this browser. It contains no account identifier or tracking data. Reset accessibility settings removes the entry; clearing browser site data also removes it.

The current source does not set analytics, marketing, advertising, or social-media cookies. Fonts are served by the app rather than fetched from Google Fonts. Portfolio access to S3 and optional server-side Gemini requests are described in the Privacy Policy; their existence alone does not mean the browser sets tracking cookies.

Do you need to accept cookies?

There is no optional tracking-cookie category to accept or reject in the current app, so it does not show an “Accept all” banner. Authentication storage is used when you use account features; blocking it can prevent sign-in or account setup.

This is a description of the technical implementation, not a conclusion that all personal-data processing is exempt from consent under Egyptian law. The institution must establish the applicable legal ground for authentication processing. Optional AI processing has a separate opt-in and is not covered by an authentication-cookie notice.

If analytics, advertising, embedded services, or other non-essential storage are introduced, this inventory and the consent assessment must be reviewed before those technologies load. Where prior permission is required, optional technologies must remain disabled until an informed choice is made, and withdrawal must be as easy as acceptance.

Your browser controls

You can sign out, delete this site’s cookies and local storage, or block cookies through your browser’s privacy settings. Clearing storage signs you out and may interrupt account verification. It does not delete academic or training records held on the server.

Shared-device users should sign out when finished. Contact the training team if you need an accessible alternative to a browser setting or have a question about an unfamiliar cookie.

Policy review

The operator should recheck live cookies after authentication-provider, hosting, or frontend changes. No claim is made about unrelated browser extensions, the institution’s other websites, or services outside this portal.

Contact the training team

Faculty of Fine Arts, Capital University (formerly Helwan University)
Arab Republic of Egypt
training.program.help@gmail.com