Protect Your Privacy: Understand Our Data Practices Clearly

Introduction and Last Updated Date

Last Updated: October 24, 2023

Standard digital privacy frameworks often obscure the mechanical realities of data collection behind legal boilerplate. The GeoConvention archive requires a different approach. Operating as a repository for the Canadian Society of Petroleum Geologists (CSPG) and allied organizations, this platform processes technical proceedings, abstracts, and user interactions daily. This policy outlines the specific data protection framework governing these operations under Canadian federal and Albertan provincial law.

We define organizational roles for privacy compliance directly alongside our technical infrastructure. Users accessing the GeoConvention Proceedings need absolute clarity on what information transmits during their session. This document maps the exact flow of user data from initial request to final deletion.

External Services Used to Operate the Archive

Delivering high-resolution geological models and extensive seismic datasets requires distributed infrastructure. We rely on specific external services to maintain archive availability and speed. Content delivery networks (CDNs) cache static assets closer to your geographic location. When you download a paper on Reservoir Characterization, the request routes through these third-party nodes.

Analytics platforms currently monitor aggregate traffic patterns to identify which archival sections receive the most academic interest. We plan future integrations with specialized ad networks to support the ongoing hosting costs of the repository. These external providers operate under strict data processing agreements. A partnership sustained across multiple grant periods ensures our hosting providers align with our conservative data retention requirements.

Data We Collect

Minimizing data capture at the server level reduces security liabilities. We log only the metrics necessary to maintain network integrity and deliver requested files. Server logs automatically record incoming IP addresses, user agent strings, referring URLs, and precise timestamps for every HTTP request.

While IP masking techniques reduce identifiability, complete anonymization of server-level routing data remains technically impossible during active session transmission. The network must know where to send the requested packets.

Information submitted through contact forms or newsletter subscriptions enters a separate, isolated database. We collect names, institutional affiliations, and email addresses only when users actively initiate a research subscription or submit an inquiry to the Scientific Committee. This active-consent model ensures we hold personal identifiers only for users who explicitly request ongoing communication.

Cookies and Tracking

Web browsers utilize small text files to maintain state across stateless HTTP connections. We deploy essential cookies strictly to preserve site functionality and store your consent preferences. Without these foundational tokens, basic navigation through complex directories like Stratigraphy & Sedimentology would fail upon every page load.

Analytics cookies operate alongside these essential files. They track user behavior, measuring time spent on specific abstracts and mapping navigation paths through the archive. This data presentation reveals how researchers actually utilize the repository, though it leaves open the question of whether interface design or content quality drives specific engagement metrics.

You can manage or disable all non-essential cookies directly within your browser settings. Modern browsers offer granular controls to block third-party trackers while permitting the essential first-party cookies required for site operation.

How We Use Collected Information

Raw server data holds little value without structured interpretation. We process collected information to enhance site user experience and optimize database query speeds. Analyzing aggregate traffic allows our engineering team to allocate server resources efficiently during peak conference seasons.

We measure analytics and performance to identify broken links, slow-loading assets, and popular research topics. If a sudden surge of traffic hits the Unconventional Resources section, our systems automatically scale to meet the demand based on historical data patterns.

Information provided via direct communication channels serves a singular purpose: responding to inquiries. We do not cross-reference contact form submissions with anonymous server logs. The data remains siloed to guarantee optimal security for user communications.

Your Privacy Rights and Requests

Data subjects maintain absolute authority over their personal information within our systems. You hold the right to request full access to any personal data we currently store. This includes subscription details, communication histories, and associated metadata—all compiled into a readable format.

You may mandate the deletion of your records at any time. Upon receiving a verified request, our database administrators execute a hard delete, purging your information from active servers and initiating the overwrite process on backup drives. Users also retain the right to opt-out of all non-essential tracking mechanisms.

Direct all data-related inquiries to our compliance team via the Contact page. We process these requests systematically to ensure proven compliance with regional privacy legislation.

Retention Periods and Deletion Routines

Indefinite data storage creates unnecessary risk. We enforce strict retention periods based on the classification of the information. Standard server logs, which contain IP addresses and routing data, undergo automatic deletion after roughly 90 days. This window provides sufficient time for security audits and traffic analysis without building a permanent behavioral profile.

Newsletter subscriptions and contact records remain active only as long as the user engages with the communications. We implement automated deletion routines that purge inactive subscriber data after about 24 months of zero engagement. Certified database scripts run these purges weekly, ensuring no orphaned data persists on the primary servers.

Policy Updates

Digital privacy legislation and technical infrastructure evolve rapidly. We update this policy to reflect changes in our data processing capabilities, external service integrations, or legal obligations. When material changes occur, we post a prominent notification on the homepage and update the revision date at the top of this document.

Users subscribed to our mailing list receive direct email notifications regarding significant shifts in data handling procedures. We encourage regular review of this framework to maintain a clear understanding of your digital footprint on the platform. Compliance operations align directly with the Personal Information Protection and Electronic Documents Act (PIPEDA) and Alberta’s Personal Information Protection Act (PIPA), which set an organizational response window of 30 days for formal data access requests. If you want to test that timeline, submit an access request through the Contact page and note the acknowledgment date—our compliance team logs each request against that statutory clock.