Published document.
Version: 2026-10-04.4 · Effective: 2026-10-04
1. Data controller
The data controller is Seeft di Bufarini Simone, an Italian sole proprietorship with registered office at Via Ponte Pio 6, 60035 Jesi (AN), Italy, VAT number 02983090420, Business Register/REA number AN-297752 (“Seeft” or the “Controller”).
Privacy contacts:
- email: privacy@seeft.io;
- certified email (PEC): simone.bufarini@pec.it.
The Controller has not appointed a data protection officer (DPO). Privacy requests may be sent to the contacts above.
2. Scope of this notice
This notice is provided under Articles 12–14 of Regulation (EU) 2016/679 (“GDPR”). It applies to seeft.io, www.seeft.io, tools.seeft.io and accounts.seeft.io, including tools, accounts, contact forms, suggestions and related features. Seeft Accounts, available at accounts.seeft.io, manages accounts and access to Seeft services, including the Google sign-in described in section 7.1. Third-party websites and services reached through links apply their own notices.
3. Personal data processed
Depending on the features used, Seeft processes:
- technical and security data: IP address, date and time, requested URL, user-agent, application logs, device information and data needed to prevent abuse;
- account data: name, email, image, OAuth provider and identifier, preferences, role, plan, last sign-in date, sessions and technical authentication tokens;
- account usage data: favorite tools, votes, saved transformation configurations, execution counts and dates;
- tool suggestions: title, descriptions of the problem, current process, expected input and output, frequency, potential audience, external services and the declared data-sensitivity level;
- communications: name, email, company, budget range, project type and contact-form message; for emails sent by Seeft, content and technical metadata about sending, delivery and any errors;
- optional analytics events: pages, referrer, approximate location, browser, operating system and device data, and allowlisted product events;
- optional diagnostic data: errors, stack traces, performance information, technical context and masked session replays;
- privacy choices: random consent identifier, action, accepted and rejected categories and services, language, hostname, policy versions, banner revision and date; for signed-in users, the internal account identifier may also be associated.
Seeft does not use personal data for behavioral advertising and does not sell personal data. It does not combine activity across devices for profiling.
4. Purposes, legal bases and retention
| Processing | Purpose | Legal basis | Intended retention |
|---|---|---|---|
| Website delivery, technical logs and security | Deliver pages and APIs, prevent abuse, investigate incidents and protect systems and users | Performance of the requested service; Controller’s legitimate interest in security (GDPR Art. 6(1)(b) and (f)) | Routine logs for the period configured with the host and no longer than 90 days; longer only where required for an incident or legal claim |
| Account and OAuth sign-in | Create the account, authenticate the user, maintain sessions and administer access and roles | Contract or steps requested by the user (Art. 6(1)(b)) | For the life of the account; sessions until expiry, normally 30 days; deletion on request unless retention is required by law or for a dispute |
| Favorites, votes and saved transformations | Provide user-requested account features | Contract (Art. 6(1)(b)) | Until deleted by the user or the account is deleted |
| Suggestions and roadmap | Review suggestions, send status updates and, if approved, publish a non-personal summary | Requested service (Art. 6(1)(b)); legitimate interest in managing and documenting the roadmap (Art. 6(1)(f)) | During review and for up to 24 months after closure; published summaries may remain without a link to the author |
| Contact form | Respond to information or commercial enquiries | Pre-contractual steps requested by the person (Art. 6(1)(b)) or legitimate interest in handling general communications (Art. 6(1)(f)) | Up to 24 months after the last communication, unless a contract or legal claim requires longer retention |
| Suggestion status emails | Send requested operational communications | Performance of the service (Art. 6(1)(b)) | Until the preference is disabled or the account is deleted |
| Email sending and Resend delivery logs | Deliver requested communications and handle sending and delivery errors, without measuring opens or clicks | Performance of the service for operational emails (Art. 6(1)(b)); consent for optional updates (Art. 6(1)(a)); legitimate interest in sending security and reliability for technical logs (Art. 6(1)(f)) | Email and log data for 30 days on the Free plan, according to the vendor’s documentation |
| Non-essential product updates | Send optional communications | Consent (Art. 6(1)(a)) | Until withdrawal; evidence follows the consent-register period; Resend email and log data for 30 days |
| Umami and first-party product analytics in the browser | Measure usage, journeys and feature adoption to improve the service | Consent (Art. 6(1)(a) GDPR and applicable ePrivacy rules) | Local identifier for 182 days; Umami Cloud retention to be confirmed with the vendor, with a target maximum of 13 months; Seeft events deleted or aggregated within 13 months |
| Browser-side Sentry and masked replay | Detect client-side errors and performance problems | Consent (Art. 6(1)(a) GDPR and applicable ePrivacy rules) | 30 days, according to the Sentry project configuration |
| Server-side Sentry | Diagnose backend errors without reading or writing identifiers on the user’s device | Legitimate interest in service security and reliability (Art. 6(1)(f)) | 30 days, according to the Sentry project configuration |
| Privacy-choice register | Record choices, changes and withdrawals and demonstrate compliance | Legal obligation and legitimate interest in defending claims (Art. 6(1)(c) and (f); Art. 7(1) GDPR) | Five years from the event, unless required for pending proceedings |
| Administrative audit trail | Trace privileged operations and investigate abuse | Legitimate interest in security and accountability (Art. 6(1)(f)) | 24 months, unless needed for an incident or dispute |
Where processing relies on legitimate interests, Seeft applies minimization, access restrictions and limited retention. You may ask for information about the balancing assessment and object on grounds relating to your particular situation.
For data stored directly by Seeft, the Controller manages retention deadlines through periodic checks and manual deletion or irreversible anonymization. Not every processing operation has automatic deletion. Checks are organized to meet the deadlines in the table; the interval between checks does not create an additional retention period. Any extension for legal obligations or the defense of rights applies only to necessary data and lasts only as long as justified by those needs.
Deletion from active systems is separate from the expiry of vendor-managed technical backups and restore history. For Neon, the maximum time data may remain in technical copies is not yet confirmed. If data is restored, Seeft reapplies the necessary deletions before putting it back into use.
According to Resend’s documentation, the Free plan retains email and log data for 30 days while the service account is active; backups persist for 7 days and remaining customer data is deleted within 90 days of closing the Resend account. These periods do not replace the periods applying to communications that Seeft may retain in its own email inbox.
5. Locally processed tools
Tools marked as “local” process inputs, files and outputs in the browser. Their content is not intentionally sent to Seeft. Data remains under the user’s and device’s control, however, and browser extensions, local software or networks not managed by Seeft may have independent access.
Do not enter personal, health or criminal-offence data, credentials, secrets or third-party data unless you have a lawful basis and appropriate safeguards. If a future feature requires cloud processing, that fact must be disclosed before upload.
6. Required and optional data
Fields marked as required are needed to provide the requested feature. Without them, that feature cannot be provided, but public tools that do not require an account remain available. Analytics, browser diagnostics and product updates are optional; refusing them does not restrict essential features.
7. Sources
Data comes from the user, the device and interactions with the service. When the user signs in, Google or GitHub provides the profile data authorized by the user. If a suggestion is published, its summary is derived from the submission but is managed separately from the author’s identifying data.
7.1 Google sign-in through Seeft Accounts
Google policies. Seeft uses information received from Google APIs in accordance with the Google API Services User Data Policy, including applicable Limited Use requirements.
Data and permissions requested. When you choose “Sign in with Google”, Seeft Accounts requests the openid, email and profile permissions. Google provides your unique account identifier (sub), name, email address, email verification status and, where available, profile picture URL. The flow also receives technical authentication tokens and their expiry and authorization information. Seeft does not receive your Google password. This sign-in does not request permissions to read Gmail, Google Drive files, calendars or contacts.
Use of the data. This data is used to create a Seeft account or link Google to an existing account, recognize you on subsequent sign-ins, display your profile and provide access to the Seeft services you request. Your email may also be used for operational account communications, such as verification, recovery and security codes. The legal basis is performance of the service you request (GDPR Art. 6(1)(b)); authorizing Google does not enable analytics, browser diagnostics or optional product updates. Google data is not sold or used for behavioral advertising.
Storage and protection. Seeft stores your profile, Google identifier and provider connection in the account database. It may store access tokens, refresh tokens where provided, and ID tokens, together with technical connection metadata. The application encrypts access and refresh tokens before storing them in the Accounts database; authentication connections use HTTPS and access to data is restricted. Token expiry limits its validity but does not imply immediate deletion of its database row. The Google connection and associated tokens are removed from active systems when you unlink the provider or your account is deleted. Profile data already held in your Seeft account remains for the life of that account even after unlinking. The periods and any exceptions in section 4 apply, including the information about backup copies.
Recipients and connected services. When you access a connected Seeft service, Seeft Accounts may provide that service with your Seeft identifier, name, email, verification status and profile picture, according to the permissions requested, together with technical information needed to manage access. Google tokens are not forwarded to these services as sign-in credentials: Seeft Accounts issues its own credentials. Vercel and Neon provide hosting and storage; for operational emails, Resend receives your email address and, where included in the message, your name. Staff access and other recipients are limited to the cases described in section 8; international transfers are described in section 9.
Unlinking, revocation and deletion. You can unlink Google on the Seeft Accounts connected providers page, while keeping another sign-in method available. You can also revoke authorization through your Google Account connections to third-party services. Revocation on Google ends the authorization you granted; a subsequent Google sign-in may require new authorization. It does not automatically delete your Seeft account, previously collected data or existing Seeft sessions. To request deletion of your account and data, email privacy@seeft.io; procedures, rights and exceptions are described in sections 4 and 11.
8. Recipients and vendors
Authorized personnel and contractors access data only where necessary. The following parties may also process it, depending on the feature used:
| Vendor | Function and indicative role | Main area/configuration |
|---|---|---|
| Vercel | Hosting, CDN and server functions; processor for service data | Functions configured in Frankfurt (fra1), with potentially international infrastructure and support |
| Neon | PostgreSQL database; processor | Project intended/configured in Frankfurt |
| Google and GitHub | OAuth providers; independent controllers for their accounts and processors or recipients for the authentication flow | Global infrastructure |
| Resend | Email delivery and delivery metadata; processor for data sent by Seeft | United States and the vendor’s listed subprocessors |
| Umami Software, Inc. | Umami Cloud analytics, Hobby plan; processor | EU account region |
| Functional Software, Inc. (Sentry) | Error, performance and replay monitoring, Developer plan; processor | EU data region, using the Germany ingestion endpoint (ingest.de.sentry.io) |
OAuth providers also apply their own notices: Google and GitHub. Vendor documents include Vercel, Neon, Resend, Umami and Sentry.
For Seeft’s email domain, Resend click tracking and open tracking are disabled. Seeft does not insert pixels to measure opens or replace links with redirects intended to measure clicks. Technical metadata needed for sending and delivery remains. Consent through the website banner does not automatically authorize any future email tracking, which would require a separate assessment and, where necessary, specific consent.
Seeft may also disclose data to public authorities, advisers or counterparties where required by law or to establish, exercise or defend rights. Data is not made public except for roadmap summaries intentionally published without the author’s identifying data.
9. Transfers outside the European Economic Area
Some vendors or their subprocessors are established or operate outside the EEA. Where applicable, transfers must rely on an adequacy decision, including the EU–US Data Privacy Framework for certified recipients, or the European Commission’s Standard Contractual Clauses and any necessary supplementary measures. You may request information or a copy of the relevant safeguards from the Controller.
The Umami account is in the EU region and the Sentry project uses the EU data region. Selecting an EU region does not, by itself, exclude access or processing outside the EEA by a vendor or its subprocessors.
10. Consent and privacy choices
Optional technologies remain disabled on the first visit. Users may accept all, reject all or select individual services. Closing the banner rejects optional technologies. Choices may be changed or withdrawn at any time through “Cookie preferences” in the footer. Withdrawal does not affect the lawfulness of earlier processing.
The individual technologies are described in the Cookie policy.
11. Data subject rights
Where Articles 15–22 GDPR apply, individuals may request access, rectification, erasure, restriction, portability and objection, and may withdraw consent. They may opt out of non-essential communications at any time.
Requests may be sent to the Controller’s contacts. Proportionate information may be requested to verify identity. A response is normally provided within one month, extendable by two months in the complex cases allowed by the GDPR.
You may lodge a complaint with the Italian Data Protection Authority or the authority for your residence, workplace or the place of the alleged infringement, and seek a judicial remedy.
Residents of other jurisdictions may exercise additional rights granted by applicable local law. Seeft does not sell personal information or share it for cross-context behavioral advertising.
12. Children
The service is not directed to children under 14 and Seeft does not knowingly collect their data. In Italy, a person aged 14 or over may consent to data processing for information-society services within the limits of applicable law; this does not give them capacity to enter every contract independently. Users aged 14–17 may use the service to the extent permitted by applicable law; taking an action that requires contractual capacity requires authorization from a parent or legal guardian where required by law. If non-compliant collection is identified, the data will be deleted or restricted.
13. Automated decisions and profiling
Seeft does not make solely automated decisions that produce legal or similarly significant effects. Usage statistics are not used for behavioral advertising or individual scoring.
14. Security
Seeft applies proportionate technical and organizational measures, including authenticated access, administrative roles, minimization, request limits and replay masking. No system is risk-free; any breach will be handled under applicable notification and remediation duties.
15. Changes
The version and effective date appear at the top of this page. Material changes will be communicated by proportionate means. A new choice will be requested when consent-based purposes, categories or services materially change.