RepoView

RepoView Terms of Service

Effective date: September 23, 2026
Last updated: September 24, 2026

RepoView is an independently developed, publicly available software project operated by Tharun Pranav Sakthivel, an individual developer based in Vancouver, British Columbia, Canada ("RepoView," "I," "me," or "my").

These Terms of Service ("Terms") govern access to and use of the RepoView website, Owner dashboard, repository-sharing features, share pages, rendering features, analytics, and related functionality (collectively, the "Service").

By creating an account, connecting a repository, creating or managing a share, or using a RepoView share, you agree to these Terms. If you do not agree, do not use the Service.

The Privacy Policy forms part of the rules governing use of RepoView and explains how personal information is handled.

1. Definitions

  • "Owner" means a person or organization that connects a repository, creates or manages a RepoView share, or controls a RepoView Owner account.
  • "Viewer" means a person who accesses Repository Content through a RepoView share.
  • "Repository Content" means code, documentation, images, diagrams, files, repository/ref information, and other material made available through a repository or share.
  • "Share" means a RepoView URL or access mechanism used to make selected Repository Content available to a Viewer.
  • "Analytics" means pseudonymous session, interaction, technical, network, and engagement information associated with a Share, as described in the Privacy Policy.
  • "Recipient Label" means a name, company, email address, role, source/campaign label, or note that an Owner associates with a Share or unique link.

2. Eligibility and authority

You must have the legal capacity required in your jurisdiction to agree to these Terms.

If you use RepoView on behalf of a company, university, employer, client, club, or other organization, you represent that you are authorized to do so and to provide or share the relevant Repository Content.

RepoView is not intended for use by children in circumstances where they cannot legally agree to these Terms or where parental consent is required and has not been obtained.

3. What RepoView provides

RepoView may allow Owners to:

  • connect or select repositories and refs;
  • create limited-distribution bearer-link Shares; the connected repository itself may be private on GitHub;
  • render source code, Markdown, images, diagrams, and other repository files;
  • review engagement associated with a Share;
  • receive configured notifications; and
  • manage shares and analytics through an authenticated dashboard.

Viewers may be able to browse a Share without creating a RepoView account.

RepoView is an independently maintained public project. Features may be incomplete, experimental, changed, suspended, or removed at any time. Unless I expressly state otherwise in writing, RepoView does not provide a service-level agreement, guaranteed support response time, guaranteed uptime, or enterprise support commitment.

4. Owner accounts and security

Owners are responsible for:

  • providing accurate account information;
  • protecting authentication credentials;
  • keeping connected GitHub or other service accounts secure;
  • reviewing the permissions granted to RepoView;
  • revoking access that is no longer needed; and
  • notifying me at tharunpranav.ubc@gmail.com if an Owner account or Share may have been compromised. Do not share authentication credentials in a way that bypasses RepoView security or access restrictions.

I may require re-authentication, revoke sessions, rate-limit traffic, disable a Share, or take other reasonable steps to protect the Service or its users.

5. GitHub and other connected services

RepoView may integrate with GitHub or other third-party services. Those services remain governed by their own terms, policies, permissions, availability, and APIs.

When an Owner authorizes an integration, the Owner instructs RepoView to access information and Repository Content within the permissions granted for the purpose of providing RepoView features.

The Owner is responsible for ensuring that:

  • the Owner has authority to connect the relevant account, repository, organization, and ref;
  • RepoView is granted only appropriate permissions;
  • sharing the Repository Content does not violate an NDA, employment agreement, client obligation, license, confidentiality duty, privacy right, intellectual-property right, or other restriction; and
  • access is revoked when no longer appropriate.

RepoView is not responsible for a third-party service's outage, API change, account restriction, authorization decision, or other event outside my reasonable control.

6. Repository Content and ownership

As between an Owner and RepoView, the Owner retains whatever rights the Owner has in Repository Content. These Terms do not transfer ownership of Repository Content to me.

The Owner grants RepoView a limited, non-exclusive, worldwide license to access, cache, reproduce, transform for rendering, transmit, and display Repository Content only as reasonably necessary to operate, secure, maintain, and provide the Service and the Shares the Owner creates.

That license ends when the relevant content is removed from active systems, subject to ordinary backup rotation, legal preservation requirements, and technical caching that expires in the normal course.

An Owner must not connect or share Repository Content that:

  • the Owner is not authorized to disclose;
  • unlawfully contains another person's personal information;
  • infringes copyright, trademark, patent, trade-secret, privacy, publicity, contractual, confidentiality, or other rights;
  • contains malicious code intended primarily to compromise RepoView or another system without authorization; or
  • is illegal to possess, transmit, or make available in the relevant context.

Unless RepoView expressly adds a separate authentication feature, possession of a valid Share link may be sufficient to open that Share.

Treat a Share link like a confidential bearer link. Anyone who receives, obtains, or is forwarded the link may be able to access it until it expires or is revoked.

RepoView does not guarantee that:

  • only the intended recipient opened the Share;
  • a Share was not forwarded, copied, previewed, or opened from several devices;
  • a browser session corresponds to one human being;
  • an IP address, device, network, company association, city, or location proves identity; or
  • a Recipient Label identifies the actual Viewer.

A Recipient Label describes the Owner's intended recipient or context. It is not authentication. RepoView should present that identity as Unverified unless separate identity verification is introduced.

Owners are responsible for choosing a sharing method appropriate to the sensitivity of their Repository Content. RepoView is not a substitute for a secured source-control account, data room, clean-room environment, digital-rights-management system, NDA, or other control where those protections are required.

8. Analytics are signals, not proof

RepoView may provide Analytics for a Share as described in the Privacy Policy. Depending on configuration and privacy choices, Analytics may include session timing, repository-relative file and directory interactions, searches, copy/download actions, coarse browser/device context, approximate city/region/country labels, and probabilistic security signals.

Depending on the Owner's settings and the Viewer's privacy choice, Owners may receive Analytics through dashboard interfaces, view notifications, and session-summary emails. A view notification may include a pseudonymous Viewer label, Recipient Label, first-or-returning-visit status, repository/ref, timestamp, browser, operating system, device category, approximate location, and referring host. A session-summary email may include session duration, files and directories viewed, search/copy/download counts, first and last file, top files by dwell, and probabilistic security signals.

Analytics can be incomplete or inaccurate.

You must not represent RepoView Analytics as verified proof of:

  • a particular person's identity;
  • employment by or affiliation with a particular company;
  • precise physical location;
  • a person's intent, interest, motive, competence, or decision;
  • whether a human or automated system performed every event; or
  • wrongdoing or misconduct.

VPN/proxy/Tor detection, IP-to-company mapping, bot detection, approximate location, and similar signals are probabilistic and may be wrong.

RepoView may suppress, delay, or remove Analytics where reasonably necessary for privacy, security, legal compliance, abuse prevention, or system integrity.

9. Privacy and lawful use of Analytics

Your use of RepoView is subject to the Privacy Policy.

Owners are responsible for ensuring that their creation, distribution, labelling, monitoring, and use of Shares and Analytics comply with laws and obligations that apply to them.

You must not use RepoView to:

  • secretly collect information where applicable law requires notice or consent;
  • unlawfully attempt to identify or deanonymize a Viewer using RepoView data and external data;
  • stalk, harass, intimidate, or monitor a person outside the legitimate context in which a Share was provided;
  • infer a person's sensitive or legally protected characteristics from RepoView Analytics;
  • use approximate location, network/company mapping, or engagement signals as conclusive evidence of identity or misconduct;
  • make an unlawful employment, housing, credit, insurance, education, or similar eligibility decision based on RepoView Analytics; or
  • combine RepoView Analytics with advertising/data-broker information for unrelated behavioural profiling.

If an Owner adds a recipient's name, email address, company, role, or notes, the Owner is responsible for having an appropriate and lawful reason to store and use that information.

10. Recruiting, portfolio, and review use

RepoView may be used to share engineering or project work with recruiters, hiring managers, collaborators, reviewers, clients, or other recipients.

RepoView Analytics may help an Owner understand whether and how a Share was interacted with, but they do not establish why a Viewer opened a file, whether a recipient personally performed every event, whether a recipient formed a positive or negative opinion, or what decision anyone should make.

Owners remain responsible for complying with any employment, recruiting, anti-discrimination, accessibility, candidate-record, monitoring, and privacy requirements that apply to their own use of RepoView.

11. Acceptable use

You must not use RepoView to:

  • violate applicable law or another person's rights;
  • gain unauthorized access to an account, repository, share, system, or data;
  • bypass share expiry, revocation, authorization checks, rate limits, or security controls;
  • distribute malware, credential-stealing code, ransomware, or destructive payloads;
  • operate phishing, fraud, impersonation, or deceptive schemes;
  • intentionally create fake engagement or misleading Analytics;
  • scrape or automate requests at a volume that materially interferes with the Service;
  • conduct denial-of-service activity;
  • probe or exploit vulnerabilities outside a good-faith security-testing context authorized by me or protected by applicable law;
  • use the Service to facilitate unlawful discrimination, harassment, stalking, or privacy invasion; or
  • intentionally interfere with the operation or security of RepoView.

I may use technical controls to enforce this Section.

12. Secrets and confidential information

Before creating a Share, Owners should review Repository Content for material that should not be exposed, including:

  • passwords, API keys, access tokens, private keys, signing secrets, database credentials, or environment files;
  • production customer/user data;
  • confidential employer or client information;
  • personal information that should not be disclosed;
  • regulated health, financial, educational, or government-identification information;
  • export-controlled or otherwise restricted technical information; and
  • third-party code or documents the Owner is not authorized to share.

RepoView may provide protections intended to reduce accidental exposure, but the Owner remains responsible for deciding whether specific content is appropriate to share.

If a credential or secret is accidentally exposed, revoking a RepoView Share does not rotate or invalidate the credential. The Owner must rotate/revoke the credential at its source.

13. Free project; future paid features

RepoView is currently provided as a public project without a promise of paid-service features.

No fee, subscription, renewal obligation, refund right, service credit, or service-level commitment exists unless I separately introduce a paid offering with clear terms before purchase.

If paid features are introduced later, the applicable price, billing interval, renewal/cancellation rules, taxes, refund terms, and any additional conditions will be disclosed before a user is charged. These Terms will be updated where appropriate.

14. Feedback

If you voluntarily send feedback, suggestions, bug reports, or feature ideas, you give me permission to use them to improve RepoView without an obligation to compensate you.

This permission does not transfer ownership of your Repository Content or confidential information.

Do not send feedback containing information you are not authorized to disclose.

15. RepoView intellectual property

Except for Repository Content and third-party/open-source components, RepoView's software, interface, design, branding, documentation, and other original project materials are owned by me or licensed to me.

Your right to use the hosted Service is limited, non-exclusive, revocable, non-transferable, and subject to these Terms.

If RepoView's source code or specific components are released under an open-source license, that license governs your use of the licensed source code. Public availability of the hosted project does not, by itself, grant an open-source license to code that has not been released under one.

Third-party software remains subject to its own license terms.

If you believe content available through RepoView infringes your copyright, privacy, confidentiality, or other legal rights, contact tharunpranav.ubc@gmail.com and include enough information to identify the material, explain the claimed right, and allow me to contact you.

I may temporarily restrict or remove access while reviewing a good-faith complaint. Where appropriate and legally permitted, I may notify the affected Owner.

Submitting a knowingly false legal or infringement complaint may itself create liability.

17. Availability, changes, and experimental features

RepoView is provided as an independently maintained public software project and may change frequently.

I do not guarantee that the Service will be uninterrupted, error-free, secure against every attack, compatible with every repository/file, or available indefinitely.

RepoView may be affected by maintenance, bugs, provider outages, Internet failures, GitHub/API changes, security incidents, dependency failures, legal requirements, or events outside my control.

I may add, change, limit, suspend, or discontinue features at any time. Where reasonably practical, I will avoid intentionally making a material change that creates unnecessary risk to existing user data without notice.

Features marked beta, preview, experimental, or similar may be incomplete and should not be relied on for high-risk or legally regulated workflows without independent safeguards.

18. Suspension and termination

You may stop using RepoView at any time. Owners may revoke or delete Shares using available controls.

I may restrict, suspend, or terminate access, revoke a Share, or block traffic if I reasonably believe that:

  • these Terms have been materially breached;
  • use of RepoView creates a material security, legal, privacy, or operational risk;
  • activity is fraudulent, abusive, or harmful;
  • action is necessary to respond to a vulnerability or compromised account/share;
  • a third-party platform requires it; or
  • applicable law or legal process requires it.

Where reasonable and safe, I may provide notice or an opportunity to correct a remediable issue. Immediate action may be taken for security, abuse, fraud, or legal reasons.

After termination, information will be handled according to the Privacy Policy and ordinary backup/deletion cycles.

Sections that logically survive termination, including ownership, disclaimers, liability limitations, indemnity, and dispute provisions, continue to apply.

RepoView may depend on or link to third-party services, including GitHub, Supabase, hosting or infrastructure providers, and email providers.

I do not control and am not responsible for third-party content, terms, privacy practices, security, availability, or decisions.

Following an external link may cause the destination site to receive ordinary browser/request information according to that site's own practices.

20. Disclaimers

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, REPOVIEW IS PROVIDED "AS IS" AND "AS AVAILABLE."

I DISCLAIM WARRANTIES, REPRESENTATIONS, AND CONDITIONS NOT EXPRESSLY STATED IN THESE TERMS, INCLUDING IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, QUIET ENJOYMENT, AND UNINTERRUPTED OR ERROR-FREE OPERATION.

WITHOUT LIMITING THE ABOVE, I DO NOT WARRANT THAT:

  • A SHARE WILL REMAIN CONFIDENTIAL AFTER AN OWNER GIVES THE URL TO ANOTHER PERSON;
  • REPOSITORY CONTENT WILL NEVER BE COPIED, DOWNLOADED, SCREENSHOTTED, OR FORWARDED BY A VIEWER;
  • ANALYTICS WILL IDENTIFY A PARTICULAR PERSON, COMPANY, DEVICE, OR LOCATION;
  • ANALYTICS WILL BE COMPLETE OR FREE OF BOT/AUTOMATION EFFECTS;
  • A VIEWER'S BEHAVIOUR REVEALS THEIR INTENT, OPINION, OR DECISION;
  • THIRD-PARTY SERVICES WILL REMAIN AVAILABLE; OR
  • THE SERVICE WILL BE FREE FROM EVERY SECURITY VULNERABILITY.

Some jurisdictions do not allow certain warranty exclusions. In those jurisdictions, the exclusions apply only to the maximum extent permitted by law.

21. Limitation of liability

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, I WILL NOT BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE, OR CONSEQUENTIAL DAMAGES, OR FOR LOSS OF PROFITS, REVENUE, BUSINESS, OPPORTUNITY, GOODWILL, DATA, OR REPOSITORY CONTENT, ARISING OUT OF OR RELATED TO REPOVIEW, EVEN IF ADVISED THAT SUCH LOSS COULD OCCUR.

TO THE MAXIMUM EXTENT PERMITTED BY LAW, MY TOTAL AGGREGATE LIABILITY ARISING OUT OF OR RELATING TO REPOVIEW WILL NOT EXCEED THE GREATER OF:

  1. THE AMOUNT YOU PAID DIRECTLY FOR REPOVIEW DURING THE 12 MONTHS BEFORE THE EVENT GIVING RISE TO THE CLAIM; OR
  2. CAD $100.

These limitations do not exclude liability that cannot lawfully be excluded or limited and do not reduce non-waivable consumer rights.

Because RepoView is a project operated by an individual rather than a separate corporation, these Terms do not create a corporate liability shield. They define the contractual limits of the Service only to the extent enforceable under applicable law.

22. Indemnity for Owner-controlled content and use

To the extent permitted by law, if you are an Owner, or use RepoView on behalf of an organization, you agree to indemnify and hold me harmless from third-party claims, damages, penalties, costs, and reasonable legal expenses arising from:

  • Repository Content you connect, upload, or share without the required rights or authorization;
  • your unlawful or unauthorized use of Analytics;
  • recipient labels or personal information you add without a lawful basis;
  • your violation of another person's intellectual-property, confidentiality, privacy, or contractual rights; or
  • your material breach of these Terms.

This Section does not require you to indemnify me for a claim to the extent caused by my own fraud, wilful misconduct, or liability that cannot lawfully be shifted to you.

23. Governing law and disputes

Except where mandatory consumer or privacy law requires otherwise, these Terms and disputes arising from them are governed by the laws of the Province of British Columbia and the applicable federal laws of Canada, without regard to conflict-of-law rules.

Subject to any mandatory right to bring a claim elsewhere, the courts located in British Columbia, Canada will have jurisdiction over disputes arising from or relating to these Terms or RepoView.

Nothing in this Section prevents either party from seeking urgent injunctive or protective relief from a court with jurisdiction where reasonably necessary to protect security, confidential information, intellectual property, or legal rights.

24. Changes to these Terms

I may update these Terms as RepoView evolves.

The displayed effective and last-updated dates identify the published copy. RepoView's application legal-version records may be maintained separately. If a change materially affects existing Owners' rights or obligations, I will provide reasonable notice where practical or where required by law.

Continued use after updated Terms take effect constitutes acceptance to the extent permitted by law. If applicable law requires express agreement to a particular change, I will seek that agreement.

25. Assignment and project transfer

You may not transfer an Owner account in a way that circumvents security restrictions or gives an unauthorized person access to repositories or Analytics.

I may transfer operation of RepoView and these Terms to a successor operator or legal entity if RepoView is incorporated, sold, or otherwise transferred, subject to applicable law and the Privacy Policy. Where required, users will receive notice of a material change in the operator.

26. General terms

If a provision of these Terms is found unenforceable, it will be enforced to the maximum extent permitted and the remaining provisions will remain in effect.

A failure to enforce a provision is not a waiver of the right to enforce it later.

Headings are for convenience only.

These Terms, together with the Privacy Policy and any additional terms expressly presented for a specific feature, form the agreement governing use of the hosted RepoView Service.

No person other than the parties to these Terms has a right to enforce them except where applicable law provides otherwise.

27. Contact

Questions about these Terms or rights complaints: tharunpranav.ubc@gmail.com
Technical or account support: tharunpranav.ubc@gmail.com
Privacy requests: tharunpranav.ubc@gmail.com

RepoView

  • Operator: Tharun Pranav Sakthivel
  • Location: Vancouver, British Columbia, Canada
  • Privacy contact / Privacy Officer: Tharun Pranav Sakthivel
  • Email: tharunpranav.ubc@gmail.com