Tracking Technologies Documentation
Documentation Current as of March 2025
What This Document Addresses
polaryntiva places small data files on devices accessing polaryntiva.com. These files enable specific functions that make spreadsheet financial management tools work properly. This documentation explains which technologies we deploy, their operational purposes, and what control mechanisms exist for visitors.
Understanding these mechanisms matters because they affect how your browser communicates with our servers and remembers your preferences across sessions.
Technology Categories We Deploy
Session Identifiers: Temporary markers that exist only while your browser remains open. They vanish when you close the browser entirely. We use these to maintain your position within the platform as you navigate between spreadsheet templates and calculation tools.
Operational Storage
Files essential to core functionality. Without these, the financial management interface cannot remember which spreadsheet you're editing or maintain calculation states between page loads.
Preference Memory
Records choices you've made about interface display, currency formats, and notification settings. These persist between visits so you don't reconfigure the system each time.
Performance Monitoring
Tracks which calculation engines load slowly or which spreadsheet templates cause browser performance issues. This helps us identify technical problems affecting user experience.
Usage Patterns
Anonymous data about which features get used most frequently. Shows us whether people actually use the budget forecasting tools or prefer the expense tracking templates.
Third-Party Technology Sources
Some tracking mechanisms originate from external services we integrate. Analytics platforms and hosting infrastructure providers place their own identifiers. We selected these services because they provide capabilities we can't build internally, but they operate under their own data practices.
Operational Purposes Explained
Each technology type serves distinct functional needs. Here's what actually happens with the data collected.
Authentication and Access
When you log into your account, a session identifier gets stored. This tells our servers you've already authenticated, so you don't need to re-enter credentials every time you click a different spreadsheet template. The identifier contains a randomly generated string — nothing about your actual identity or activities.
Interface Customization
If you adjust date formats from DD/MM/YYYY to MM/DD/YYYY, or change currency display preferences, we store that choice. Otherwise you'd set these options repeatedly. Same applies to notification preferences about calculation updates or shared spreadsheet modifications.
Technical Performance Assessment
We measure how long complex financial calculations take to process. Which browser versions handle large datasets efficiently? Where do users encounter errors when importing transaction data? This information identifies optimization priorities and compatibility problems.
Feature Development Priorities
Anonymous usage metrics show which templates get downloaded most often, which calculation tools rarely get used, and where people abandon the interface. This guides decisions about what to improve versus what to deprecate.
Data Lifecycle and Retention
Initial Placement
When you first visit polaryntiva.com, your browser receives operational files necessary for the platform to function. Session identifiers get created. If you interact with preference settings, those choices get recorded.
Active Usage Period
During your session, temporary identifiers track your navigation through different spreadsheet tools. Performance metrics collect timing data. Preference files remain dormant unless you modify settings.
Session Conclusion
When you close your browser, session identifiers expire immediately. Preference storage remains on your device. Performance data gets transmitted to analytics systems where it's aggregated with data from other users.
Long-Term Storage
Preference files persist for up to 12 months. Performance metrics stay in analytics systems for 24 months before automated deletion. Individual session data doesn't exist beyond the active session — only aggregated statistics remain.
User Experience With and Without Tracking
| Platform Feature | With Full Tracking | With Tracking Disabled |
|---|---|---|
| Account Login Sessions | Maintains authentication across the entire platform without repeated login prompts | Requires re-authentication frequently, possibly for each major section accessed |
| Interface Preferences | Remembers currency formats, date displays, notification settings between visits | Resets to default settings each session — customization must be repeated |
| Spreadsheet State | Preserves which template you were working on, unsaved calculation states, current position | Loses context when navigating away — starts fresh each time |
| Performance Optimization | Platform learns which features need improvement based on actual usage patterns | Development team works without real usage data, potentially optimizing wrong areas |
| Error Diagnostics | Technical issues get logged with context about what actions preceded the problem | Errors occur but we can't determine patterns or causes — harder to fix systematically |
Control Mechanisms Available
Several methods exist for managing these tracking technologies. Effectiveness varies by approach.
- Browser settings contain sections specifically for managing stored data. Look for "Privacy" or "Security" settings where you can view, block, or delete files by polaryntiva. This affects all sites you visit, not just polaryntiva.com.
- Browser extensions exist specifically for tracking management. These tools provide more granular control than native browser settings but require installation and configuration.
- Private or incognito browsing modes prevent storage of most persistent data. Session identifiers still function during the private session but everything clears when you close the window.
- Browser "Do Not Track" signals indicate preference against tracking, but websites aren't legally obligated to honor them in Australia. polaryntiva respects these signals for non-essential tracking but operational files remain necessary for platform function.
- Regular browser cache clearing removes accumulated data files. This can be automated to occur daily, weekly, or at custom intervals through browser settings.
Consequences of Comprehensive Blocking
If you block all tracking technologies completely, you can still access polaryntiva.com's public content and educational resources. However, account-based features won't function properly. The platform won't remember your login state, spreadsheet templates won't save your work between sessions, and preference settings will reset constantly.
You essentially get a read-only experience of public materials without the ability to use interactive financial management tools.
Updates and Modifications
This documentation reflects our practices as of March 2025. When we deploy new tracking technologies or modify existing ones, this document gets updated. We don't notify users individually about documentation changes — it's your responsibility to check periodically if this matters to you.
Substantial changes to tracking practices get announced through the platform's notification system for logged-in users. Public visitors only see updates reflected in this documentation.
Documentation Inquiries
Questions about these tracking practices or requests for clarification about specific technologies can be directed to polaryntiva through these channels.
Response timing for documentation inquiries typically ranges from 2-5 business days depending on complexity. Technical questions about specific tracking mechanisms may require consultation with our development team before we can provide detailed answers.