YOUR INFORMATION
Learn what information SK ONE uses, why it is used and how it is retained. Your digital mobile-app account and the community’s institutional records serve different purposes.
This policy covers the institutional website and the SK ONE mobile-app account. SK ONE is developed by OBIES TECH S.A., Argentina. Community systems also hold institutional records. Deleting a digital account does not terminate your relationship with the community.
OBIES TECH S.A., CUIT 30-71955734-8, registered address: Av. Roque Sáenz Peña 875 EP 3, CABA (1035), Argentina.
OBIES TECH S.A. is responsible for processing digital-account and website information. Each community’s administering entity is responsible for its roster and institutional records and processes. For these records, OBIES supplies technology under the community’s instructions and agreements. Requests about your digital account are handled separately from institutional requests.
For access, correction or deletion requests concerning your digital account or this website, contact privacidad@skone.com.ar. Technical support: soporte@skone.com.ar. For roster, payments, property relationships or other institutional records, contact your community’s Administration directly.
National ID number, names, date of birth, contact details, communities, properties and profiles. Some information comes from Administration; you supply or verify other information in the app.
Document verification processes front/back images, readable fields and the validation result. These may include sex, nationality, document dates and references. Capture evidence and accepted identity records have different purposes and retention.
Requests, messages, attachments and service states. Depending on enabled features, these include reservations, invitations, admissions, access events and administrative records.
App and system versions, notification identifiers, device-integrity signals and technical events used to operate, protect and diagnose the service.
Location, files and audio are used by features that need them. Processing depends on enabled services and your profile.
Information identifies you, verifies access, links communities, handles requests and delivers services. It also supports communications, service protection and error resolution.
Identification and access verification require the information indicated in each flow. Without it, that service may be unavailable. Optional permissions are requested when used; this notice does not replace specific consent when required.
Login codes respond to an interaction you initiate. App notification preferences are separate from institutional communications. Deleting your digital account does not automatically erase roster contact details or necessary institutional communications.
The minimum age for direct mobile-app use is thirteen. Each community decides whether to enable use at that age or require a higher age, such as sixteen or eighteen. A community cannot set an age below thirteen.
Eligible minors use the app directly. Being present in the roster does not itself authorize access.
Each community defines the responsible-adult authorization requirements for registration and use by minors, within applicable law. This authorization is separate from the minor’s direct use of the app.
Used where documentation or evidence must be captured or attached. You can manage device permissions; denying a permission can make the corresponding feature unavailable.
Each community decides whether to enable geolocation for security company patrols and provider control. When enabled, location records and supervises those operations and may be used in the background while the relevant service is active. Security and Administration may access it according to their duties and permissions. You can manage device location permissions.
Where enabled by your community, location may verify your presence when checking in to a reservation, such as a tennis court. It is requested at check-in and does not require continuous route tracking. Security and Administration may access the relevant information according to permissions.
Notifications deliver enabled service alerts. The microphone is used by voice features when you use them. Permissions can be managed in device settings.
The community’s access-control hardware performs facial recognition. SK ONE integrates the equipment and manages authorizations and access events. Depending on configuration, the integration also handles enrollment photos and data necessary to operate the devices. The purpose is the community’s defined access control; Security and Administration access relevant information according to duties and permissions.
Authorized Administration and other personnel access information required for their duties. Information in a service request reaches those responsible for handling it.
Microsoft Azure provides infrastructure, files and document reading; Apple and Google provide mobile features, notifications and integrity. Enabled features may involve maps, messaging, payments or other technology providers. Processing may take place outside Argentina.
The normal document-reading process uses Microsoft Azure to obtain readable information from images and compare it with the registered identity.
Information may need to be retained or disclosed to meet valid obligations or requests. The scope is limited to information relevant to each case.
Microsoft Clarity website analytics loads after analytics consent. The preference is stored in the browser and can be changed through “Privacy and analytics” in the footer. This is separate from app analytics. Support email information is processed to answer your request.
Retention depends on the information and its purpose. Digital-account deletion does not erase all community records. Unnecessary information is erased or irreversibly anonymized; obligations and justified exceptions are assessed separately.
A valid deletion confirmation closes mobile-app access across all communities and invalidates sessions, codes and links. The account and credentials are deleted, rather than merely disabled. Independent administrative access to community systems is outside this action.
App-only device associations, push tokens, settings, favorites, read states and personalization are deleted. They are not restored when a new account is created.
Personal files, messages and content without an independent institutional purpose are deleted together with applicable references and controlled copies. A community’s shared file is not deleted merely because the user authored it.
Identity and contact information needed for an ongoing community relationship may be retained for that purpose. They do not reactivate the digital account. A person created solely for digital use is not automatically retained without an independent basis.
Deleting the app account does not cancel reservations, requests or procedures, nor erase institutional records that must be retained. Contact your community’s Administration directly about these records.
Verified fields and accepted document history are separate from the photos used to read them. Necessary identity fields follow their institutional purpose; photographs have a different treatment and retention period.
Photos, unsuccessful readings and technical records have limited, differentiated retention. Deletion or redaction covers relevant SK ONE-controlled copies; complete evidence is not retained by default.
A minimal record is retained for five years from resolution to demonstrate handling and prevent improper reactivation. It contains only necessary reference, dates, scope, policy version and outcome, not a full profile or copies of erased data. Its expiry does not reactivate the account; a new explicit registration is required.
The recipient is erased once delivery is confirmed. Otherwise, delivery handling has a maximum of seven days from verified active-data deletion, after which the recipient is erased and private-reference/operational follow-up remains. Failure is not reported as completed deletion.
A specific incident, dispute or valid requirement may justify separate retention of identified records with a documented reason, scope and responsible party. Exceptions are reviewed every ninety days. When lifted, the original expiry applies; already-expired data is erased within thirty days unless a specific obligation applies. The exception does not restart retention or keep the digital account active.
These periods apply to the minimum necessary institutional archive. Account deletion does not restart periods or cancel valid operations. Legal obligations and case-specific exceptions are separate; photos and other sensitive data do not automatically inherit these periods.
Necessary institutional identity and property relationships are kept while active and for ten years after they end. This does not retain the full profile or every image. Occasional visitor, provider and subscriber relationships follow the separate period below.
Necessary facts, decisions and evidence are retained for five years after closure. Unnecessary conversation and attachments do not automatically inherit that period.
The necessary application, decision and evidence are retained during the relationship and for five years after it ends. Sensitive attachments are treated separately.
Minimal actor, date, action and reason are retained for five years from the change. An act supporting a record subject to a specific retention obligation follows that record’s applicable period.
Kept for three years from completion or cancellation. Payment receipts and accounting evidence follow their separate retention rule.
Without another institutional relationship, a minimal record is kept for two years from termination or the last effective authorization. Individual access events and payment records are separate.
Email, phone and address needed for post-termination communications are retained for twelve months from effective termination. An open matter retains only the relevant contact. This does not remove required information already in a historical receipt.
A minimal decision and reason are retained for twelve months from closure where no subsequent institutional relationship exists. Unnecessary additional documents are deleted.
These are ordinary maximum periods for features using this information. Valid account deletion may accelerate erasure of exclusively digital data without an independent basis. Necessary incident evidence is retained separately with a documented reason and scope.
Front/back images and complete readings are retained for at most thirty days from capture, for successful and unsuccessful attempts alike. Necessary accepted identity data are separate.
Retained for at most ninety days from the event. Unnecessary identifying information is minimized, erased or redacted. Irreversibly anonymous metrics cannot reconstruct personal activity.
Ordinary security audit and entry/exit events are retained for at most one hundred eighty days from the event. This does not apply to video or biometric templates. Records serving another institutional purpose are assessed separately.
Precise coordinates and detailed routes are retained for at most seven days from capture. Relevant incident evidence is separated and limited to that case.
Recordings made by enabled features are retained for at most thirty days from capture. Necessary incident or case evidence is separate. This applies to SK ONE-controlled systems and providers subject to the relevant agreements.
Necessary case and solution information is retained for at most two years from closure. Sensitive or unnecessary documents are removed earlier; valid account deletion covers personal information without an independent retention basis.
Operational backups are kept for at most thirty days from creation of each copy. Deleted data temporarily in a backup are excluded from normal use. Deletions are reapplied before a restored service is reopened. Long-term institutional history is kept as a specific archive, not through prolonged full-database backups.
The process covers file versions, recoverable copies and provider data. A deletion marker is not proof of physical deletion. Completion is not confirmed until required actions and evidence are complete; failure does not restore access.
You can request access, correction and, where applicable, deletion or confidential treatment. For your digital account or this website, contact privacidad@skone.com.ar with your name, response channel and request. Identity is verified through an appropriate channel without publishing IDs, codes or third-party data. Contact Administration directly for institutional records.
You can change device permissions and available optional-feature settings, and request withdrawal of consent where processing depends on it. This is separate from processing supported by another applicable basis.
Digital deletion does not automatically resolve requests about institutional records. Contact Administration directly about roster, payments, property relationships and other institutional records. Their responsible entity must explain what is retained, why and for how long.
Rights requests are handled within applicable legal time limits. You may contact Argentina’s Agency for Access to Public Information for rights under Argentine law.
Visit the AAIPDeleting your digital account closes mobile-app access across all communities. It does not terminate institutional relationships or cancel valid operations.
The option is under Preferences → Account → Delete account, with a website flow available without installing the app. Privacy email remains a contact channel and does not replace this procedure. Uninstalling or signing out does not delete an account.
A recent code verifies identity and confirms scope. A private reference lets you track progress. The operational target is twenty-four hours for active-data deletion, with failure follow-up; backups and justified exceptions are handled separately.
Deletion covers all app profiles without terminating community membership, tenancy, visitor, provider or external-subscriber relationships. Reservations, requests and procedures remain valid; institutional retention follows its specific rules.
After completion, returning requires explicit registration and identity/email verification. A new account does not restore deleted preferences, sessions or content. Roster synchronization does not recreate it automatically.
Platform communications use encryption and data access is restricted by permissions. These measures reduce risk but cannot guarantee absolute security.
Last updated: September 30, 2026. Material changes are communicated through appropriate channels. Updating this notice does not replace specific authorization where required.