Cookies Policy

1. Where this policy applies

GodwinElijah.com is the parent website for custom development services and digital product workspaces. A visit to an informational page, signing into an account, uploading a file, making a payment, and using a tool involve different browser functions. The technologies used depend on the page and service you choose. This policy covers the parent website and Godwin Elijah workspaces; independent websites reached through external links publish their own notices.

A shared account may involve more than one subdomain. Browser rules can limit which domains can read a cookie. Where a workspace needs to recognize your account, it uses the authentication method configured for that service rather than giving every workspace unrestricted access to every browser-stored item.

2. Cookies and similar technologies

A cookie is a small piece of data that a website asks your browser to store and send back on later requests. Session cookies normally disappear when a browsing session ends; persistent cookies remain until they expire or are deleted. First-party cookies belong to the domain you are visiting, while a third party may set its own cookie through content or a service it provides.

Browsers also offer local storage and session storage. These can hold settings or account-related information without being sent automatically with every page request. The same privacy questions can arise when a page uses embedded content, pixels, or other technologies to access information on a device. This policy refers to them collectively as browser technologies where the distinction does not change the explanation.

3. Essential service functions

Essential browser technologies support functions you request, such as keeping an account signed in, maintaining a secure session, navigating between workspace steps, remembering a transaction or project state, and protecting forms or accounts from misuse. A payment flow may rely on the payment provider's own session and fraud-prevention technologies. Without the relevant essential technology, sign-in, checkout, or a tool workflow may not function correctly.

“Essential” is a purpose-based description. It does not mean that every technology used by a provider is automatically exempt from consent requirements. Each use must be assessed according to its actual function and the law that applies to the visitor.

4. Preferences and workspace continuity

A workspace can store a choice such as a selected output format, display setting, or an unfinished step so you can continue your task. Whether a preference is essential depends on why it is stored and how the service works. Preferences that are merely convenient should not be treated as essential solely because they improve the experience.

Deleting browser storage can remove saved settings or interrupt a draft in progress. Keep your own copy of important source files and download completed outputs that you need to retain.

5. Measurement and analytics

Technical logs can record requests, errors, and performance without using a browser cookie. Analytics technologies, where used, can help understand which pages or tool steps are used and where problems occur. The data involved may include a browser identifier, device information, approximate location inferred from an IP address, page visits, or events within a workspace. Information from a project brief, CV, manuscript, invoice, or uploaded file is not described here as ordinary analytics data.

Whether analytics need consent depends on the technology, purpose, configuration, and applicable law. Analytics that require consent must not be activated for a visitor before the required choice is obtained. A visitor's refusal of optional measurement should not block essential access to a service.

6. Advertising and optional tracking

Advertising pixels, cross-site identifiers, and similar tools can track activity across websites or help measure or personalize advertisements. They are distinct from the technologies required to complete your requested task. If used, their purpose and provider must be explained at the point where a visitor is asked to choose, and any consent required by law must be obtained before they operate.

Using a Godwin Elijah workspace does not itself grant permission for unrelated advertising tracking. Refusing optional tracking does not cancel an account or a paid service.

7. Providers and embedded services

Identity, payment, hosting, email, font, media, and processing providers can receive technical information when their services are used. Supabase supports account and backend functions, while Stripe processes payments. A provider may use its own browser technologies for authentication, checkout, security, or fraud prevention under its applicable terms and notices. The provider and technology involved depend on the feature you use.

Loading a font or other external resource can send a request to its provider, including technical information such as an IP address, even where it does not set a browser cookie. An embedded video or external payment page may involve additional storage or access by that provider. Follow the linked provider notice for its independent processing, and see the Privacy Policy for broader data-sharing information.

8. Your choices and browser controls

Where optional browser technologies require consent, you can accept or decline them through the choice presented for the relevant service. You may withdraw a previous consent for future use through the available preference control or by contacting dev@godwinelijah.com. Withdrawal does not undo processing that was lawful before it was made.

Most browsers let you inspect, block, or delete cookies and site data. Browser menus vary, but these controls are generally found under privacy, security, or site settings. Blocking all cookies can prevent account sign-in, payment, or saved workspace steps from working. Private browsing can limit how long some browser data is kept on your device, but it does not prevent all server logs or provider requests.

A browser's general permission to accept cookies is not, by itself, a substitute for consent where the law requires a specific informed choice. The same applies to simply continuing to browse.

9. Duration and changes

The lifetime of a browser technology depends on its function and the provider that sets it. A session identifier, remembered preference, and payment security token need not have the same duration. Deleting a cookie in your browser removes that browser copy; it does not necessarily delete an account, project record, transaction, or server log. Requests about personal information are addressed in the Privacy Policy.

This policy is updated when the technologies or their purposes materially change. The current version appears at this address with its updated date. If a new optional purpose requires consent, the relevant choice must be obtained before that purpose begins.

10. Questions about browser technologies

For a question about a cookie, browser storage, an optional choice, or the way a particular workspace handles these technologies, email dev@godwinelijah.com or use the Support page. Include the page or workspace involved and, if possible, the name of the technology shown in your browser. Do not send a password, payment card number, or full sensitive document with an initial inquiry.