Privacy policy

Who we are

Talvess is operated by Aditya Ojha. This policy covers our website, analytics dashboard, and the data received through Talvess integrations. Contact us at adityakodez@gmail.com.

For your Talvess account and our own website, we decide how information is used. For analytics collected on a customer's website, that website owner decides why the information is collected and we process it to provide their reports. Visitors should also read that website's privacy notice.

Your account and support messages

When you use Talvess, we may process:

• Your name, email address, profile image, and account identifiers supplied by Google or GitHub when you sign in.
• Authentication tokens, session information, and sign-in timestamps. Account sessions may include your IP address and browser user agent for authentication and security.
• The website addresses, display names, settings, saved funnels, and integrations you add to your workspace.
• Your email address and anything you choose to include when you contact support.

We need account information to provide a signed-in workspace. If you do not provide it through a supported sign-in provider, you can still browse our public pages and demo but cannot use a private workspace.

Data collected by the website tracker

When a website installs Talvess, the tracker collects page pathnames, pageview timestamps, random visitor and session identifiers, and approximate active time on a page. It also collects an external referrer's hostname and the landing URL's UTM source, medium, and campaign values when present.

The collector reads the request's user agent to estimate the browser, operating system, and device category. Our hosting provider may supply country, region, city, and approximate coordinates derived from the request's IP address. These are approximate network locations, not precise device locations. Supported browsers also send performance measurements for loading, responsiveness, and layout stability.

The standard tracker does not send page contents, form inputs, a full referrer URL, a full query string, or URL fragments. Talvess does not store visitor IP addresses in its analytics records. Network requests still reach our hosting provider, which can process IP addresses and request information to deliver and protect the service.

Pathnames and campaign values can contain information a website owner puts there. Do not include names, emails, secrets, or other sensitive information in tracked paths or campaign tags.

Signup events and optional integrations

A customer can send a server-confirmed signup or another named event. We store the event name, its opaque event identifier, occurrence and receipt times, and any supplied visitor/session context. This API does not accept customer profile fields or arbitrary event metadata. Event identifiers should not contain personal information.

When a customer enables cross-site signup handoff, random tracking identifiers can pass from their website to their signup application through a URL parameter. The optional helper removes the parameter when it reads it and keeps the context in that tab's session storage. The customer controls whether to enable this integration.

If you connect GitHub deployment tracking, we process authorized installation and repository identifiers, repository names, deployment details, commit references, and integration credentials needed to display and sync deployments. Disconnecting stops new deployment collection; existing records remain until the website is deleted.

Cookies and browser storage

The website analytics tracker uses no cookies. It saves a random visitor identifier in the tracked website's first-party local storage and visit information in session storage. Visits expire after 30 minutes of inactivity. The local visitor identifier remains until that site's storage is cleared or becomes unavailable; clearing it does not delete records already received by Talvess.

The Talvess application uses cookies for account authentication and sign-in state. Interface preferences, such as your theme, may also be stored in your browser. Our own production website uses the Talvess tracker described above.

Cookieless does not mean storage-free or automatically exempt from consent requirements. Website owners must provide the notices and obtain permissions required for their use of analytics and browser storage. You can manage cookies and site storage through your browser.

Why we use information

We use information to run accounts, provide analytics and integrations, answer support requests, troubleshoot problems, secure the service, prevent abuse, and meet legal obligations. We do not use customer visitor data to build advertising profiles or sell that data.

Where a legal basis is required, account administration supports the service you request, security and support serve our legitimate interests in operating it, and compliance processing meets applicable legal obligations. Website owners are responsible for the legal basis and any required consent for analytics they collect from visitors.

Service providers and disclosure

• Vercel hosts the application and handles network requests and operational logs.
• Neon provides the Postgres database used to store account and analytics records.
• Google and GitHub provide sign-in. GitHub also supplies data for deployment integrations you connect. Support messages sent to our Gmail address are handled by Google.
• Your browser may request profile images and website favicons from their original hosts. To display icons for referring websites, your browser may also request their domains from Google's favicon service.

These providers may process information in countries other than your own. Their terms and privacy information describe their handling and transfer arrangements. Contact us for questions about the providers used for your data.

Workspace analytics are available to the account that owns the website. The public demo displays analytics from Talvess's own website; it does not make customer workspaces public. We may also disclose information when required by law or necessary to investigate abuse and protect the service.

Retention and deletion

Account records are kept while your account remains open. Website analytics, server events, saved funnels, and deployment records remain in your workspace until you delete the website or request account deletion. There is currently no automatic age-based deletion of these website records. The date ranges in reports and attribution windows are calculation rules, not deletion schedules.

Deleting a website removes its associated records from the active application database. Removing the tracking script, revoking a server key, disconnecting an integration, or signing out does not delete previously collected data. Account deletion is handled by email; we verify the request before removing account and website records.

Support correspondence and limited operational records may be kept as needed to resolve requests, investigate security issues, or meet legal obligations. Provider backups and logs can retain copies after active records are removed and expire under the provider's retention processes. Contact us if you need details for a deletion request.

Your choices and privacy requests

Depending on the law that applies, you may request access, correction, deletion, a copy of your data, or restrictions on its use. You may also object to processing or withdraw consent where processing depends on consent. Contact adityakodez@gmail.com from the email connected to your account where possible. We may need enough information to verify your request, and we respond within the time required by applicable law.

If you visited a customer's website, contact that website owner first so they can identify the relevant website and data. You can also contact us for help routing the request. You may raise a concern with the data protection authority in your jurisdiction.

See Support for account deletion instructions. Never send passwords, server keys, OAuth tokens, or sensitive visitor information in a support message.

Changes to this policy

We update this page when our data handling changes and revise the date above. Where applicable law requires additional notice, we provide it. Contact us if you have a question about this policy.