Privacy Policy

1. Scope

AiM — AI Network Manager (“AiM”, “we”, “us” or “our”) is a business relationship management product concept owned by Creon Design Studio. It is designed to help people capture business-card details, organize contacts, retain relationship context and manage follow-ups.

This policy is intended to cover the AiM website and the mobile app or related services when they are made available. If a feature is not implemented, it does not mean that the feature is currently collecting information.

2. Information we may handle

Depending on the features you use and the product configuration, AiM may handle the following categories of information:

• Account information: such as your name, mobile number, email address, authentication details and account preferences.
• Business contact information you add: names, designations, company names, phone numbers, WhatsApp numbers, email addresses, websites, postal addresses and public business or social links.
• Scanned card data: images of visiting cards and text extracted from them using optical character recognition (OCR).
• Relationship context: notes, voice notes or their transcriptions, where supported; event name, date and venue; tags; categories; referral context; interaction history; and follow-up tasks.
• Workspace information: team membership, assigned contacts, roles and activity records if team features are enabled.
• Subscription and transaction records: plan, billing cycle, subscription status and provider reference identifiers if paid plans are offered. Payment details may be handled by the selected payment provider.
• Technical information: device, app version, diagnostics, security events and usage information where these are collected by the implemented service.
• Enquiry information: details you submit through a website contact form.

Please only add contact information that you are authorized to store and use. People whose details appear on a business card may not be users of AiM.

3. How information is used

Where the relevant features are available, information may be used to:

• Create, maintain, search, categorize and update business contact records.
• Extract and normalize text from visiting cards and suggest categories, sub-categories or tags.
• Store notes and event context, manage follow-up reminders and help users take actions such as calling or emailing a contact.
• Synchronize or back up information across devices when the user enables a supported sync feature.
• Operate individual or team workspaces, including contact assignments and access controls.
• Manage accounts, subscriptions, support requests, service reliability and security.
• Understand product performance and improve the service where analytics are enabled.
• Respond to enquiries and communicate important service or policy updates.

We do not state that any particular processing activity occurs unless the corresponding feature and service have actually been implemented.

4. AI and OCR processing

AiM is designed to use OCR and AI-assisted features for tasks such as reading business cards, suggesting contact categories and tags, summarizing notes and searching a user's private network.

• Extracted text and AI suggestions should be reviewable and correctable by the user.
• AI-generated suggestions should not silently replace user-entered contact information.
• Processing may occur on the device or through a server or third-party AI provider, depending on the final implementation.
• Before launch, we will identify the actual AI/OCR providers and explain whether submitted information is sent to them, how it is used and what retention terms apply.

Do not assume that all processing happens on-device or that information is never transmitted to a third party. Those details depend on the implemented architecture and provider terms.

5. Sharing and service providers

AiM is intended to keep a user's contact network private by default. Information may be shared in limited circumstances that are necessary for the service, including:

• At your direction: when you choose to export information, open a communication app, or share contacts through a supported feature.
• Within a team workspace: with authorized workspace members according to the workspace's sharing and permission settings.
• With service providers: such as hosting, storage, authentication, OCR/AI, notifications, analytics, support or payment providers, if used by the live service.
• For legal and safety reasons: where disclosure is required by applicable law or is reasonably necessary to protect rights, security or prevent misuse.

We do not claim to sell personal information. Before launch, document the actual providers, the information each receives and the contractual safeguards that apply.

6. Security and retention

The product brief calls for safeguards such as encryption in transit and at rest, secure authentication, workspace access controls, tenant data isolation, backup and recovery procedures, export and deletion controls, and audit logs for important team actions. These are design requirements; do not represent them as operational guarantees until verified in the live service.

Information should be retained only for as long as necessary for the purposes described in this policy, to provide the service, meet legitimate operational needs and comply with applicable legal obligations. Actual retention periods, backup deletion timelines and card-image retention settings must be confirmed and documented before launch.

No method of electronic storage or transmission can be guaranteed to be completely secure.

7. Your choices and rights

Depending on the features available, you may be able to review and correct contact records, manage permissions, export your information, control optional synchronization, manage notifications, leave a team workspace or request account deletion.

You should only share contacts with a team when authorized to do so. Where a contact belongs to a shared workspace, workspace policies may affect how it is handled when a member leaves.

Applicable privacy laws may provide additional rights, subject to their conditions and exceptions. To make a request, contact us using the details in the Contact section. Add a monitored privacy email address before publishing this page.

8. Device permissions

Depending on the features you choose to use, the mobile app may request:

• Camera: to capture visiting cards.
• Contacts: if contact import, export or device synchronization is supported and you opt in.
• Notifications: to deliver follow-up reminders and service updates.
• Photos or files: to import existing card images or attachments.
• Microphone: to record voice notes if that feature is available.

Permissions should be requested when relevant and can generally be managed in your device settings. Exact permission behavior depends on the app build and operating system.

9. Children

AiM is intended for professional and business networking use, not for children. The service is not designed to knowingly collect personal information from children. The owner should confirm the minimum-age policy and applicable requirements before release.

10. International processing

Depending on the hosting and service providers selected, information may be processed or stored in countries other than the country where you live. Before launch, identify the relevant locations and confirm the safeguards and legal requirements applicable to those transfers.

11. Changes to this policy

We may update this policy as AiM's features, providers or legal obligations change. The revised version should be published on this page with an updated effective date. Where required, we will provide additional notice or seek consent.

12. Contact

For privacy questions, access or deletion requests, or concerns about how information is handled, contact:

Creon Design Studio
Product: AiM — AI Network Manager
Email: [ADD OFFICIAL PRIVACY EMAIL]
Address: [ADD OFFICIAL BUSINESS ADDRESS, IF REQUIRED]

Replace the bracketed placeholders with monitored, accurate contact details before publishing. Do not publish this page with incomplete contact information.